From: George Dunlap <george.dunlap@eu.citrix.com>
To: Matt Wilson <msw@amazon.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
Keir Fraser <keir.xen@gmail.com>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: HYBRID naming [Was: Re: [HYBRID]: status update...]
Date: Thu, 2 Aug 2012 12:41:19 +0100 [thread overview]
Message-ID: <501A675F.4010804@eu.citrix.com> (raw)
In-Reply-To: <20120801165359.GF8228@US-SEA-R8XVZTX>
On 01/08/12 17:53, Matt Wilson wrote:
> On Wed, Aug 01, 2012 at 09:21:57AM -0700, George Dunlap wrote:
>> Hmm -- that's an interesting issue I hadn't thought of. "PVHVM" has
>> already been sort of taken by Stefano's extensions to allow Linux
>> kernels booted in HVM mode to use some of the PV extensions. I tend
>> to think "xen_pvh_domain()" is probably OK, but maybe calling it
>> "pvext" (or "pvhext") in the code, and "PVH" in documentation /
>> stories? Just using "pvext" everywhere could work as well; it's a
>> little bit "now even better!", but not as much as pvplus.
> How about HAPV, for "Hardware Assisted Paravirtualization"? It's
> nicely pronounceable as "hap-vee" and follows the general
> "hardware-assisted paging" (HAP) Xen terminology that spans both Intel
> EPT and AMD RVI. 'if (xen_hapv_domain())'
Wouldn't "HAPV" make people think more of HAP than of PV? It seems like
it would be much more confusing to distinguish "hapv" from "hap" than
"pvh" from "pv". :-)
-George
next prev parent reply other threads:[~2012-08-02 11:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 1:17 [HYBRID]: status update Mukesh Rathor
2012-06-27 2:10 ` Mukesh Rathor
2012-06-28 8:44 ` Ian Campbell
2012-07-03 19:24 ` Mukesh Rathor
2012-07-04 10:01 ` Stefano Stabellini
2012-07-04 23:13 ` Mukesh Rathor
2012-07-05 14:05 ` Stefano Stabellini
2012-08-01 15:25 ` George Dunlap
2012-08-01 15:25 ` Konrad Rzeszutek Wilk
2012-08-01 15:59 ` George Dunlap
2012-08-01 16:05 ` Konrad Rzeszutek Wilk
2012-08-01 16:21 ` George Dunlap
2012-08-01 16:51 ` Sander Eikelenboom
2012-08-01 16:55 ` Konrad Rzeszutek Wilk
2012-08-01 16:53 ` HYBRID naming [Was: Re: [HYBRID]: status update...] Matt Wilson
2012-08-02 11:41 ` George Dunlap [this message]
2012-08-04 1:06 ` Pasi Kärkkäinen
2012-08-01 16:05 ` [HYBRID]: status update Andrew Cooper
2012-08-01 16:08 ` Ian Campbell
2012-08-01 16:02 ` Sander Eikelenboom
2012-08-01 22:34 ` Mukesh Rathor
2012-08-02 9:53 ` George Dunlap
2012-08-02 14:24 ` Konrad Rzeszutek Wilk
2012-08-13 22:14 ` Mukesh Rathor
2012-08-14 10:44 ` Stefano Stabellini
2012-08-14 17:38 ` Mukesh Rathor
2012-08-14 17:42 ` Stefano Stabellini
2012-08-14 17:51 ` Mukesh Rathor
2012-08-15 8:19 ` Jan Beulich
2012-08-15 9:42 ` Ian Campbell
2012-08-15 9:54 ` Jan Beulich
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=501A675F.4010804@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=keir.xen@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=msw@amazon.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.