linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
	kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	Avi Kivity <avi@qumranet.com>
Subject: Re: [kvm-devel] [PATCH] Refactor hypercall infrastructure
Date: Fri, 14 Sep 2007 16:00:21 -0700	[thread overview]
Message-ID: <46EB1285.5050807@goop.org> (raw)
In-Reply-To: <97D612E30E1F88419025B06CB4CF1BE10379EBF9@scsmsx412.amr.corp.intel.com>

Nakajima, Jun wrote:
>>> one.  Start the kvm leaves at 0x40001000 or something?
>>>
>>>       
>> Yeah, that works with me.
>>     
>
> To me this is the beginning of fragmentation. Why do we need different
> and VMM-specific Linux paravirtualization for hardware-assisted
> virtualization? That would not be good for Linux.
>   

On the contrary.  Xen already has a hypercall interface, and we need to
keep supporting it.  If we were to also support a vmm-independent
interface (aka "kvm interface"), then we need to be able to do that in
parallel.  If we have a cpuid leaf clash, then its impossible to do so;
if we define the new interface to be disjoint from other current users
of cpuid, then we can support them concurrently.

    J

  reply	other threads:[~2007-09-14 23:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-14 19:45 [PATCH] Refactor hypercall infrastructure Anthony Liguori
2007-09-14 20:53 ` Jeremy Fitzhardinge
2007-09-14 21:02   ` [kvm-devel] " Anthony Liguori
2007-09-14 21:20     ` Zachary Amsden
2007-09-14 21:44       ` Anthony Liguori
2007-09-15  3:37         ` Zachary Amsden
2007-09-15  8:08           ` Avi Kivity
2007-09-15 17:33           ` Anthony Liguori
2007-09-14 21:22     ` Jeremy Fitzhardinge
2007-09-14 21:46       ` Anthony Liguori
2007-09-14 21:52         ` Jeremy Fitzhardinge
2007-09-14 22:08           ` Anthony Liguori
2007-09-14 22:40             ` Nakajima, Jun
2007-09-14 23:00               ` Jeremy Fitzhardinge [this message]
2007-09-15  0:10                 ` Nakajima, Jun
2007-09-15  0:28                   ` Jeremy Fitzhardinge
2007-09-15  1:04                     ` Nakajima, Jun
2007-09-15  4:53                       ` Jeremy Fitzhardinge
2007-09-15  6:11                         ` Nakajima, Jun
2007-09-15 18:23                           ` Anthony Liguori
2007-09-17 18:14                             ` Nakajima, Jun
2007-09-17 18:27                               ` Anthony Liguori
2007-09-17 19:15                                 ` Jeremy Fitzhardinge
2007-09-17 19:33                                   ` Anthony Liguori
2007-09-17 19:15                               ` Jeremy Fitzhardinge
2007-09-17 20:52                                 ` Nakajima, Jun
2007-09-15  8:00               ` Avi Kivity
2007-09-15  7:53     ` Avi Kivity
2007-09-15  2:35   ` 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=46EB1285.5050807@goop.org \
    --to=jeremy@goop.org \
    --cc=anthony@codemonkey.ws \
    --cc=avi@qumranet.com \
    --cc=jun.nakajima@intel.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).