All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: PGNet Dev <pgnet.dev@gmail.com>, bgregg@netflix.com
Cc: xen-devel@lists.xen.org
Subject: Re: Clarifying PVH mode requirements
Date: Thu, 4 Feb 2016 17:39:14 -0500	[thread overview]
Message-ID: <56B3D312.4030402@oracle.com> (raw)
In-Reply-To: <56B3CA47.7090805@gmail.com>

On 02/04/2016 05:01 PM, PGNet Dev wrote:
>>> On Mon, Feb 1, 2016 at 11:58 AM, Boris Ostrovsky
>>>     Current PVH implementation has never been described as
>>>     production-ready. What is happening now with HVMlite is
>>>     essentially bringing PVH to production-quality level.
>>>
>>>
>>> So should I s/PVH/HVMlite/g?
>>
>>  From user perspective that will be almost true. I am not sure it should
>> be classified as PV mode anymore since it's really an HVM guest without
>> any devices. But it's not there yet so it's too early to point your
>> editor there.
>>
>> BTW, I don't think the flowchart in the wiki is correct as far as PVH is
>> concerned --- you can't use PVH unless HVM (and, in fact, PVHVM) is
>> supported.
>
> Noting the very recent flurry of HVMLite activity, so where does PVH sit?
>
> As it's not production-ready (and, atm, unusable here), is it planned 
> to be? 

Not the current implementation.

> Or is it being simply leap-frogged by HVMLite?
>

I don't know about "leap-frogged", I think you might say PVH evolved 
into HVMlite?

-boris

      reply	other threads:[~2016-02-04 22:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-31 21:27 Clarifying PVH mode requirements PGNet Dev
2016-02-01  3:47 ` PGNet Dev
2016-02-01 10:30   ` Roger Pau Monné
2016-02-01 12:16     ` PGNet Dev
2016-02-01  9:59 ` Wei Liu
2016-02-01 12:23   ` PGNet Dev
2016-02-01 12:29     ` Wei Liu
2016-02-01 12:29     ` Roger Pau Monné
2016-02-01 12:38       ` PGNet Dev
2016-02-01 13:38         ` PGNet Dev
2016-02-01 14:54           ` Boris Ostrovsky
2016-02-01 16:56             ` Jan Beulich
2016-02-01 19:17               ` Boris Ostrovsky
2016-02-02  9:32                 ` Jan Beulich
2016-02-02 15:51             ` Jan Beulich
2016-02-02 16:16               ` PGNet Dev
2016-02-01 10:28 ` Roger Pau Monné
2016-02-01 12:30   ` PGNet Dev
2016-02-01 14:11   ` Boris Ostrovsky
2016-02-01 15:49     ` PGNet Dev
2016-02-01 19:14       ` Boris Ostrovsky
2016-02-01 19:27         ` PGNet Dev
2016-02-01 19:58           ` Boris Ostrovsky
2016-02-01 23:49             ` Brendan Gregg
2016-02-02 15:28               ` Boris Ostrovsky
2016-02-04 22:01                 ` PGNet Dev
2016-02-04 22:39                   ` Boris Ostrovsky [this message]

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=56B3D312.4030402@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=bgregg@netflix.com \
    --cc=pgnet.dev@gmail.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.