|-|<div style="background:#ffff00">[[Fall 2014 Current SPO600 Weekly Schedule|Weekly Schedule]]</div>[[Fall 2014 Current SPO600 Participants|Participants and Project Table]]<br />[httphttps://wwwtelescope.cdot.systems Telescope]<br />[https://ict.senecacollege.ca/ssos/findWithoutSemestercourse/spo600/sict Course Outline]<br />[[media:SPO600 Course PoliciesWinter 2022 addendum.pdf|Course PoliciesWinter 2022 Addendum]]<br />[http://linaro.org Linaro[SPO600 Course Policies|Course Policies]<br />[http://zenit.senecac.on.ca/~chris.tyler/planet/ Planet CDOT]<br />

<!--{{Admon/tip|Who can take this course?|This course is open to both '''CTY''' (system and network administration) and '''CPA''' (software development) students. Each group brings unique but overlapping skills: CTY students have a strong understanding Thinking of operating systems and administrative procedures, and CPA students have a strong understanding of programming. This course provides a range of project opportunities requiring different combinations of skills from each program of study.}} {{Admon/tip|Why take taking this course?|In this course, you'll learn about the internal details of computer architecture and the lowest levels of programming [[SPO600 - the instructions that a compiler produces from your code. You'll also learn how to port code to work on a new architecture (or on a range of architectures), benchmark software performance, improve software performance by changing the code or the way it is built, and debug code. This Information for Prospective Students|Here is a project-based course, and you will gain experience working directly with one or more open source communities on software that is in everyday use.<br /><br />After completing this course, you will understand the fundamentals of computer architecture and operation and be able to build and/or write software that performs well, work with multiple computer architectures, and participate in open source projects. This is a challenging course but it should be rewarding some information for prospective students interested in the details of computer architecture and software optimization.}} {{Admon/note|Questions about SPO600?|Please contact Professor [[User:Chris Tyler|Chris Tyler]] (via email at [mailto:chris.tyler@senecacollege.ca chris.tyler@senecacollege.ca]).}}--> 

Software is sometimes written to work on a specific computer architecture (type of computer), such as on Intel-compatible x86_64 PCs, or IBM Z9 Z-series mainframes. This course is about bringing software to a new architecture. This course deals with the challenge of making software compatible with a new architecture in one of two ways:

== SPO600 in Fall 2014 2023 ==

In SPO600, you'll be working directly with open source communities to port softwareA new computer architecture has appeared: 64-bit ARM systems (also known as "ARM64" or "AArch64"). This semester, we'll be collaborating with a project set While AArch64 is showing up by Jon "Maddog" Hall in cell phones and [http://linarotablets, it is also poised to pounce on the datacentre.org Linaro] Most of the work of porting core software to port AArch64 has been completed, and optimize software which doesn't currently at this point, just about everything that runs on x86_64 Linux systems will run on 64-bit ARM (aarch64) computersan AArch64 systems. This project However, the x86_64 architecture has identified been around 1400 for many years, and software packages has been well-optimized to work on that need work. (As a bonusarchitecture; but AArch64 is relatively new, completed projects and it may be eligible for recognition possible to get better performance with additional tuning and possibly prizes from Linaro)optimization.

In this semester, the SPO600 course will be focused on optimizing software on AArch64 systems, and specifically on building infrastructure to make it easier to use indirect functions (similar to the glibc "ifunc" capability) for runtime implementation selection. This technique is widely used in a few places -- such as in glibc, the GNU standard C library -- but it would be great if we could easily use it in other places. This would allow (for example) two versions of a particular function to be automatically compiled, with and without support for particular hardware features (such as Scalable Vector Extensions (SVE/SVE2)), and for the best version to be automatically used at runtime. Note that, unlike some other project-based courses, the results of the projects done in SPO600 will eventually be incorporated into the actual "upstream" open source projectssoftware, and have a real impact on other people. For this reason, projects must be completed in collaboration with the relevant open source communities, using relevant [[SPO600 Communication Tools|communication tools]]. Work performed in this course will be licensed using the relevant open source licenses used by the associated community.

* Course information and labs are online- no textbook is required. '''Required:'''* You '''must''' be able to [[SSH]] to [[SPO600 Servers|computer systems]] at Seneca (CDOT). You can do this using an SSH client program, included with or available for almost all platforms.* You '''must''' be able to participate in synchronous (live) streaming classes and be able to view/stream video content. <!-- '''Recommended:'''* Classes are held in an [[Active Learning Classroom]]. You '''should''' have a mobile device of some type (laptop, smartphone, tablet) with a wireless network connection (WiFi or mobile) and a video output (HDMI). If your video output is of a different type (VGA/DVI/DP/Miracast/MyDP/MiniDP/MiniHDMI/other) you will require need an appropriate adapter.* For productivity, you '''should''' have access to a personal Linux installation on a 64-bit (x86_64) computer (ideally, a fast onesee [[SPO600 Host Setup]]). This * Students in the SPO600 course may be on your own laptop, on want to purchase a large/fast virtual machine on your laptop64-bit ARM computer, on an SSH-accessible system (such as a home desktop computer), Rasbperry Pi 4 or on a SATA disk pack or USB drive for use with the Seneca computers.* You Raspberry Pi 400 -- but you will need to be able to ssh to computer systems at Seneca (CDOT)run a 64-bit operating system, such as [https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi Fedora AArch64].-->

1. '''Blog.''' Tell your professor, your colleagues, the community, and everyone else what you're doing. <u>Write a lot</u> and write well, include good technical content, and incorporate links to all relevant resources and the product of your work, and write often. Almost all of your work in this course is submitted by blogging. 2. '''Be ambitious.''' In this course, you will need to be the driving force behind your project. The community will help you, but it's up to you to supply the energy. 3. '''Work ''in'' the open source community.''' The projects we will be doing are too large and too unfamiliar for you to succeed entirely on your own. You will need to use the community's knowledge, connections, and resources to succeed well. Respect the community's standards, tell the community what you're doing, ask when you have a question, and pull your own weight within the community.

3. '''Be ambitious.''' In this course, you will need to be the driving force behind your project. The community will help you, but it's up to you to supply the energy. '''It's best to plan to make a bit of progress each day.'''

See the [[Fall 2014 Current SPO600 Weekly Schedule]] for specific dates and topics.

See the online [https://ict.senecacollege.ca/course/spo600 course outline] for course details, and the [[media:SPO600 Winter 2022 addendum.pdf|Winter 2022 Addendum]] for additional course details.