linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] UML patches against vanilla 2.6.0
Date: Fri, 26 Dec 2003 19:56:13 +0100	[thread overview]
Message-ID: <200312261956.13626.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20031226182737.GK2378@erdos.home>

Alle 19:27, venerdì 26 dicembre 2003, Cameron Patrick ha scritto:
> On Fri, Dec 26, 2003 at 07:05:48PM +0100, BlaisorBlade wrote:
> | Go here:
> |
> | http://web.tiscali.it/no-redirect-tiscali/blaisorblade/index.html
>
> Which says:
>
> 	The only problematic patch is A-04-MM-compile-fix.patch, but
> 	maybe i386 can live even with it (I don't remember if I got a
> 	successful compilation with it applied). However, I think it's
> 	not at all safe even if it compiles.
>
> and in the README:
>
> 	but I think you'd better avoid doing this or do a complete
> 	backup, since you'll need it...).

> Eeek!  I just upgraded my home desktop to a 2.6.0 kernel with that patch
> applied (actually as part of Jeff's 2.6.0-test9 patch) and so far it
> seems to be working.
Are you sure? If you compile a stock 2.6.0 with Jeff's 2.6.0-test9 patch and 
try to compile an i386 kernel, you'll get soon errors about 
do_mmap_pgoff(except if you applied a host-skas to your 2.6 tree).

> Looking at the patch, it seems innocuous enough -
> why should it be unsafe on an i386 kernel?

I don't know actually, but it doesn't seem innocuous.

Instead, FIXADDR_USER_START is replaced by FIXADDR_START(+ some syntactical 
changes that do not hurt). And they have a different meaning(see 
include/asm-i386/fixmap.h).

Since I'm not a VM hacker, and I don't understand the change, I just say that 
that shouldn't be used, for prudence's sake. That mention about backup is 
maybe a bit exaggerated, but it's a form of "no warranty" disclaimer.

*NOTE*: the combo patches from Ingo Molnar contain this, too(I don't know if 
he noticed this change at all), and he probably used this without problem. So 
I may be wrong at all.

Bye
-- 
cat <<EOSIGN
Paolo Giarrusso, aka Blaisorblade
Linux Kernel 2.4.21/2.6.0-test on an i686; Linux registered user n. 292729
EOSIGN



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&opÌk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2003-12-26 19:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-26 18:05 [uml-devel] UML patches against vanilla 2.6.0 BlaisorBlade
2003-12-26 18:27 ` Cameron Patrick
2003-12-26 18:56   ` BlaisorBlade [this message]
2003-12-27 18:27 ` BlaisorBlade
2003-12-29 20:09   ` [uml-devel] " Jason Lunz
2003-12-31 17:58     ` BlaisorBlade
2003-12-28  1:07 ` [uml-devel] " Jeff Chua
2003-12-28 16:20   ` BlaisorBlade
2003-12-28 16:27   ` [uml-user] " Domenico Andreoli
2003-12-28 17:46     ` Jeff Chua

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=200312261956.13626.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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