This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] [PATCH 1/1] Reserve V4V hypercall number

To: Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH 1/1] Reserve V4V hypercall number
From: Ross Philipson <Ross.Philipson@xxxxxxxxxx>
Date: Wed, 13 Jul 2011 11:27:31 -0400
Accept-language: en-US
Acceptlanguage: en-US
Cc: James, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, McKenzie <James.McKenzie@xxxxxxxxxx>
Delivery-date: Wed, 13 Jul 2011 08:28:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110713152454.GA10754@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <831D55AF5A11D64C9B4B43F59EEBF720724926C135@xxxxxxxxxxxxxxxxxxxxxxxxx> <20110713152454.GA10754@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcxBcQWIZ45utSWnQqKuQp4HO7X3KwAAEM9w
Thread-topic: [Xen-devel] [PATCH 1/1] Reserve V4V hypercall number
OK, I will resubmit with language like that. I also forgot the VIRQ we use...


-----Original Message-----
From: Tim Deegan 
Sent: Wednesday, July 13, 2011 11:25 AM
To: Ross Philipson
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; James McKenzie
Subject: Re: [Xen-devel] [PATCH 1/1] Reserve V4V hypercall number

At 11:03 -0400 on 13 Jul (1310554989), Ross Philipson wrote:
> Reserve the V4V hypercall number to prevent its use prior to the 
> up-streaming of the rest of the V4V functionality.

When can we expect patches for the actual hypercall?  If it's not imminent, if 
would be better to use language like 22626:ceb508436e6e so as not to confuse 
readers of the code.  



Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, Xen Platform Team Citrix Systems UK Ltd.  (Company 
#02937203, SL9 0BG)

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>