From: Avi Kivity <avi@qumranet.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andrew Morton <akpm@osdl.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@muc.de>
Subject: Re: [PATCH] Cleanup: rationalize paravirt wrappers
Date: Fri, 23 Mar 2007 13:19:59 +0200 [thread overview]
Message-ID: <4603B7DF.6000202@qumranet.com> (raw)
In-Reply-To: <1174647912.7642.4.camel@localhost.localdomain>
Rusty Russell wrote:
> 4) Access to the native versions is trivial for KVM, lguest, Xen and
> others who might want it.
>
kvm will be quite happy with it, as long as the x86_64 version has a
similar API.
include/asm-x86 anyone? ;-)
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2007-03-23 11:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 2:41 [PATCH] Cleanup: rationalize paravirt wrappers Rusty Russell
2007-03-22 7:30 ` Avi Kivity
2007-03-22 8:00 ` Rusty Russell
2007-03-22 8:09 ` Jeremy Fitzhardinge
2007-03-22 8:09 ` Avi Kivity
2007-03-22 9:55 ` Rusty Russell
2007-03-23 11:05 ` Rusty Russell
2007-03-23 11:19 ` Avi Kivity [this message]
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=4603B7DF.6000202@qumranet.com \
--to=avi@qumranet.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.