From: Keir Fraser <keir.xen@gmail.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>,
Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 6/18 V2]: PVH xen: Introduce PVH guest type
Date: Mon, 25 Mar 2013 20:07:10 +0000 [thread overview]
Message-ID: <CD765EEE.1BB00%keir.xen@gmail.com> (raw)
In-Reply-To: <20130325120507.5621a913@mantra.us.oracle.com>
On 25/03/2013 19:05, "Mukesh Rathor" <mukesh.rathor@oracle.com> wrote:
>> These are all ugly, and I don't see why the triplet I suggested
>> (is_pv, is_pvh, and is_hvm), including their intended use, wouldn't
>> be acceptable.
>
> Because this implies pvh is a new type, whereas like I said before,
> PVH is a PV guest. Ok, lets go with your suggestion above, and if
> people find it confusing, we can change in future.
It's not really PV -- the interfaces and execution environment are somewhat
different, evidence being that a legacy PV guest will not boot in PVH mode!
There are certainly similarities, but then there are between HVM and PV too
(e.g., many hypercalls), so at the end of the day a guest is one of
PV/PVH/HVM. So I have to agree with Jan.
-- Keir
next prev parent reply other threads:[~2013-03-25 20:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-16 0:32 [PATCH 6/18 V2]: PVH xen: Introduce PVH guest type Mukesh Rathor
2013-03-18 11:54 ` Jan Beulich
2013-03-19 0:21 ` Mukesh Rathor
2013-03-19 8:48 ` Jan Beulich
2013-03-19 13:03 ` Konrad Rzeszutek Wilk
2013-03-19 13:41 ` Jan Beulich
2013-03-23 1:13 ` Mukesh Rathor
2013-03-25 9:26 ` Jan Beulich
2013-03-25 19:05 ` Mukesh Rathor
2013-03-25 20:07 ` Keir Fraser [this message]
2013-03-25 22:04 ` Mukesh Rathor
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=CD765EEE.1BB00%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=mukesh.rathor@oracle.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.