|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 15)|[[#Tuesday (Oct 14)|Architecture-specific Code for Performance- Why?]]||[[#Friday (Oct 17)|Compiler Intrinsics and Picking your Package]]||[[#Week 7 Deliverables|Pick you 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||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%)
|}
* Pick three additional packages (not the ones done in class) from your section of the [[Fall 2014 SPO600 Packages by Participant|Packages by Participant]] list and find the platform-specific code (or build instructions). Figure out what that code does, and document that on the list page. Blog about your results and your reflections on the task.
<!-- ############################################################################################################################################################################################################################################################################################################ == Carried Forward from previous semester -- Kept here for potential copypasta == === Friday (Jan 17) ===* [[SPO600 Compiled C Lab]] == Deliverables ==* Blog your conclusion to the [[SPO600 Compiled C Lab]] == Week 3 == === Tuesday (Jan 21) ===* [[Assembler Basics]] === Friday (Jan 24) =7 ==* Background information: [[SPO600 aarch64 QEMU on Ireland]]* [[SPO600 Assembler Lab]]
=== Week 3 Deliverables Tuesday (Oct 14) ===* Blog your conclusion to the [[SPO600 Assembler Lab]]
== Week 4 == === Tuesday (Jan 28) ===* [[SPO600 Assembler Lab|Assembler Lab]] review* [[Inline Assembly Language]]* [[Compiler Optimizations]] === Friday (Jan 31) === * [[Codebase Analysis Lab]] === Week 4 Deliverables === * '''Reminder:''' Week 1-3 blog posts are due for marking on Friday, January 31.* Blog about Discussion of some of the [[Codebase Analysis Lab]] == Week 5 == === Tuesday reasons that platform specific (Feb 4usually assembly language) === Platform-specific code is often utilized for '''Memory Barriers''' and '''Atomics Operations'''.used in software
==== 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]
* GCC provides intrinsics (built-in functions) for atomic operations, as documented in the GCC manual:
** [http://gcc.gnu.org/onlinedocs/gcc-4.8.2/gcc/_005f_005fsync-Builtins.html#_005f_005fsync-Builtins Legacy __sync Built-in Functions for Atomic Memory Access]
** [http://gcc.gnu.org/onlinedocs/gcc-4.8.2/gcc/_005f_005fatomic-Builtins.html#_005f_005fatomic-Builtins Built-in functions for memory model aware atomic operations]
* The Fedora project has some guidelines/recommendations for the use of these GCC builtins:
** http://fedoraproject.org/wiki/Architectures/ARM/GCCBuiltInAtomicOperations
=== Friday (Feb 7) ===
==== Hack Session: Potential Project Analysis =Friday (Oct 17) ===
Select a project from the * [[Winter 2014 SPO600 Software ListCompiler Intrinsics]] 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 * The use of compiler intrinsics (e.g., exists those in gcc, or in another compiler) locks you into the use of that specific compiler (or another that supports the Fedora aarch64 port - fastest way to test exact same intrinsics), but it provides platform portability. It is better to use 'yum' inside language features (e.g., C11 or C++11 atomic and acquire/release syntax) where possible, but since that is often not possible, the arm64 emulation environment on Ireland)use of compiler intrinsics is more maintainable than inline assembly.#* What the platform* GCC provides intrinsics (built-specific code in functions) for atomic operations, as documented in the software doesGCC manual:*** [http://gcc.gnu.org/onlinedocs/gcc-4.9.1/gcc/_005f_005fsync-Builtins.html#* Whether portable work_005f_005fsync-Builtins Legacy __sync Built-arounds existin Functions for Atomic Memory Access]#* The need for an aarch64 port or for platform** [http://gcc.gnu.org/onlinedocs/gcc-4.9.1/gcc/_005f_005fatomic-specific code eliminationBuiltins.html#* Opportunities _005f_005fatomic-Builtins Built-in functions for optimizationmemory model aware atomic operations]#** The amount of work involved in porting and optimizing, and your skills Fedora project has some guidelines/recommendations for performing that work# Based on the result use of these GCC builtins:*** http://fedoraproject.org/wiki/Architectures/ARM/GCCBuiltInAtomicOperations* Select your investigation, decide on your interest in the project.(s):** Criteria:**#Interest* If you wish to choose this project for yourself, place it on your row in the [[Winter 2014 SPO600 Participants|Participants]] page.*# Scope**#* If you do not wish to choose this Fit between your skills and project, remove your name from the "Claimed by" column in the [[Winter 2014 SPO600 Software List|Software List]] page.needs**# Repeat until you have two packagesUpstream status (e.g., dead project)
{{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.}}=== Week 7 Deliverables ===
{{Admon# Select at least two software packages from the [http://performance.linaro.org Linaro performance web site] and/tipor the [[Fall 2014 SPO600 Packages by Participant|RPM Packages]] page.# Record your choice on:## The [[Fall 2014 SPO600 Participants|For sofware Participants page]] - so that is present your colleagues in class know that you're working on the rpmfusion repositories but not in Fedora, you can use <code>yumdownloader --source package(s). '''Note:'packagename''<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:/code> to grab /performance.linaro.org Linaro performance web site] - this will tell other people outside of our group within the source RPM and then examine it using Linux-on-ARM community that you are working on the RPM toolspackage(s). See [[RPM Packaging Process]] for information# Investigate and blog about your choice.}}
=== 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 ''Over reading week:'not''' choose particular # Contact the upstream communities for the packages, too. == Week 6 == === Tuesday (Feb 11) === * Architectureyou have selected --specific code for Performance** Sometimes assembler is used in so that they know that you are working on the package and to open a C/C++ program channel of communication for performance. However, modern versions of C/C++ your forthcoming patches (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, 3DNowor benchmarks, or AltaVec on various processorsother results).** Linaro enginener Matthew Gretton-Dann gave # Formulate 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 work plan that will conclude with landing your software changes in the presentation above, Matthew takes upstream software before 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 end 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.7course. === 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 work plan and maintain the software what you have selected need to work on. Figure out how they are structured, how they communicate, how code is maintained, and how patches are accepted. Introduce yourself investigate/learn in order to each of the two communities (one for each of the two software projects you have selected). Blog about complete your findingsproject. == 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 11Oct 28) ===* 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 Working with the Foundation ModelCode** [[:fedora:Architectures/ARM/AArch64/QuickStart|Fedora AArch64 Quick Start]]** [http://www.linaro.org/engineering/engineering-projects/armv8 Linaro Foundation Model Instructions]Working with GIT* Baseline BenchmarkingWorking with other version control systems
==== Resources ====* Foundation Model** [http://www.arm.com/products/tools/models/fast-models/ ARM Fast Models] - Note that "fast" here refers to Looking at How Distributions Package the modelling approach, not execution speed!* BenchmarkingCode** [http://www.tokutek.com/wp-content/uploads/2013/05/20130424-percona-live-benchmarking.pdf Benchmarking Talk by Tim Callaghan]Using fedpkg
=== Week 9 Deliverables Friday (Oct 31) ===* Set up the Foundation Model* Upstream your proposed code changes* Blog about your work == Week 10 ==Benchmarking and Profiling
=== Tuesday (March 18) ===
* 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/>
