From: Paul Mackerras <paulus@samba.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Fabrice Bellard <fabrice.bellard@free.fr>,
linux-kernel@vger.kernel.org,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [PATCH] Qemu support for PPC
Date: Mon, 7 Apr 2003 16:05:56 +1000 [thread overview]
Message-ID: <16017.5444.941131.275543@argo.ozlabs.ibm.com> (raw)
In-Reply-To: <20030407072144.A28096@infradead.org>
Christoph Hellwig writes:
> On Mon, Apr 07, 2003 at 03:09:37PM +1000, Paul Mackerras wrote:
> > sys_personality will fail if there isn't an exec_domain registered for
> > the personality you want.
>
> But there already is one registered :) Okay, you\re right.
>
> > Why? It's a well-contained patch that affects very little outside its
> > own area, and is quite similar to other things that have been there
> > for ages.
>
> Because stuff should go into 2.5 first. And even if it looks trivial
> there's an important policy decision here: do we want to clutter up
> our personality system for userspace emulators? If you look at the
> current list of personalities they all have kernel implementations, even
> if not all of them are currently merged, qemu OTOH is a purely userspace
> thing (and still very new!). Personally I'd rather prefer qemu doing
> pathname translation in userspace instead of bloating the kernel. This
> gets even more important when we get qemu-style emulators for other
> architectures - the number of personalities needed just for this ugly
> pathname-translation scheme will get very high.
Well, all we really want is a way to set emul_prefix. Which I could
do with a PPC-specific syscall if I had to, I guess. Doing it in
userspace is possible but ugly, because you have to handle several
different syscalls, plus keep track of the current directory, plus
handle symlinks, etc., etc., in the emulator. The kernel has all that
information readily to hand plus the data structures to keep track of
it all.
> > Anyway, it's not your call.
>
> if you look at MAINTAINERS I'm responsible for personality handling, so
> maybe it actually _is_ my call?
Oh. Ah. I didn't realize it was a subsystem with a maintainer.
Paul.
next prev parent reply other threads:[~2003-04-07 6:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 2:40 Rusty Russell
2003-04-07 2:29 ` Paul Mackerras
2003-04-07 5:58 ` Christoph Hellwig
2003-04-07 5:09 ` Paul Mackerras
2003-04-07 6:21 ` Christoph Hellwig
2003-04-07 6:05 ` Paul Mackerras [this message]
2003-04-07 11:24 ` Alan Cox
2003-04-07 20:41 ` Tom Rini
2003-04-07 6:45 Rusty Russell
2003-04-07 6:56 ` Christoph Hellwig
2003-04-07 8:34 ` Rusty Russell
2003-04-07 12:49 ` Christoph Hellwig
2003-04-08 1:52 ` Rusty Russell
2003-04-07 11:21 ` Alan Cox
2003-04-09 2:07 ` Rusty Russell
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=16017.5444.941131.275543@argo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=fabrice.bellard@free.fr \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®