linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: Bodo Stroesser <bstroesser@fujitsu-siemens.com>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: Skas0 general testing?
Date: Wed, 22 Jun 2005 21:12:55 -0400	[thread overview]
Message-ID: <20050623011255.GB15548@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200506230238.35960.blaisorblade@yahoo.it>

On Thu, Jun 23, 2005 at 02:38:35AM +0200, Blaisorblade wrote:
> Would you start preparing a SKAS0 patch-set that I can merge into -bs for 
> general testing and that can be merged into -mm at least?

I'm working on it.  skas0 and skas0-clone are the first to go.  I just
"fixed" skas0 so it gets mm->nr_ptes right without the change to
exit_mmap that used to be there.  I'm banging on that patch now.

The rest still need work.  The setup patches (where we make proc_mm et
al settable on the command line and all combinations will work) are
probably OK.

Some of the later ones are pretty sad.  The ldt patches are probably
not too hard to clean up, but things like add-gate-vma are horrible.

I'm not planning on having a whole good set before starting to send
them to Andrew.  I'll send the ones I'm happiest about, and clean up
the rest, sending them in during the course of 2.6.13.

> I'd like it to be verifiably "don't touch" about SKAS3 working (i.e. no 
> "little changes which won't hurt"). As I already said, I don't mean from the 
> "code" viewpoint but from the "what's actually done" viewpoint (in terms of 
> strace output, if you want so).

That's a good goal, but we can't let it get in the way of keeping the
code clean.  Certainly, anything which touches skas3 should be
carefully looked at, but I don't want to state that we will not touch
any skas3 code.  Bodo's patches which make any combination of
PTRACE_LDT, PTRACE_FAULTINFO, and /proc/mm work are a good example.  I
think that's a worthwhile patch, but it does touch skas3 code.

				Jeff


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&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-06-23  1:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23  0:38 [uml-devel] Skas0 general testing? Blaisorblade
2005-06-23  1:12 ` Jeff Dike [this message]
2005-06-23  1:36   ` [uml-devel] " Blaisorblade
2005-06-23  3:11     ` Jeff Dike
2005-06-30 14:31     ` Jeff Dike
2005-06-30 15:14       ` Blaisorblade
2005-06-30 16:09         ` Jeff Dike
2005-07-01 22:56           ` Blaisorblade
2005-06-23 10:28   ` Bodo Stroesser

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=20050623011255.GB15548@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=blaisorblade@yahoo.it \
    --cc=bstroesser@fujitsu-siemens.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox