From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
"Yang, Sheng" <sheng.yang@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Dong, Eddie" <eddie.dong@intel.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: Re: Xen: Hybrid extension patchset for hypervisor
Date: Fri, 18 Sep 2009 17:28:34 -0700 [thread overview]
Message-ID: <4AB425B2.400@goop.org> (raw)
In-Reply-To: <0B53E02A2965CE4F9ADB38B34501A3A19411EAE7@orsmsx505.amr.corp.intel.com>
On 09/18/09 17:17, Nakajima, Jun wrote:
> Even if we start from PV kernels, I think what we should do is to implement ability (as "incremental changes") for PV guests to stop using PV MMU (and PV CPU) at boot time depending on the H/W features available rather than to keep using the same ABI, because we may not need them in the near future. Then, such PV kernels would be at par or faster/more efficient than pure HVM guests on machines with HAP enabled because of the other PV features.
>
Sure, that's no problem. So long as the current ABI keeps working, we
can easily switch to something else more appropriate where possible.
J
next prev parent reply other threads:[~2009-09-19 0:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 8:44 Xen: Hybrid extension patchset for hypervisor Yang, Sheng
2009-09-16 9:08 ` Keir Fraser
2009-09-16 14:04 ` Keir Fraser
2009-09-16 16:28 ` Nakajima, Jun
2009-09-16 18:19 ` Jeremy Fitzhardinge
2009-09-16 21:12 ` Ian Campbell
2009-09-16 21:22 ` Jeremy Fitzhardinge
2009-09-17 9:16 ` Ian Campbell
2009-09-17 15:56 ` Nakajima, Jun
2009-09-17 17:34 ` Jeremy Fitzhardinge
2009-09-19 0:17 ` Nakajima, Jun
2009-09-19 0:28 ` Jeremy Fitzhardinge [this message]
2009-09-17 17:19 ` Jeremy Fitzhardinge
2009-09-16 19:11 ` Frank van der Linden
2009-09-17 6:13 ` Yang, Sheng
2009-09-17 6:25 ` Keir Fraser
2009-09-17 6:30 ` Sheng Yang
2009-09-17 6:47 ` Yang, Sheng
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=4AB425B2.400@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=eddie.dong@intel.com \
--cc=jun.nakajima@intel.com \
--cc=sheng.yang@intel.com \
--cc=xen-devel@lists.xensource.com \
/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.