xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: PGNet Dev <pgnet.dev@gmail.com>
To: boris.ostrovsky@oracle.com, roger.pau@citrix.com,
	xen-devel@lists.xen.org
Subject: Re: Clarifying PVH mode requirements
Date: Mon, 1 Feb 2016 07:49:14 -0800	[thread overview]
Message-ID: <56AF7E7A.1040305@gmail.com> (raw)
In-Reply-To: <56AF679E.4040104@oracle.com>

On 02/01/2016 06:11 AM, Boris Ostrovsky wrote:
> This actually never happened for Linux: HVMlite showed up fast enough
> that it didn't make sense anymore to add 32-bit support to Linux
> (especially given that AMD was still not supported).

Is 'HVMLite' replacing 'PVH'? Or are they separate modes?

  reply	other threads:[~2016-02-01 15:49 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 [this message]
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

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=56AF7E7A.1040305@gmail.com \
    --to=pgnet.dev@gmail.com \
    --cc=boris.ostrovsky@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).