|6||Oct 6||[[#Tuesday (Oct 7)|Guest Speaker: Jon "Maddog" Hall]]||[[#Friday (Oct 10)|Codebase analysis / Memory barriers and Atomics]]||[[#Week 6 Deliverables|Analyze the platform-specific code in 3 packages.]]
|-
|7||Oct 13||[#Tuesday (Oct 1415)|[[#Tuesday (Oct 14)|Architecture-specific Code - Why?]]||[[#Friday (Oct 17)|Compiler Intrinsics and Picking your Package]]||[[#Week 7 Deliverables|Pick your package and blog about it.]]
|-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||Profiling[[#Tuesday (Oct 28)|Working with the Code]]||[[#Friday (Oct 31)|Group hack session - Profiling]]||[[#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|Post baseline stats for your software.]]|-
|10||Nov 10||Optimizing Code[[#Tuesday (Nov 11)|Presentations]]|Group hack |[[#Friday (Nov 14)|AArch64 on x86_64 / Hack session]]||[[#Week 10 Deliverables|Blog about your progressproject status - 1st project marks.]]
|-
|11||Nov 17||Optimizing Code[[#Tuesday (Nov 18)|Discussion and hack session]]||Group [[#Friday (Nov 21)|Discussion and hack session - Profiling and optimizing: Commercial vs. Technical Reality]]||[[#Week 11 Deliverables|Post a code review update.Upstream your work and blog about it]]
|-
|12||Nov 24||Using complier optimizations[[#Tuesday (Nov 25)|Project Update Presentations]]||[[#Friday (Nov 28)|Discussion and hack session]]|Project Work|[[#Week 12 Deliverables|Post a code review updateBlog about your project status - 2nd project marks.]]
|-
|13||Dec 1||Final Presentations[[#Tuesday (Dec 2)|Discussion and Hack Session]]|Final Presentations|[[#Friday (Dec 5)|Discussion 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%||<strike>November 2111</strike> (15%), November 25 (20%), December 10(25%)
|}
=== Week 7 Deliverables ===
# Select at least two software packages from the [http://performance.linaro.org|Linaro performance web site] and/or the [[Fall 2014 SPO600 Packages by Participant|Packages]] page.
# Record your choice on:
## The [[Fall 2014 SPO600 Participants|Participants page]] - so that your colleagues in class know that you're working on the package(s). '''Note:''' Package choices will be approved by [[User:Chris Tyler|your professor]], but will usually be accepted on a first-come, first-served basis.
## The [http://performance.linaro.org|Linaro performance web site] - this will tell other people outside of our group within the Linux-on-ARM community that you are working on the package(s).
# Investigate and blog about your choice.
# Blog about your work plan and what you need to investigate/learn in order to complete your project.
<!--== Week 8 ==
############################################################################################################################################################################################################################################################################################################=== Tuesday (Oct 28) ===
== Carried Forward from previous semester -- Kept here for potential copypasta ==Working with the Code* Working with GIT* Working with other version control systems
=== Friday (Jan 17) ===Looking at How Distributions Package the Code* [[SPO600 Compiled C Lab]]Using fedpkg
== Deliverables = Friday (Oct 31) ===* Blog your conclusion to the [[SPO600 Compiled C Lab]]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
*** <code>gprof ''nameOfBinary''</code> # Displays text profile including call graph
*** <code>gprof ''nameOfBinary'' | gprof2dot | dot | display -</code> # Displays visualization of call graph
== Week 3 ==Resources* [https://sourceware.org/binutils/docs-2.16/gprof/ GProf Manual]* [http://www.thegeekstuff.com/2012/08/gprof-tutorial/ Profiling with GProf]
=== Tuesday (Jan 21) Week 8 Deliverables ===* [[Assembler Basics]]Blog about your progress connecting with the communities associated with your projects and working with the code.
==Week 9 = Friday ==== Tuesday (Jan 24Nov 4) ===* Background information: [[SPO600 aarch64 QEMU on Ireland]]Profiling/baseline benchmarking review* [[SPO600 Assembler Lab]]Hacking session
=== Week 3 Deliverables Friday (Nov 7) ===* Blog your conclusion to the [[SPO600 Assembler Lab]]Hacking session
=== Week 4 9 Deliverables ===* Blog about your baseline benchmarking/profiling.
== Week 10 ===== Tuesday (Jan 28Nov 11) ===* [[SPO600 Assembler Lab|Assembler Lab]] review* [[Inline Assembly Language]]* [[Compiler Optimizations]]Presentation on your project status
=== Friday (Jan 31Nov 14) ===* Running AArch64 code on x86** Foundation models** [[AArch64 QEMU User Space Emulation]]
=== Week 10 Deliverables ===* [[Codebase Analysis Lab]]Blog about your project status
== Week 11 ==== Week 4 Deliverables = 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]
* '''Reminder:''' Week 1-3 blog posts are due for marking on === Friday, January 31.(Nov 21) ===* Blog about the [[Codebase Analysis Lab]]Discussion and hack session
=== Week 5 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 (Feb 4Nov 25) ===* Project update presentations
Platform-specific code is often utilized for '''Memory Barriers''' === Friday (Nov 28) ===* Discussion and hack session: ''Commercial vs. Technical Reality'Atomics Operations'''.
== Week 13 ==
=== Friday Tuesday (Feb 7Dec 2) ===* Discussion and hack session
==== Hack Session: Potential Project Analysis =Friday (Dec 5) ===* Wrap-up session* '''Remember: Final project submissions via blog are due 11:59 pm December 10.'''
Select a project from the [[Winter 2014 SPO600 Software List]] and perform these steps:
# Edit that page to put your name in the "Claimed by" column.
# Investigate the package to determine:
#* If the current version has been built for ARM (e.g., exists in the Fedora aarch64 port - fastest way to test is to use 'yum' inside the arm64 emulation environment on Ireland)
#* What the platform-specific code in the software does
#* Whether portable work-arounds exist
#* The need for an aarch64 port or for platform-specific code elimination
#* Opportunities for optimization
#* The amount of work involved in porting and optimizing, and your skills for performing that work
# Based on the result of your investigation, decide on your interest in the project.
#* If you wish to choose this project for yourself, place it on your row in the [[Winter 2014 SPO600 Participants|Participants]] page.
#* If you do not wish to choose this project, remove your name from the "Claimed by" column in the [[Winter 2014 SPO600 Software List|Software List]] page.
# Repeat until you have two packages.
{{Admon/note|Overload|It is strongly recommended that you choose two projects with a total scope sum of 0-1. If you wist to try a higher or lower sum, or more or less than two projects, please talk to your professor.}}
{{Admon/tip|RPM Packages|For sofware that is present in the rpmfusion repositories but not in Fedora, you can use <code>yumdownloader --source ''packagename''</code> to grab the source RPM and then examine it using the RPM tools. See [[RPM Packaging Process]] for information.}}
=== Week 5 Deliverables ===
* Blog about your two selected projects, including your detailed initial analysis of them.
** You may want to break this into a couple of posts - e.g., post about your first package while you're working on your second.
** Feel free to also blog about why you did '''not''' choose particular packages, too.
== Week 6 ==
=== Tuesday (Feb 11) ===
* Architecture-specific code for Performance
** Sometimes assembler is used in a C/C++ program for performance. However, modern versions of C/C++ (such as C++11) and recent compilers provide portable ways of accessing high-performance processor capabilities, such as Single Instruction/Multiple Data (SIMD) instructions (called "marketing names" such as SSE, Neon, MMX, 3DNow, or AltaVec on various processors).
** Linaro enginener Matthew Gretton-Dann gave a good presentation on [http://www.linaro.org/linaro-blog/2013/09/20/introduction-to-porting-and-optimising-code/ Porting and Optimizing Code] for aarch64. The vectorization portion, beginning at 28:10, provides a good introduction to SIMD and autovectorization using GCC on aarch64 (Note that the earlier portion of the presentation includes good information about Atomics).
*** [http://www.youtube.com/watch?v=epzYErIIx0Y YouTube Video] direct link
*** [http://www.linaro.org/assets/common/campus-party-presentation-Sept_2013.pdf Slides] direct link
** Note that in the presentation above, Matthew takes the code beyond portability without straying into assembler (e.g., using compiler-specific, architecture-specific intrinsics). It is possible to achieve almost all of the performance gains without becoming arch-specific, and most of those can be attained without becoming compiler-specific as well.
* For full details on the SIMD instructions in aarch64, refer to the [http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.genc010197a/index.html ARMv8 Instruction Set Overview], particularly section 5.7.
=== Week 6 Deliverables ===
* Complete your analysis of your two selected software projects (if you haven't already) - see [[#Week 5|Week 5]]. Blog in detail about your findings.
* Identify the upstream communities that develop and maintain the software you have selected to work on. Figure out how they are structured, how they communicate, how code is maintained, and how patches are accepted. Introduce yourself to each of the two communities (one for each of the two software projects you have selected). Blog about your findings.
== Week 7 ==
* Project Work
== Week 8 ==
* Project Work ([[User:Chris Tyler|Chris Tyler]] is at [http://www.linaro.org/connect-lca14 Linaro Connect]) this week.
* Aim at getting your code changes upstream to your communities
== Week 9 ==
=== Tuesday (March 11) ===
* Status updates
* Update from Linaro Connect
* Discussion of useful tools
** screen
** time
=== Friday (March 14) ===
* 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
==== Resources ====
* Foundation Model
** [http://www.arm.com/products/tools/models/fast-models/ ARM Fast Models] - Note that "fast" here refers to the modelling approach, not execution speed!
* Benchmarking
** [http://www.tokutek.com/wp-content/uploads/2013/05/20130424-percona-live-benchmarking.pdf Benchmarking Talk by Tim Callaghan]
=== Week 9 Deliverables ===
* Set up the Foundation Model
* Upstream your proposed code changes
* Blog about your work
== Week 10 ==
=== Tuesday (March 18) ===
* Profiling with <code>gprof</code>
** Build with profiling enabled (<code>-pg</code>)
** Run the profile-enabled executable
** Analyze the data in the <code>gmon.out</code> file
*** <code>gprof ''nameOfBinary''</code> # Displays text profile including call graph
*** <code>gprof ''nameOfBinary'' | gprof2dot | dot | display -</code> # Displays visualization of call graph
Resources
* [https://sourceware.org/binutils/docs-2.16/gprof/ GProf Manual]
* [http://www.thegeekstuff.com/2012/08/gprof-tutorial/ Profiling with GProf]
=== Friday (March 21) ===
* Gather baseline statistics for your software
=== Week 10 Deliverables ===
* Blog your baseline benchmark results
-->
<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/>
