9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] 386
Date: Sun, 30 Oct 2005 19:49:03 -0500	[thread overview]
Message-ID: <ee9e417a0510301649pff0f722ref6e39d3ff8e9191@mail.gmail.com> (raw)
In-Reply-To: <4365633A.1070005@lanl.gov>

On reflection it's just not that hard to write a C invlpg
that calls putcr3 if it's running on a 386.  We use
LOCK INCL to do ref counts so that it works on the 386,
we never use BSWAP, and we use CR0.WP by checking
the cpuid.

For actually running a system, VMware and Qemu are
pretty much neck and neck and Bochs is far behind.

For debugging a system, Bochs is slightly ahead of
Qemu and VMware is far behind.  Bochs has a reasonable
debugger interface that knows about 16-bit mode and
segments and offsets and page tables and everything.
Qemu is much faster but has no debugger.  You can attach
to it with gdb but gdb only knows about 32-bit mode user-level
sorts of things, so usually I have to set a break point using gdb
and then dump register info back at qemu's console.
I lost count of the number of times one or the other got me out
of a jam while I was writing the new VM code or the realmode
code that made vesa-in-the-kernel possible.

Russ


  reply	other threads:[~2005-10-31  0:49 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29 15:08 Russ Cox
2005-10-29 15:26 ` Lucio De Re
2005-10-29 19:07 ` William Josephson
2005-10-29 20:01   ` jmk
2005-10-29 20:06     ` Lucio De Re
2005-10-29 21:07     ` Uriel
2005-10-29 21:18       ` jmk
2005-10-29 21:51     ` Ronald G Minnich
2005-10-29 22:31       ` Francisco J Ballesteros
2005-10-30  0:50         ` Ronald G Minnich
2005-10-30  5:41           ` Jack Johnson
2005-10-30 16:15             ` Ronald G Minnich
2005-10-30 20:02             ` jmk
2005-10-30 20:12               ` Uriel
2005-10-30 20:34                 ` Devon H. O'Dell
2005-10-30 20:52                   ` jmk
2005-10-30 21:15                     ` Devon H. O'Dell
2005-10-30 22:56                       ` jmk
2005-10-31  0:20                         ` Ronald G Minnich
2005-10-31  0:49                           ` Russ Cox [this message]
2005-10-31 21:26                             ` Dave Eckhardt
2005-10-30 21:27                     ` Mike Haertel
2005-10-31 10:06                       ` Charles Forsyth
2005-10-30 22:11                     ` Ronald G Minnich
2005-10-30 21:16                       ` Francisco J Ballesteros
2005-10-30 21:53               ` Ronald G Minnich
2005-10-29 23:45       ` John DeGood
2005-10-30  0:04         ` William Josephson
2005-10-30 12:59       ` Brantley Coile
2005-10-30  1:14     ` geoff
2005-10-29 20:22 ` Christopher Nielsen

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=ee9e417a0510301649pff0f722ref6e39d3ff8e9191@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).