From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: "Juergen Gross" <jgross@suse.com>,
"Lars Kurth" <lars.kurth@citrix.com>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: PVHv2 vs HVMlite
Date: Tue, 27 Sep 2016 10:36:00 -0400 [thread overview]
Message-ID: <20160927143600.GF16528@localhost.localdomain> (raw)
In-Reply-To: <57EA7FF4.4020803@citrix.com>
On Tue, Sep 27, 2016 at 03:19:32PM +0100, David Vrabel wrote:
> On 27/09/16 15:08, Boris Ostrovsky wrote:
> > I will be dusting off Linux domU PVHv2 patches now that ACPI changes are
> > getting close to being accepted.
> >
> > Last version of that patch referred to these guests as 'hvmlite',
> > including in names of variables, routines etc. I was hesitant to remove
> > "classic" PVH code and use "pvh" instead of "hvmlite" because we didn't
> > have dom0 v2 support and so I kept existing PVHv1 code intact.
> >
> > Do we still want to do this (i.e. keep v1 code and use "hvmlite")? FWIW,
> > I am not aware of anyone using PVH dom0 (or PVH domU for that matter).
>
> I think we should remove the PVHv1 code from Linux and then reuse the
> "pvh" name.
+1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-27 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 14:08 PVHv2 vs HVMlite Boris Ostrovsky
2016-09-27 14:19 ` David Vrabel
2016-09-27 14:36 ` Konrad Rzeszutek Wilk [this message]
2016-09-27 14:45 ` Juergen Gross
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=20160927143600.GF16528@localhost.localdomain \
--to=konrad.wilk@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=lars.kurth@citrix.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.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 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.