From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH for-4.5 v6 08/16] xen: Add limited support
 of VMware's hyper-call rpc
Date: Tue, 23 Sep 2014 13:34:27 +0100
Message-ID: <1411475667.1781.17.camel@kazak.uk.xensource.com>
References: <1411236447-7435-1-git-send-email-dslutz@verizon.com>
	<1411236447-7435-9-git-send-email-dslutz@verizon.com>
	<1411393637.18331.108.camel@kazak.uk.xensource.com>
	<5420923E.2090704@terremark.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <5420923E.2090704@terremark.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: Don Slutz <dslutz@verizon.com>
Cc: Tim Deegan <tim@xen.org>, Kevin Tian <kevin.tian@intel.com>, Keir Fraser <keir@xen.org>, Jun Nakajima <jun.nakajima@intel.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>, George Dunlap <George.Dunlap@eu.citrix.com>, Ian Jackson <ian.jackson@eu.citrix.com>, Eddie Dong <eddie.dong@intel.com>, xen-devel@lists.xen.org, Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>, Jan Beulich <jbeulich@suse.com>, Andrew Cooper <andrew.cooper3@citrix.com>, Boris Ostrovsky <boris.ostrovsky@oracle.com>, Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
List-Id: xen-devel@lists.xenproject.org

On Mon, 2014-09-22 at 17:18 -0400, Don Slutz wrote:
> On 09/22/14 09:47, Ian Campbell wrote:
> > On Sat, 2014-09-20 at 14:07 -0400, Don Slutz wrote:
> >> This interface is an extension of __HYPERVISOR_HVM_op.  It was
> >> picked because xc_get_hvm_param() also uses it and VMware guest
> >> info is a lot like a hvm param.
> > Sorry if this has been discussed before, but did you consider doing all
> > this in qemu rather than Xen?
> 
> 
> Yes, but QEMU does not have access to the VCPU registers.  Also QEMU 
> does not have this code; so would also need it to be added.

I thought you said KVM had this functionality already? If so then the
bulk of the code should be there already.

> A second part would be adding a way for a tool stack to
> communicate with QEMU to access this data.  xenstore/xenbus might
> be one way to do this.

qmp would be the more modern way I think.

Ian.