From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] replacing 9load
Date: Mon, 5 Dec 2005 16:21:24 -0500 [thread overview]
Message-ID: <ee9e417a0512051321jedf70c6l44333da435be6a69@mail.gmail.com> (raw)
In-Reply-To: <4394AAFF.50207@lanl.gov>
> I would ask people to consider looking at what we finally had to do in
> linuxbios, which is to put an x86 emulator. derived from the X11 x86
> emulator, into a driver. This works really well. You can catch evil
> things that the vga bios tries to do, and make them less evil. Also,
> such a driver would go in port/, not pc/. Just a thought.
This is way more code than doing vm86, though vm86 is gone on amd64,
so maybe it's necessary. I tried doing this years ago with a home-grown
x86 simulator, and it didn't seem to run fast enough to appease the
hardware.
> But, long term, the approach of replacing 9load with plan9 sure makes a
> lot of sense. Is it possible some day that 9fat could go away, and we
> just load a kernel off of fossil? Just wondering.
Sure. That could happen today if someone wrote the fossil
and venti parsing code for 9load.
Russ
next prev parent reply other threads:[~2005-12-05 21:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 20:47 Russ Cox
2005-12-05 20:52 ` William Josephson
2005-12-05 21:02 ` Ronald G Minnich
2005-12-05 21:06 ` Charles Forsyth
2005-12-05 23:22 ` Ronald G Minnich
2005-12-05 21:21 ` Russ Cox [this message]
2005-12-05 23:27 ` Ronald G Minnich
2005-12-05 23:33 ` Russ Cox
2005-12-06 0:19 ` Ronald G Minnich
-- strict thread matches above, loose matches on Subject: below --
2005-12-04 4:48 [9fans] Replacing 9load Uriel
2005-12-04 7:01 ` jmk
2005-12-04 16:00 ` Russ Cox
2005-12-04 16:56 ` Nigel Roles
2005-12-04 19:07 ` Charles Forsyth
2005-12-04 19:29 ` jmk
2005-12-04 22:13 ` C H Forsyth
2005-12-05 19:42 ` David Leimbach
2005-12-05 20:11 ` jmk
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=ee9e417a0512051321jedf70c6l44333da435be6a69@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).