From: Christoph Hellwig <hch@infradead.org>
To: linux-ia64@vger.kernel.org
Subject: Re: Fast Syscalls and Virtualised Linux on Linux
Date: Thu, 30 Jun 2005 14:15:36 +0000 [thread overview]
Message-ID: <20050630141536.GA27256@infradead.org> (raw)
In-Reply-To: <17090.8605.481641.322881@wombat.chubb.wattle.id.au>
On Wed, Jun 29, 2005 at 02:20:45PM +1000, Peter Chubb wrote:
> One approach might be to redefine __BREAK_SYSCALL for the guest OS.
> That'd require a specially compiled glibc and kernel, and possibly
> other executables.
>
> Does anyone have a better idea?
Make sure glibc is always doing syscalls via the vdso (and that the kernel
actually support this ;-)) Then the guest kernel can provide an alternate
vdso implementation using whatever implementation it wants. This also
allows the kernel an chose different syscall implemetations for native
compilation later on. x86 is already doing this to suport sysenter()
next prev parent reply other threads:[~2005-06-30 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 4:20 Fast Syscalls and Virtualised Linux on Linux Peter Chubb
2005-06-29 15:03 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-06-30 14:12 ` Jes Sorensen
2005-06-30 14:15 ` Christoph Hellwig [this message]
2005-06-30 23:05 ` Peter Chubb
2005-07-04 15:09 ` Christoph Hellwig
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=20050630141536.GA27256@infradead.org \
--to=hch@infradead.org \
--cc=linux-ia64@vger.kernel.org \
/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