From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
boris.ostrovsky@oracle.com, Aravind.Gopalakrishnan@amd.com,
suravee.suthikulpanit@amd.com, Jan Beulich <JBeulich@suse.com>
Subject: Re: [RFH]: AMD CR intercept for lmsw/clts
Date: Tue, 5 Aug 2014 15:30:25 -0700 [thread overview]
Message-ID: <20140805153025.679dda72@mantra.us.oracle.com> (raw)
In-Reply-To: <53E0D569.2030700@citrix.com>
On Tue, 05 Aug 2014 14:00:25 +0100
Andrew Cooper <andrew.cooper3@citrix.com> wrote:
> On 05/08/2014 13:11, Jan Beulich wrote:
> >>>> On 05.08.14 at 13:16, <andrew.cooper3@citrix.com> wrote:
> >> On 05/08/2014 08:46, Jan Beulich wrote:
...
> Despite the current limitations, I firmly believe that PVH should be
> HVM
> - device model, rather than PV + VMX/SVM.
I think that might be a dangerous route to take, classifying upfront
whether it's that way or the other. Eg, if we say it's former, then
anyone adding any feature would not examine the best approach, but just
take hvm approach.
> Fundamentally, the end goal of PVH needs deciding ASAP, and
> documenting, to help guide decisions like this.
I think it's decided somewhat. Evolve to one of three approaches: PV,
HVM, or alternate, picking the easiest and fastest. IMO, at the very
least, pvh should retain "guest modified" characteristic, that would be
good for xen future imho.
Mukesh
next prev parent reply other threads:[~2014-08-05 22:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 1:33 [RFH]: AMD CR intercept for lmsw/clts Mukesh Rathor
2014-08-05 7:46 ` Jan Beulich
2014-08-05 11:16 ` Andrew Cooper
2014-08-05 12:11 ` Jan Beulich
2014-08-05 13:00 ` Andrew Cooper
2014-08-05 13:15 ` Jan Beulich
2014-08-05 22:30 ` Mukesh Rathor [this message]
2014-08-06 9:34 ` Andrew Cooper
2014-08-15 21:04 ` Konrad Rzeszutek Wilk
2014-08-15 21:48 ` Andrew Cooper
2014-08-05 22:22 ` 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=20140805153025.679dda72@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=xen-devel@lists.xenproject.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).