All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Blaisorblade <blaisorblade@yahoo.it>,
	Peter <peter.spamcatcher@rimuhosting.com>
Subject: Re: [uml-devel] 2.6.9-bs7 panic on check_sysemu
Date: Tue, 5 Apr 2005 13:23:47 -0400	[thread overview]
Message-ID: <200504051323.47160.rob@landley.net> (raw)
In-Reply-To: <200504041532.23866.blaisorblade@yahoo.it>

On Monday 04 April 2005 09:32 am, Blaisorblade wrote:

> > Is this a case where I should be upgrading my host kernels (will do that
> > in time anyway)?
>
> You simply need to update the SKAS patch version. -V2 is very old, and many
> bugs (including this, that is a bug in the SYSEMU part of the SKAS patch).
> Upgrading to -V7 for the SKAS patch, even on the same host kernel version
> (i.e. against 2.6.8.1), would fix that.
>
> Also, some older guest kernels may seem to work, because they don't
> diagnose such bugs. But actually they have problems in some situations,
> because of the host bugs. For instance panicking with a simple "echo 0 >
> /proc/sysemu; echo 1 > /proc/sysemu".
>
> > Or is there something that can be done on the guest to make it work on
> > older kernels also?
>
> Not a lot, except disabling SYSEMU (and its performance advantage) entirely
> - add the "nosysemu" param to the UML command line and it will work.
>
> But it won't be as slow as if you didn't use SKAS.
>
> Bye

Speaking of which, I ask this from time to time:

What's the minimal patch set that _just_ adds -SKAS0 mode to something like a 
2.6.11 kernel?  I'd like to try it out, but every time I sit down to whack at 
it my interest budget runs out sifting through a mountain of unrelated x86-64 
patches to try to figure out what exactly I need to apply to get just 
SKAS0...

No biggie.  I'll can always ask again later... :)

Rob


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
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:[~2005-04-05 19:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-03 22:47 [uml-devel] 2.6.9-bs7 panic on check_sysemu Peter
2005-04-04 13:32 ` Blaisorblade
2005-04-05 17:23   ` Rob Landley [this message]
2005-04-05 20:54     ` Blaisorblade
2005-04-05 20:55     ` Blaisorblade
2005-04-06  4:59       ` Rob Landley
2005-04-06  0:24     ` Jeff Dike

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=200504051323.47160.rob@landley.net \
    --to=rob@landley.net \
    --cc=blaisorblade@yahoo.it \
    --cc=peter.spamcatcher@rimuhosting.com \
    --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 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.