From: Pavel Machek <pavel@ucw.cz>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Brian Gerst <bgerst@didntduck.org>,
willy@w.ods.org, arjanv@redhat.com, hch@lst.de, akpm@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: i486 emu in mainline?
Date: Thu, 27 May 2004 23:03:46 +0200 [thread overview]
Message-ID: <20040527210346.GC997@openzaurus.ucw.cz> (raw)
In-Reply-To: <E1BS5V8-0006d6-00@gondolin.me.apana.org.au>
Hi!
> >> It was intentional for speed purpose. The areas are checked once with
> >> verify_area() when we need to access memory, then data is copied directly
> >> from/to memory. I don't think there's any risk, but I can be wrong.
> >
> > Which will break with 4G/4G. You must use at least __get_user().
>
> A 386 with a 4G/4G split, I'd like to see that.
I believe you could...
1) some 586 class machines do not know 486 opcodes
2) this is for rescue kernel. If you want to be able to rescue 64GB machine *and* rescue 486 too,
this+4G/4G is right choice ;-)
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2004-05-31 13:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-22 23:40 i486 emu in mainline? Christoph Hellwig
2004-05-23 0:20 ` Rene Rebe
2004-05-23 7:13 ` Arjan van de Ven
2004-05-23 8:44 ` Willy Tarreau
2004-05-23 9:13 ` Arjan van de Ven
2004-05-23 9:48 ` Willy Tarreau
2004-05-23 9:58 ` Arjan van de Ven
2004-05-23 11:49 ` Helge Hafting
2004-05-23 9:20 ` Andrew Morton
2004-05-23 17:11 ` Brian Gerst
2004-05-24 2:47 ` Herbert Xu
2004-05-27 21:03 ` Pavel Machek [this message]
2004-05-23 8:29 ` Willy Tarreau
2004-05-23 11:08 ` Alan Cox
2004-05-23 11:57 ` Willy Tarreau
2004-05-23 13:15 ` Alan Cox
2004-05-24 15:17 ` Jan-Benedict Glaw
2004-05-24 17:41 ` Alan Cox
2004-05-25 9:36 ` Jan-Benedict Glaw
2004-05-25 13:48 ` Alan Cox
[not found] ` <20040523105130.GA588@samarkand.rivenstone.net>
2004-05-23 11:59 ` Willy Tarreau
2004-05-24 9:08 ` P
2004-05-23 15:18 ` Jeff Garzik
2004-05-23 21:14 ` Alan Cox
2004-05-24 12:28 ` Maciej W. Rozycki
2004-05-25 17:21 ` Kronos
-- strict thread matches above, loose matches on Subject: below --
2004-05-25 17:03 Albert Cahalan
2004-05-25 22:43 ` Alan Cox
2004-10-10 20:33 Nathanael Nerode
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=20040527210346.GC997@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--cc=bgerst@didntduck.org \
--cc=hch@lst.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.org \
/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.