From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mukesh Rathor <mukesh.rathor@oracle.com>
Subject: Re: [RFH]: AMD CR intercept for lmsw/clts
Date: Tue, 5 Aug 2014 15:30:25 -0700
Message-ID: <20140805153025.679dda72@mantra.us.oracle.com>
References: <20140804183337.2bb1b680@mantra.us.oracle.com>
	<53E0A7EC02000078000294FF@mail.emea.novell.com>
	<53E0BD00.8010602@citrix.com>
	<53E0E61F0200007800029731@mail.emea.novell.com>
	<53E0D569.2030700@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <mukesh.rathor@oracle.com>) id 1XEnFe-0000w4-Rl
	for xen-devel@lists.xenproject.org; Tue, 05 Aug 2014 22:30:38 +0000
In-Reply-To: <53E0D569.2030700@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
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>
List-Id: xen-devel@lists.xenproject.org

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