1,885
edits
Changes
no edit summary
|-
|4||Sept 22||[[#Tuesday (Sep 23)|Assembly language presentations & Assembly Basics]]||[[#Friday (Sep 26)|Assembly Language Lablanguage presentations, continued]]||[[#Week 4 Deliverables|Blog about writing in assembly language (Lab 3)the content of your presentation]]
|-
|5||Sep 29||[[#Tuesday (Sep 30)|Discuss Assembly lab (Lab 3 results / Inline assembler and compiler optimizations)]]||[[#Friday (Oct 3)|Inline assembler and compiler optimizations / Potential Project Triage – Scan the potential project list from the Linaro Performance site]]||[[#Week 5 Deliverables|Blog post about assembly lab (lab 3) and potential projects]]
|-
|6||Oct 6||[[#Tuesday (Oct 7)|Guest Speaker: Jon "Maddog" Hall]]||[[#Friday (Oct 10)|Codebase analysis / Memory barriers and Atomics]]||[[#Week 6 Deliverables|Analyze your portion of the potential projects list and post your results on the wiki and your blog; select two projects and contact the associated communitiesplatform-specific code in 3 packages.]]
|-
|7||Oct 13||[#Tuesday (Oct 15)|[[#Tuesday (Oct 14)|Architecture-specific Code for Performance- Why?]]||Group hack session - Porting[[#Friday (Oct 17)|Compiler Intrinsics and Picking your Package]]||[[#Week 7 Deliverables|Blog Pick your package and blog about your progressit.]]
|-style="background: #f0f0ff"
|Study Week||Oct 20||colspan="3" align="center"|Study Week<br />'''[http://fsoss.ca FSOSS 2014] on Thursday-Friday'''
|-
|8||Oct 27||Architecture-specific [[#Tuesday (Oct 28)|Working with the Code for Performance]]||[[#Friday (Oct 31)|Group hack session - PortingProfiling]]||[[#Week 8 Deliverables|Blog about your progress.]]
|-
|9||Nov 3||Portability - Removing platform-specific code[[#Tuesday (Nov 4)|Profiling review]]||[[#Friday (Nov 11)|Group hack session - Portability]]||[[#Week 9 Deliverables|Blog about Post baseline stats for your progresssoftware.]]
|-
|810||Nov 10||Project Work[[#Tuesday (Nov 11)|Presentations]]||Project Work[[#Friday (Nov 14)|AArch64 on x86_64 / Hack session]]||[[#Week 10 Deliverables|Get code into review and blog Blog about ityour project status - 1st project marks.]]
|-
|911||Nov 17||Status Update[[#Tuesday (Nov 18)|Discussion and hack session]]|Foundation Models|[[#Friday (Nov 21)|Install Discussion and Test With Foundation Model hack session: Commercial vs. Technical Reality]]||[[#Week 11 Deliverables|Upstream your work and blog about it.]]
|-
|1012||Nov 1024||Profiling[[#Tuesday (Nov 25)|Project Update Presentations]]||[[#Friday (Nov 28)|Discussion and hack session]]|Baseline Profiling|[[#Week 12 Deliverables|Post baseline stats for Blog about your softwareproject status - 2nd project marks.]]
|-
|1113||Nov 17Dec 1||Optimizing Code[[#Tuesday (Dec 2)||Group hack - Profiling Discussion and optimizing||Post a code review update.|- |12||Nov 24||Using complier optimizations||Project Work||Post a code review update.|- |13Hack Session]]||[[#Friday (Dec 15)||Final Presentations||Final PresentationsDiscussion and Hack Session]]||Code accepted upstream. Blog about it!
|-style="background: #f0f0ff"
!Category!!Percentage!!Evaluation Dates
|-
|Communication||align="right"|20%||<strike>September 30</strike>, <strike>October 31</strike>, November 21, December 10
|-
|Quizzes||align="right"|10%||May be held during any class, usually at the start of class. A minimum of 5 one-page quizzes will be given. No make-up/retake option is offered if you miss a quiz. Lowest 3 scores will not be counted.
|Labs||align="right"|10%||See deliverables column above.
|-
|Project work||align="right"|60%||October 10<strike>November 11</strike> (15%), November 2125 (20%), December 10(25%)
|}
=== Tuesday (Sep 23) ===
* Give your [[Fall 2014 SPO600 Assembly Language Presentation|presentation about an assembly language topic]] - teach your SPO600 colleagues
=== Friday (Sep 26) ===
* Remainder of the [[Fall 2014 SPO600 Assembly Language Presentation|presentations about an assembly language topic]]
* [[Assembler Basics|Introduction to assembly language]]
* Writing x86_64 and aarch64 code in the [[SPO600 Assembler Lab|Assembly language lab (Lab 3)]]
=== Week 4 Deliverables ===
* Blog about the your [[Fall 2014 SPO600 Assembler LabAssembly Language Presentation|assembler lab (Lab 3)presentation]]
== Week 5 ==
=== Tuesday (Sep 30) ===
* [[SPO600 Assembler Lab|Assembler Lab]] review === Friday (Oct 3) ===
* [[Inline Assembly Language]]
* [[Compiler Optimizations]]
The [http://performance.linaro.org/find/ list of packages] for this project was originally developed by the UK Debian developer Steve Macintyre, who works for Linaro. His focus in developing that list was to find packages that contained assembly language code for x86 (or other platforms) and which did not have assembly language code for ARM, especially Aarch64. As a result, the list includes many false-positives: there are many packages on there that can successfully build on ARM, either due to C work-arounds for the missing assembly code, or conditional compilation of the assembly code, or recent updates to the software, or other reasons.
In this class, we're going to start to triage this list by analyzing which packages exist in the Fedora package set and which have been successfully built for the aarch64 architecture.
# Grab the list of packages from the Linaro Performance Challenge site.
# Find out the corresponding names of the packages in the Fedora package set. Most of these will be the same as in the list, but some may be different.
# Find out which packages have not been built on x86_64# Find out which packages have build for Fedora on aarch64# Come up with a short-list which consists of the packages in these groups:## Packages which do not exist in Fedora -- these need further investigation## Packages which exist in Fedora and build on x86_64, but which do not build on aarch64 The packages in Divide the short-resulting list will be divided up between the members of the class for further analysis.
{{Admon/tip|Participating in the Linaro Performance Challenge|You are invited to participate in the [http://performance.linaro.org Linaro Performance Challenge] directly, utilizing the work you are doing in the SPO600 course. Doing so may enable you to receive a prize for participation and the chance to win a trip to a Linaro Connect conference. In order to participate in the Challenge, you will need to comply with the technical requirements and rules of the Challenge.<br/><br/>Your participation in this course, and the mark you receive in this course, are independent of your participation in the Linaro Performance Challenge.<br/><br/>In other words: Linaro and Seneca are distinct entities, and although you can participate in both the Challenge and SPO600 with the same project, Seneca assumes no responsibility for your interaction with Linaro, and vice-versa.}}
=== Week 5 Deliverables ===
* Blog about the potential project list [[SPO600 Assembler Lab|assembler lab (Lab 3)]].* Do the tasks assigned to youon the [[Fall 2014 SPO600 Packages by Participant]] page, and blog about it.
== Carried Forward = Tuesday (Oct 7) ===
== Deliverables = Friday (Oct 10) ===* Blog your conclusion to the [[SPO600 Compiled C Lab]]
In groups, we'll be analyzing software pacakges from the [[Fall 2014 SPO600 Packages by Participant|Packages by Participant]] list to find the platform-specific code and build instructions.
=== Week 3 6 Deliverables ===
=== Tuesday (Feb 4Oct 14) ===
==== Memory Barriers ====
** [http://blogs.msdn.com/b/oldnewthing/archive/2008/10/03/8969397.aspx MSDN Blog Post] with a very clear explanation of Acquire-Release.
** [http://preshing.com/20130922/acquire-and-release-fences/ Preshing on Programming post] with a good explanation.
** [http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.genc010197a/index.html ARMv8 Instruction Set Architecture Manual] (ARM InfoCentre registration required) - See the section on Acquire/Release and Load/Store, especially Load/Store Exclusive (e.g., LDREX)
==== Atomics ====
'''Atomics''' are operations which must be completed in a single step (or appear to be completed in a single step) without potential interruption.
* Wikipedia has a good basic overview of the need for atomicity in the article on [http://en.wikipedia.org/wiki/Linearizability Linerarizability]
== Week 8 ==
=== Friday Tuesday (March 14Oct 28) ===* Comparison of Emulation** QEMU** Fast Model and Foundation Model* Install and configure the Foundation Model** [[:fedora:Architectures/ARM/AArch64/QuickStart|Fedora AArch64 Quick Start]]** [http://www.linaro.org/engineering/engineering-projects/armv8 Linaro Foundation Model Instructions]* Baseline Benchmarking
== Week 10 =Friday (Oct 31) ===* Benchmarking and Profiling
* Profiling with <code>gprof</code>
** Build with profiling enabled (use the option <code>-pg</code>with both gcc and ld)
** Run the profile-enabled executable
** Analyze the data in the <code>gmon.out</code> file
* [http://www.thegeekstuff.com/2012/08/gprof-tutorial/ Profiling with GProf]
=== Week 8 Deliverables ===* Blog about your progress connecting with the communities associated with your projects and working with the code. == Week 9 ===== Tuesday (Nov 4) ==* Profiling/baseline benchmarking review* Hacking session === Friday (March 21Nov 7) ===* Gather Hacking session === Week 9 Deliverables ===* Blog about your baseline statistics for benchmarking/profiling. == Week 10 ===== Tuesday (Nov 11) ===* Presentation on your softwareproject status === Friday (Nov 14) ===* Running AArch64 code on x86** Foundation models** [[AArch64 QEMU User Space Emulation]]
=== Week 10 Deliverables ===
* Blog about your baseline benchmark project status == Week 11 ===== Tuesday (Nov 18) ===* Discussion and hack session** Blog post about upstreaming: [https://www.linaro.org/blog/core-dump/working-upstream/ What do we mean by working upstream: A long-term contributor's view] === Friday (Nov 21) ===* Discussion and hack session === Week 11 Deliverables ===* Upstream your changes/test results/documentation* Blog about your work* '''Note: Blogs will be marked as of Nov 21 11:59 pm''' == Week 12 ===== Tuesday (Nov 25) ===* Project update presentations === Friday (Nov 28) ===* Discussion and hack session: ''Commercial vs. Technical Reality'' == Week 13 == === Tuesday (Dec 2) ===* Discussion and hack session === Friday (Dec 5) ===* Wrap-->up session* '''Remember: Final project submissions via blog are due 11:59 pm December 10.'''
<BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/><BR/>