summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGuruprasad Aphale <guru@koruna.cs.unc.edu>2010-05-18 16:59:51 -0400
committerGuruprasad Aphale <guru@koruna.cs.unc.edu>2010-05-18 16:59:51 -0400
commitae5c6554d5c5d38f45820171fc069030b16b54f4 (patch)
treebb1273b17c56180327e9246a27a14606c6c66a22
parentbaf295e0bba71d8c396e71c0eac489751b1ab3a5 (diff)
Updated the scons section and added -h option.
Also included publication section
-rw-r--r--index.html71
1 files changed, 58 insertions, 13 deletions
diff --git a/index.html b/index.html
index 6961509..bb6c026 100644
--- a/index.html
+++ b/index.html
@@ -63,8 +63,8 @@
63 <p> 63 <p>
64 Please refer to the <a href="#download">download</a> and <a href="#install">installation</a> sections for details. 64 Please refer to the <a href="#download">download</a> and <a href="#install">installation</a> sections for details.
65 </p> 65 </p>
66 <p>Earlier versions based on Linux &nbsp;2.6.24 and Linux&nbsp;2.6.20, 66 <p>Earlier versions (2008.1 &mdash 2008.3),based on Linux &nbsp;2.6.24 and (2007.1 &mdash; 2007.3), based on Linux&nbsp;2.6.20
67 which supported additional scheduling policies, are discussed on separate pages dedicated to the <a href="litmus2007.html">LITMUS<sup>RT</sup> 2008</a> and <a href="litmus2007.html">LITMUS<sup>RT</sup> 2007 </a> series respectively. 67 ,support additional scheduling policies, are discussed on separate pages dedicated to the <a href="litmus2007.html">LITMUS<sup>RT</sup> 2008</a> and <a href="litmus2007.html">LITMUS<sup>RT</sup> 2007 </a> series respectively.
68 </p> 68 </p>
69 <p class="nobottommargin"> 69 <p class="nobottommargin">
70 The first version of LITMUS<sup>RT</sup>, which was implemented in Spring 2006, 70 The first version of LITMUS<sup>RT</sup>, which was implemented in Spring 2006,
@@ -76,9 +76,9 @@
76 <h2 id="support">Support</h2> 76 <h2 id="support">Support</h2>
77 <div class="box"> 77 <div class="box">
78 <p class="nomargin"> 78 <p class="nomargin">
79 The LITMUS<sup>RT</sup> development effort is being supported by grants from 79 The LITMUS<sup>RT</sup> development effort is being supported by grants from, SUN Corp.,
80 AT&amp;T, IBM, and Northrop Grumman Corps.; the National Science Foundation (grants CNS 0834270 and CNS 0834132); the U.S. 80 Intel Corp., IBM Corp., The National Science Foundation (grant CCR 0615197), and The U.S.
81 Army Research Office (grant W911NF-09-1-0535); and the Air Force Office of Scientific Research (grant FA 9550-09-1-0549). 81 Army Research Office (grant W911NF-06-1-0425).
82 </p> 82 </p>
83 </div> 83 </div>
84 84
@@ -97,18 +97,17 @@
97 <li> 97 <li>
98 <a href="http://www.cs.unc.edu/~bbb/">Bj&ouml;rn B. Brandenburg</a> (current maintainer) 98 <a href="http://www.cs.unc.edu/~bbb/">Bj&ouml;rn B. Brandenburg</a> (current maintainer)
99 </li> 99 </li>
100 <li> <a href="http://www.sprg.uniroma2.it/home/bastoni/">Andrea Bastoni</a> (University of Rome "Tor Vergata") 100 <li> <a href="http://www.sprg.uniroma2.it/home/bastoni/">Andrea Bastoni</a> (Visiting researcher from University of Rome "Tor Vergata")
101 </li> 101 </li>
102 </ul> 102 </ul>
103 <p class="nobottommargin"> 103 <p class="nobottommargin">
104 Additional collaborators contributed to the previous <a href="litmus2008.html#collaborators">LITMUS<sup>RT</sup> 2008</a> and the <a href="litmus2007.html#collaborators">LITMUS<sup>RT</sup> 2007</a> versions. 104 (Additional collaborators for <a href="litmus2008.html#collaborators">LITMUS<sup>RT</sup> 2008 series</a> and <a href="litmus2007.html#collaborators">LITMUS<sup>RT</sup> 2007 series</a> contributed to earlier versions of LITMUS<sup>RT</sup>.)
105 </p> 105 </p>
106 </div> 106 </div>
107 107
108 108
109 <h2 id="publications">Publications</h2> 109 <h2 id="publications">Publications</h2>
110 <div class="box"> 110 <div class="box">
111
112 <ol class="nomargin"> 111 <ol class="nomargin">
113 <li><p> 112 <li><p>
114 B. Brandenburg and J. Anderson, 113 B. Brandenburg and J. Anderson,
@@ -331,7 +330,7 @@ Technology and Applications Symposium</cite>, pp. 342-353, April 2008.
331 model, a scheduler plugin infrastructure, and some scheduler plugins, as 330 model, a scheduler plugin infrastructure, and some scheduler plugins, as
332 well as a user-space library that provides the LITMUS<sup>RT</sup> 331 well as a user-space library that provides the LITMUS<sup>RT</sup>
333 real-time API. Note that the current implementation only works on the 332 real-time API. Note that the current implementation only works on the
334 Intel x86-32 and x86-64 architectures. 333 Intel x86-32 and sparc64 architectures.
335 </p> 334 </p>
336 <h3>Patching the Kernel</h3> 335 <h3>Patching the Kernel</h3>
337 <p class="notopmargin"> 336 <p class="notopmargin">
@@ -380,14 +379,60 @@ make modules
380 depends on the LITMUS<sup>RT</sup> kernel kernel and provides its own build system (based on <a href="http://www.scons.org/">scons</a>). 379 depends on the LITMUS<sup>RT</sup> kernel kernel and provides its own build system (based on <a href="http://www.scons.org/">scons</a>).
381 In order to compile <span class="src">liblitmus</span>, you need to adjust the 380 In order to compile <span class="src">liblitmus</span>, you need to adjust the
382 variable <span class="src">LITMUS_KERNEL</span> in the <span class="src">SConstruct</span> file to point to your 381 variable <span class="src">LITMUS_KERNEL</span> in the <span class="src">SConstruct</span> file to point to your
383 copy of the kernel. 382 copy of the kernel. Users should not update the <span class="src">SConstruct</span> file manually anymore. Instead, a <span class="src">.config</span> file can be created with appropriate variables. The required variables can be listed using <span class="src"> scons -h </span> command. This command lists the variables required for building the <span class="src"> liblitmus2010 </span> library. <br>
383 Sample output of <span class="src"> scons -h </span> is as shown below.
384 </p> 384 </p>
385 <p>
386 <pre class="shell">
387scons -h
388scons: Reading SConscript files ...
389scons: done reading SConscript files.
390
391=============================================
392liblitmus --- The LITMUS^RT Userspace Library
393
394There are a number of user-configurable build
395variables. These can either be set on the
396command line (e.g., scons ARCH=x86) or read
397from a local configuration file (.config).
398
399Run 'scons --dump-config' to see the final
400build configuration.
401
402Build Variables
403---------------
404
405LITMUS_KERNEL: Where to find the LITMUS^RT kernel. ( /path/to/LITMUS_KERNEL )
406 default: ../litmus2010
407 actual: ../litmus2010
408
409PYTHON_HEADERS: Where to find Python headers. ( /path/to/PYTHON_HEADERS )
410 default: /usr/include/python2.5
411 actual: /usr/include/python2.5
412
413ARCH: Target architecture. (x86_64|sparc64|x86|i686)
414 default: x86_64
415 actual: x86_64
416
417WSS: Working set size for pm analysis
418 default: 3072
419 actual: 3072
420
421Use scons -H for help about command-line options.
422 </pre>
423
424<p class="notopmargin">
425 To summarize, the <span class="src"> liblitmus </span> can be obtained and
426 compiled with the following commands:
427</p>
428
385<pre class="shell"> 429<pre class="shell">
386cd $DIR 430cd $DIR
387wget http://www.cs.unc.edu/~anderson/litmus-rt/download/2010.1/liblitmus-2010.1.tgz 431wget http://www.cs.unc.edu/~anderson/litmus-rt/download/2010.1/liblitmus-2010.1.tgz
388tar xzf liblitmus-2010.1.tgz 432tar xzf liblitmus-2010.1.tgz
389cd liblitmus 433cd liblitmus
390# change LITMUS_KERNEL in SConstruct to point to the kernel source 434
435# set LITMUS_KERNEL in .config to point to the kernel source and compile
391scons 436scons
392</pre> 437</pre>
393 <p class="nobottommargin"> 438 <p class="nobottommargin">
@@ -447,7 +492,7 @@ scons
447 Only root can change the active policy, and only when there are no real-time tasks present. 492 Only root can change the active policy, and only when there are no real-time tasks present.
448 </p> 493 </p>
449 <p> 494 <p>
450 If you do not have the <span class="src">dialog</span> utility installed, then you can still used <span class="src">setsched</span> by passing the desired scheduling policy as a commandline parameter, <em>e.g.</em> type <span class="src"> setsched PFAIR </span> to activate the PFAIR plugin. 495 If you do not have the <span class="src">dialog</span> utility installed, then you can still use <span class="src">setsched</span> by passing the desired scheduling policy as a commandline parameter, <em>e.g.</em> type <span class="src"> setsched PFAIR </span> to activate the PFAIR plugin.
451 </p> 496 </p>
452 <h3>Writing Real-Time Tasks</h3> 497 <h3>Writing Real-Time Tasks</h3>
453 <p class="qa"> 498 <p class="qa">