From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: UML patches against vanilla 2.6.0
Date: Wed, 31 Dec 2003 18:58:02 +0100 [thread overview]
Message-ID: <200312311858.02382.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <slrnbv12f4.4rj.lunz@absolut.localnet>
Alle 21:09, lunedì 29 dicembre 2003, Jason Lunz ha scritto:
> blaisorblade_spam@yahoo.it said:
> > I have some doubts about the 2.6 host-skas patch. I've searched through
> > the list for earlier ports to 2.6 and I've seen someone (Bryan O'Sullivan
> > <bos@serpentine.com>) complaining:
> >
> > "The big issue with the skas patches, though, appears to be that they
> > don't handle the UML kernel being killed, which results in the host
> > kernel's memory management being completely trashed."
> >
> > Is this a real issue or not?
>
> I think so. I'm running 2.6.0 vanilla + Ingo's combo -A2 on my host,
> with 2.4.23 UMLs.
> I tried to do something in the uml involving lots of
> tmpfs usage, and the host system crashed.
If you use the Ingo's combo patch, maybe it's not the Skas mode itself.
There is a change in mm/memory.c which is fine for UML, but IMHO probably
hurts for the host kernel. Looking at the patch he posts, however, he didn't
use this change, so beyond the mm/memory.c problem there must be another one.
To test that, you can either select the changes to that file away from the
patch, or unapply (with -R option to patch) this patch, which contains
exactly that change:
http://web.tiscali.it/no-redirect-tiscali/blaisorblade/linux/archives/UML/v2/A-04-MM-compile-fix.patch
--
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
next prev parent reply other threads:[~2004-01-01 9:46 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
2003-12-27 18:27 ` BlaisorBlade
2003-12-29 20:09 ` [uml-devel] " Jason Lunz
2003-12-31 17:58 ` BlaisorBlade [this message]
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=200312311858.02382.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