From 11c1519a12cdae1ce05d31a6e389a103259c6c93 Mon Sep 17 00:00:00 2001 From: manuel Date: Mon, 26 Mar 2012 20:18:23 +0200 Subject: first timer alarm implementation --- proj0.txt | 23 +++++++++++++++++++---- 1 file changed, 19 insertions(+), 4 deletions(-) (limited to 'proj0.txt') diff --git a/proj0.txt b/proj0.txt index d77cdb9..8cdfb49 100644 --- a/proj0.txt +++ b/proj0.txt @@ -3,14 +3,14 @@ | PROJECT 0: INTRO | | DESIGN DOCUMENT | +--------------------+ - + ---- GROUP ---- >> Fill in the names and email addresses of your group members. -FirstName LastName -FirstName LastName -FirstName LastName +Peter Ketscher +Karoline Koth +Manuel Mausz ---- PRELIMINARIES ---- @@ -21,6 +21,7 @@ FirstName LastName >> preparing your submission, other than the Pintos documentation, course >> text, lecture notes, and course staff. +TODO ALARM CLOCK =========== @@ -30,27 +31,41 @@ FirstName LastName >> `struct' member, global or static variable, `typedef', or >> enumeration. Identify the purpose of each in 25 words or less. +struct thread: +int64_t alarm_tick ...absolute tick when to trigger an alarm event + ---- ALGORITHMS ---- >> A2: Briefly describe what happens in a call to timer_sleep(), >> including the effects of the timer interrupt handler. +TODO + >> A3: What steps are taken to minimize the amount of time spent in >> the timer interrupt handler? +TODO + ---- SYNCHRONIZATION ---- >> A4: How are race conditions avoided when multiple threads call >> timer_sleep() simultaneously? +TODO + >> A5: How are race conditions avoided when a timer interrupt occurs >> during a call to timer_sleep()? +We've disabled the interrupts during list operations. + ---- RATIONALE ---- >> A6: Why did you choose this design? In what ways is it superior to >> another design you considered? +It's very simple, doesn't require any complex structures and memory allocations +and fulfills the needs of project0. + ARGUMENT PASSING ================ -- cgit v1.2.3