Subversion Repositories HelenOS-doc

Rev

Rev 151 | Only display areas with differences | Ignore whitespace | Details | Blame | Last modification | View Log | RSS feed

Rev 151 Rev 171
1
<?xml version="1.0" encoding="UTF-8"?>
1
<?xml version="1.0" encoding="UTF-8"?>
2
<chapter id="intro">
2
<chapter id="intro">
3
  <?dbhtml filename="intro.html" ?>
3
  <?dbhtml filename="intro.html" ?>
4
 
4
 
5
  <title>Introduction</title>
5
  <title>Introduction</title>
6
 
6
 
7
  <para>HelenOS is a portable operating system with support for a variety of modern
7
  <para>HelenOS is a portable operating system with support for a variety of
8
  processor architectures<footnote>
8
  modern processor architectures<footnote>
9
      <para>amd64, ia32, ia64, mips32 and ppc32.</para>
9
      <para>amd64, arm32, ia32, ia64, mips32, ppc32 and sparc64. ia32xen and
-
 
10
      ppc64 are currently broken.</para>
10
    </footnote>.</para>
11
    </footnote>.</para>
11
 
12
 
12
  <para>This book describes the design and principles of the HelenOS operating
13
  <para>This book describes the design and principles of the HelenOS operating
13
  system from the perspective of its microkernel as well as from the
14
  system from the perspective of its microkernel as well as from the
14
  perspective of its userspace drivers and server tasks. Its primary goal is
15
  perspective of its userspace drivers and server tasks. Its primary goal is
15
  to present ideas behind each subsystem and highlight things that are
16
  to present ideas behind each subsystem and highlight things that are
16
  specific to HelenOS. Although this text contains references to source code
17
  specific to HelenOS. Although this text contains references to source code
17
  (e.g. function names), these are provided only to improve reader's
18
  (e.g. function names), these are provided only to improve reader's
18
  orientation when reading the code. This book does not attempt to be a
19
  orientation when reading the code. This book does not attempt to be a
19
  substitute for a reference manual and the reader is strongly encouraged to
20
  substitute for a reference manual and the reader is strongly encouraged to
20
  look for interface details there.</para>
21
  look for interface details there.</para>
21
 
22
 
22
  <section>
23
  <section>
23
    <title>How to Read This Book</title>
24
    <title>How to Read This Book</title>
24
 
25
 
25
    <para><xref linkend="architecture" /> contains overview of the overall
26
    <para><xref linkend="architecture" /> contains overview of the overall
26
    HelenOS architecture.</para>
27
    HelenOS architecture.</para>
27
 
28
 
28
    <para><xref linkend="ds" /> describes essential data structures used both
29
    <para><xref linkend="ds" /> describes essential data structures used both
29
    in the kernel and in the userspace.</para>
30
    in the kernel and in the userspace.</para>
30
 
31
 
31
    <para><xref linkend="time" /> focuses on time management in the kernel and
32
    <para><xref linkend="time" /> focuses on time management in the kernel and
32
    scheds some light on the userspace source of time.</para>
33
    scheds some light on the userspace source of time.</para>
33
 
34
 
34
    <para><xref linkend="scheduling" /> is dedicated to threads and the
35
    <para><xref linkend="scheduling" /> is dedicated to threads and the
35
    scheduling subsystem.</para>
36
    scheduling subsystem.</para>
36
 
37
 
37
    <para><xref linkend="mm" /> describes memory management of physical and
38
    <para><xref linkend="mm" /> describes memory management of physical and
38
    virtual memory.</para>
39
    virtual memory.</para>
39
 
40
 
40
    <para><xref linkend="ipc" /> deals with the IPC subsystem.</para>
41
    <para><xref linkend="ipc" /> deals with the IPC subsystem.</para>
41
 
42
 
42
    <para><xref linkend="hardware" /> describes facilities that a userspace
43
    <para><xref linkend="hardware" /> describes facilities that a userspace
43
    task can use in order to become a device driver.</para>
44
    task can use in order to become a device driver.</para>
44
 
45
 
45
    <para><xref linkend="archspecs" /> presents some architecture specific
46
    <para><xref linkend="archspecs" /> presents some architecture specific
46
    issues.</para>
47
    issues.</para>
47
  </section>
48
  </section>
48
</chapter>
49
</chapter>