From: Anders Larsen <anders@alarsen.net>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is it useful to support user level drivers
Date: Fri, 22 Jun 2001 02:30:48 +0200 [thread overview]
Message-ID: <3B3291CE.7BAF5BC3@alarsen.net> (raw)
In-Reply-To: <Pine.LNX.3.95.1010621193107.6383A-100000@chaos.analogic.com>
"Richard B. Johnson" wrote:
>
> QNX does not have any difference between user-space and kernel space.
> It's not paged-virtual. It's just one big sheet of address space
> with no memory protection (everything is shared). All procedures
> to be executed are known at compile time.
That's completely, utterly untrue.
QNX does indeed sport paged-virtual memory with memory protection;
(although QNX4 does not support swap).
User-mode interrupts are standard procedure; the deadlock problems
Alan has mentioned do not apply, since any running process is
always resident in memory.
Shared regions have to be explicitly created; access is *not* open
to anybody.
Nothing has to be known at "compile time"; QNX is a full-featured
OS with dynamic loading.
> Therefore, any piece of code can do anything it wants including
> handling hardware directly.
Again not true; only privileged processes can enter kernel mode
to execute port I/O instructions directly.
cheers
Anders
--
"In theory there is no difference between theory and practice.
In practice there is." - Yogi Berra
next prev parent reply other threads:[~2001-06-22 0:32 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.993156181.18994.linux-kernel2news@redhat.com>
2001-06-21 22:06 ` Is it useful to support user level drivers Pete Zaitcev
2001-06-21 22:20 ` David S. Miller
2001-06-21 23:09 ` Mike Mackovitch
2001-06-21 23:22 ` David S. Miller
2001-06-21 23:50 ` Mike Mackovitch
2001-06-22 0:36 ` David S. Miller
2001-06-21 23:40 ` Richard B. Johnson
2001-06-22 0:30 ` Anders Larsen [this message]
2001-06-22 0:43 ` Richard B. Johnson
2001-06-25 0:06 ` Anders Larsen
2001-06-21 10:41 Balbir Singh
2001-06-21 10:55 ` Tim Waugh
2001-06-21 11:04 ` Alan Cox
2001-06-21 12:43 ` Balbir Singh
2001-06-21 13:27 ` Alan Cox
2001-06-28 22:52 ` Pavel Machek
2001-06-21 12:45 ` Dmitry A. Fedorov
2001-06-21 13:24 ` Oliver Neukum
2001-06-21 14:46 ` Dmitry A. Fedorov
2001-06-21 15:19 ` Oliver Neukum
2001-06-22 4:19 ` Dmitry A. Fedorov
2001-06-22 7:28 ` Balbir Singh
2001-06-21 16:34 ` Abramo Bagnara
2001-06-21 17:27 ` Alan Cox
2001-06-21 19:59 ` Abramo Bagnara
2001-06-21 20:40 ` Richard B. Johnson
2001-06-21 20:54 ` Abramo Bagnara
2001-06-21 21:09 ` Oliver Neukum
2001-06-28 22:57 ` Pavel Machek
2001-06-21 13:28 ` Alan Cox
2001-06-21 14:03 ` Matthias Urlichs
2001-06-28 22:54 ` Pavel Machek
2001-06-21 14:20 ` Dmitry A. Fedorov
2001-06-21 11:38 ` Dmitry A. Fedorov
2001-06-21 13:50 ` john slee
2001-06-21 13:58 ` Matthias Urlichs
2001-06-21 14:21 ` john slee
2001-06-28 22:51 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B3291CE.7BAF5BC3@alarsen.net \
--to=anders@alarsen.net \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.