From: "Bryan O'Sullivan" <bos@keyresearch.com>
To: stevegt@TerraLuna.Org
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] SKAS: Why pass mm vs. current?
Date: 05 Sep 2003 14:53:53 -0700 [thread overview]
Message-ID: <1062798832.23069.56.camel@serpentine.internal.keyresearch.com> (raw)
In-Reply-To: <20030905214737.GF1601@pathfinder>
On Fri, 2003-09-05 at 14:47, stevegt@TerraLuna.Org wrote:
> So that sounds like it answers one of my first questions -- there's
> actually no special context that needs to be preserved down through the
> call stack, so neither mm nor current need to be explicitly passed at
> all?
Um, of course mm needs passing in some form or another.
The whole point of the skas patches is to let a single process execute
with multiple different mm_structs, switching back and forth between
them under the control of the master process.
In order to do this, the host process has to have some way of telling
the slave which mm_struct to use. Look at the changes to ptrace.c in
the patch and you'll see what's going on at the top level. Everything
else kind of follows from that.
> If I fix this by creating a new patch, can we post it as skas3.1 or
> something?
SuSE already has a modified skas patch that fixes the interface breakage
in 2.4. The 2.6 patch doesn't break any interfaces. Jeff is likely to
have time to make a clean interface very soon.
Ergo, there's nothing much to be done.
<b
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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:[~2003-09-05 21:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 2:06 [uml-devel] SKAS: Why pass mm vs. current? stevegt
2003-09-05 20:12 ` Jeff Dike
2003-09-05 21:08 ` stevegt
2003-09-05 21:28 ` Bryan O'Sullivan
2003-09-05 21:47 ` stevegt
2003-09-05 21:53 ` Bryan O'Sullivan [this message]
2003-09-08 22:51 ` Adam Heath
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=1062798832.23069.56.camel@serpentine.internal.keyresearch.com \
--to=bos@keyresearch.com \
--cc=stevegt@TerraLuna.Org \
--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