From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 386
Date: Sun, 30 Oct 2005 17:56:54 -0500 [thread overview]
Message-ID: <e01c1aafa710d7af0edd26169e7988d7@plan9.bell-labs.com> (raw)
In-Reply-To: <9ab217670510301315n3ac47987l@mail.gmail.com>
Sorry, I rounded the effect down. You get to remove the
following from the kernel if you drop the 386:
{ 3, -1, 32, "386", }, /* family defaults */
and
if(X86FAMILY(m->cpuidax) == 3)
conf.copymode = 1;
and to simplify this:
if(read && conf.copymode == 0 && s->ref == 1) {
but you get to add code to check and whine if you try to
run the kernel on a 386.
On Sun Oct 30 16:16:32 EST 2005, devon.odell@gmail.com wrote:
> 2005/10/30, jmk@plan9.bell-labs.com <jmk@plan9.bell-labs.com>:
> > On Sun Oct 30 15:34:52 EST 2005, devon.odell@gmail.com wrote:
> > > ...
> > > My understanding of how this got into the embedded chipset stuff was
> > > that a suggestion was made to deprecate 486 as well, which I don't
> > > think we should do at all. Get rid of 386, support 486+.
> > > ...
> >
> > If you keep the 486 then there is no point in removing the 386,
> > you would gain nothing.
>
> Huh? I thought we would gain the use of the page invalidation instruction?
next prev parent reply other threads:[~2005-10-30 22:56 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 [this message]
2005-10-31 0:20 ` Ronald G Minnich
2005-10-31 0:49 ` Russ Cox
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=e01c1aafa710d7af0edd26169e7988d7@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.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).