From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= <roger.pau@citrix.com>
Subject: Re: [Draft C] Boot ABI for HVM guests without a
 device-model
Date: Fri, 4 Sep 2015 18:09:27 +0200
Message-ID: <55E9C237.2020408@citrix.com>
References: <55E98A8F.3080305@citrix.com>
	<55E9C1E1020000780009FC72@prv-mh.provo.novell.com>
	<55E9AB40.8060402@citrix.com>
	<55E9D30C020000780009FD9F@prv-mh.provo.novell.com>
	<55E9BD02.40701@citrix.com>
	<55E9DCD5020000780009FE00@prv-mh.provo.novell.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 <prvs=682060d1e=roger.pau@citrix.com>)
	id 1ZXtf3-00025R-SG
	for xen-devel@lists.xenproject.org; Fri, 04 Sep 2015 16:16:21 +0000
In-Reply-To: <55E9DCD5020000780009FE00@prv-mh.provo.novell.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: Jan Beulich <JBeulich@suse.com>
Cc: Elena Ufimtseva <elena.ufimtseva@oracle.com>, Andrew Cooper <andrew.cooper3@citrix.com>, Boris Ostrovsky <boris.ostrovsky@oracle.com>, Tim Deegan <tim@xen.org>, xen-devel <xen-devel@lists.xenproject.org>
List-Id: xen-devel@lists.xenproject.org

El 04/09/15 a les 18.03, Jan Beulich ha escrit:
>>>> On 04.09.15 at 17:47, <roger.pau@citrix.com> wrote:
>> VCPUOP_initialize was never available to HVM guests, so I don't think
>> changing the argument is a problem. However, I understand that for the
>> sake of clarity overloading an hypercall this way is not the best
>> practice. What about naming it VCPUOP_hvm_initialise?
> 
> Hmm, don't know, the more that we want it primarily for PVH.

Well, it will be available to HVM guests in general, both pure HVM and
PVH guests.

Roger.