1,885
edits
Changes
→Evaluation
|-
|11||Apr 2||[[#Week 11 - Class I|Guest speaker (tentative)Project Hacking]]||[[#Week 11 - Class II|Compiler Intrinsics]]||[[#Week 11 Deliverables|Blog about your project.]]
|-
|12||Apr 9||[[#Week 12 - Class I|<strike>Project Hacking</strike> <span style="color: #ff0000"><b>Class cancelled</b></span>]]||[[#Week 12 - Class II|Project Hacking]]||[[#Week 12 Deliverables|Blog about your project.]]
|-
!Category!!Percentage!!Evaluation Dates
|-
|Communication||align="right"|20%||January (blog posts up to Feb 4, 5%), End of February (March 4, 5%), End of March (April 2, 5%), end of course (April 21 - 22, 5%).
|-
|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. All labs must be submitted by April 21, but it is best if you stay on top of the labs and submit according to the table above.
|-
|Project work||align="right"|60%||3 stages: 15% (March 18), 20% (April 810), 25% (April 2122).
|}
** Demand Loading
** Memory mapped files
=== Software Impact ===
* Alignment checks
* Page boundary crossing
=== Week 8 Delivarables ===
* Blog about your project
== Week 9 ==
=== Week 9 - Class I ===
==== 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]
** Atomics may be performed using special instructions or Kernel-compiler cooperation
==== Memory Barriers ====
* Memory encryption
=== = Building Software Impact ====* Configuration Systems** make-based systems*** [https://www.gnu.org/software/automake/manual/html_node/index.html#Top The GNU Build System: autotools, autoconf, automake]*** Configuration name ("triplet") -- ''cpu-manufacturer-operatingSystem'' or ''cpu-manufacturer-kernel-operatingSystem''**** config.guess and config.sub*** CMake*** qmake*** Meson*** iMake and Others** Non-make-based systems*** Apache Ant*** Apache Maven*** Qt Build System* Building in the Source Tree vs. Building in a Parallel Tree** Pros and Cons** [https://www.gnu.org/software/automake/manual/html_node/VPATH-Builds.html#VPATH-Builds GNU automake ''vpath'' builds]* Installing and Testing in non-system directories** Configuring installation to a non-standard directory*** Running <code>configure</code> with <code>--prefix</code>*** Running <code>make install</code> as a non-root user*** DESTDIR variable for <code>make install</code>** Runtime environment variables:*** PATH*** LD_LIBRARY_PATH and LD_PRELOAD (see the [http://man7.org/linux/man-pages/man8/ld.so.8.html ld.so manpage])** Security when running software*** Device access**** Opening a TCP/IP or UDP/IP port below 1024**** Accessing a <code>/dev</code> device entry***** Root permission***** Group permission*** SELinux Type Enforcement**** Enforcement mode***** View enforcement mode: <code>getenforce</code>***** Set enforcement mode: <code>setenforce</code>**** Changing policy***** [https://fedoraproject.org/wiki/SELinux/audit2why audit2why]* Alignment checks**** [https://fedoraproject.org/wiki/SELinux/audit2why audit2allow] === Week 9: Class II ===* Page boundary crossingPortability Issues
=== Week 8 Delivarables 9 Deliverables ===
* Blog about your project
== Week 10 ==
=== Week 10: Class I ===
* Project hacking and discussion
=== Week 10 Deliverables ===
* Blog about your project.
* Note: March blogs are due Monday, April 2. Remember that the target is 1-2 posts/week, which is 4-8 posts/month.
== Week 11 ==
=== Week 11 - Class I ===
* Project hacking and discussion
=== Week 11 - Class II ===
* [[Compiler Intrinsics]]
* Project discussion
== Week 12 ==
=== Week 12 - Class I ===
* Class cancelled
=== Week 12 - Class II ===
* Project hacking and discussion
