JAVA-BASED REAL-TIME PROGRAMMING

More documents

Recommendations

Info

4. Exercises and Labs Getting approved To pass you need to show your solution to the lab supervisor. You should be able to explain what you have done and motivate your implementation. A working Java solution free of real-time problems is compulsory. Common problems that need to be fixed are race conditions (the washing machine burns up, etc.), potential data corruption and excessive use of CPU. You must use mailboxes for thread communication in your solution. Other primitives, such as semaphores and monitors are not allowed. Miscellaneous OwnerError The OwnerError is thrown when a putEvent (or similar) is called within a RTThread object using a different thread than the one associated with the object. Typically you get this error when starting washing programs using program.wash() instead of program.start() within WashingController .process- Button(), i.e. you let the simulation thread run the washing program instead of starting a new washing program thread. 140 2012-08-29 16:05
Chapter 5 Solutions 5.1 Solution to exercise 1 1. A sequence of calls to Java:s System.out needs to be in critical section. Import the package se.lth.cs.realtime.semaphore, and within your class you declare the attribute: Semaphore sysoutLock; which is instantiated and initialized to one (in the constructor of the class) by one of the following lines: sysoutLock = new MutexSem(); // Preferred! sysoutLock = new CountingSem (1); // Works in simple cases. (sysoutLock = new CountingSem ()).give(); // Dito., less readable. Then, on each place where print is called, the statements must be enclosed by take and give according to sysoutLock.take(); // Start of critical section System.out.print(someStuff); System.out.print(moreStuff); // .... System.out.println(finalStuff); sysoutLock.give(); // End of critical section Of course, all functions using System.out have to follow this convention; take and give using the very same semaphore instance. Using a MutexSem, the run-time systems can check during give that the same thread first has called take. 141
Page 1:
JAVA-BASED REAL-TIME PROGRAMMING Kl
Page 4 and 5:
• Each piece of software must be
Page 7 and 8:
Contents I Concurrent programming i
Page 9:
Part I Concurrent programming in Ja
Page 12 and 13:
1. Introduction pany depends on the
Page 14 and 15:
1. Introduction control may be dela
Page 17 and 18:
Chapter 2 Fundamentals Goal: Review
Page 19 and 20:
2.2. Our physical world is parallel
Page 21 and 22:
2.4. Concurrency a trend that the p
Page 23 and 24:
2.4. Concurrency Behind the term co
Page 25 and 26:
2.4. Concurrency in functions like
Page 27 and 28:
2.5. Interrupts, pre-emption, and r
Page 29 and 30:
2.5. Interrupts, pre-emption, and r
Page 31 and 32:
2.6. Models of concurrent execution
Page 33 and 34:
Object properties Implicit mutual e
Page 35 and 36:
2.6. Models of concurrent execution
Page 37 and 38:
2.7 Multi-process programming 2.7.
Page 39 and 40:
2.9. Software issues In this chapte
Page 41 and 42:
Chapter 3 Multi-Threaded Programmin
Page 43 and 44:
3.1.1 Thread creation At start of a
Page 45 and 46:
to foresee the value actually retur
Page 47 and 48:
3.1. Threads first obtains the curr
Page 49 and 50:
the run-time system (that is, the s
Page 51 and 52:
3.1.6 Thread interruption and termi
Page 53 and 54:
• If the operation of an industri
Page 55 and 56:
3.2. Resources and mutual exclusion
Page 57 and 58:
Page 59 and 60:
give give give 3.2. Resources and m
Page 61 and 62:
synch. T1 entry give take 3.2. Reso
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
class Account { int balance; Semaph
Page 69 and 70:
3.3. Objects providing mutual exclu
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
class Producer extends Thread { pub
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
3.4 Message-based communication - M
Page 87 and 88:
3.4.2 Events and buffers 3.4. Messa
Page 89 and 90: Real-Time Events - RTEvent 3.4. Mes
Page 91 and 92: 3.4. Message-based communication -
Page 93 and 94: RTEvent post(RTEvent e) final void
Page 95 and 96: 3.4. Message-based communication -
Page 97: 3.4. Message-based communication -
Page 100 and 101: 4. Exercises and Labs 4. In the pro
Page 102 and 103: 4. Exercises and Labs /** * The buf
Page 104 and 105: 4. Exercises and Labs object and gi
Page 106 and 107: 4. Exercises and Labs Excerpt from
Page 108 and 109: 4. Exercises and Labs 4.3 Lab 1 - A
Page 110 and 111: 4. Exercises and Labs Some advice o
Page 112 and 113: 4. Exercises and Labs 4.4 Exercise
Page 114 and 115: 4. Exercises and Labs • CustomerH
Page 116 and 117: 4. Exercises and Labs 4.5 Exercise
Page 118 and 119: 4. Exercises and Labs Lab 2 prepara
Page 120 and 121: 4. Exercises and Labs } /** Draws a
Page 122 and 123: 4. Exercises and Labs public static
Page 124 and 125: 4. Exercises and Labs Specification
Page 126 and 127: 4. Exercises and Labs /** * Turns t
Page 128 and 129: 4. Exercises and Labs your washing
Page 130 and 131: 4. Exercises and Labs } } super(mac
Page 132 and 133: 4. Exercises and Labs } /** * @retu
Page 134 and 135: 4. Exercises and Labs PeriodicThrea
Page 136 and 137: 4. Exercises and Labs Miscellaneous
Page 138 and 139: 4. Exercises and Labs Scheduling wi
Page 142 and 143: 5. Solutions 2. With some additiona
Page 144 and 145: 5. Solutions 5.2 Solution to exerci
Page 146 and 147: 5. Solutions class YourMonitor { pr
Page 148 and 149: 5. Solutions 5.4 Solution to exerci
Page 150: 5. Solutions b) After the rewriting
show all

JAVA-BASED REAL-TIME PROGRAMMING

Create successful ePaper yourself

Delete template?

Save as template?