From: Doug McNaught <doug@wireboard.com>
To: Riley Williams <rhw@MemAlpha.cx>
Cc: Pavel Machek <pavel@suse.cz>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: Linux updates RTC secretly when clock synchronizes
Date: 10 Nov 2001 15:49:01 -0500 [thread overview]
Message-ID: <m3g07mpd1e.fsf@belphigor.mcnaught.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0111102030150.12260-100000@Consulate.UFP.CX>
In-Reply-To: Riley Williams's message of "Sat, 10 Nov 2001 20:35:34 +0000 (GMT)"
Riley Williams <rhw@MemAlpha.cx> writes:
> Hi Pavel.
>
> > It ... just is not that way. Kernel + modules run at ring 0,
> > userland at ring 3.
>
> I know that much. I was just curious whether there was any particular
> reason why it was that way.
Well, Unix has historically run on systems with at most two processor
privilege levels, "user" and "supervisor"; ie, you're either in user
or kernel mode.
ix86 is one of the few Linux platforms that offers more than two
levels, so having modules run in an in-between level would be a
portability headache as well as a lot of work.
Certainly not impossible, but you'd need to create task gates or
whatever they're called at every point where modules called into the
kernel (and vice versa as well I think). Might be a serious
performance hit...
-Doug
--
Let us cross over the river, and rest under the shade of the trees.
--T. J. Jackson, 1863
next prev parent reply other threads:[~2001-11-10 20:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 0:33 PROBLEM: Linux updates RTC secretly when clock synchronizes Ian Maclaine-cross
2001-10-31 1:05 ` Kurt Roeckx
2001-10-31 2:55 ` Ian Maclaine-cross
2001-10-31 11:52 ` Kurt Roeckx
2001-11-01 0:52 ` Riley Williams
2001-11-01 1:26 ` Kurt Roeckx
2001-11-01 13:57 ` Alex Bligh - linux-kernel
2001-11-02 9:50 ` Riley Williams
2001-11-03 11:41 ` Alex Bligh - linux-kernel
2001-11-03 18:35 ` Riley Williams
2001-11-03 19:19 ` Alex Bligh - linux-kernel
2001-11-03 21:04 ` Kurt Roeckx
2001-11-06 10:01 ` Pavel Machek
2001-11-06 9:57 ` Pavel Machek
2001-11-02 12:16 ` Pavel Machek
2001-11-05 23:08 ` Riley Williams
2001-11-06 10:17 ` Pavel Machek
2001-11-07 0:00 ` Riley Williams
2001-11-07 0:44 ` Alex Bligh - linux-kernel
2001-11-07 1:01 ` Kurt Roeckx
2001-11-07 1:15 ` Alex Bligh - linux-kernel
2001-11-07 9:24 ` Russell King
2001-11-08 12:26 ` Pavel Machek
2001-11-08 23:00 ` Riley Williams
2001-11-09 9:32 ` Pavel Machek
2001-11-09 21:11 ` Riley Williams
2001-11-09 21:30 ` Pavel Machek
2001-11-09 22:54 ` Riley Williams
2001-11-09 23:10 ` Mark Zealey
2001-11-10 20:04 ` Pavel Machek
2001-11-10 20:35 ` Riley Williams
2001-11-10 20:43 ` Pavel Machek
2001-11-10 20:49 ` Doug McNaught [this message]
2001-11-06 0:20 ` Ian Maclaine-cross
2001-11-06 10:18 ` Pavel Machek
2001-11-08 5:09 ` Ian Maclaine-cross
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=m3g07mpd1e.fsf@belphigor.mcnaught.org \
--to=doug@wireboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rhw@MemAlpha.cx \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox