From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: HYBRID naming [Was: Re: [HYBRID]: status update...] Date: Thu, 2 Aug 2012 12:41:19 +0100 Message-ID: <501A675F.4010804@eu.citrix.com> References: <20120626181707.4203d336@mantra.us.oracle.com> <20120801152508.GA7132@phenom.dumpdata.com> <20120801160515.GA16155@phenom.dumpdata.com> <20120801165359.GF8228@US-SEA-R8XVZTX> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20120801165359.GF8228@US-SEA-R8XVZTX> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Matt Wilson Cc: Ian Campbell , Keir Fraser , "Xen-devel@lists.xensource.com" , Stefano Stabellini , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org 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