[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
From: Ross Philipson <Ross.Philipson@xxxxxxxxxx>
Date: Wed, 13 Jul 2011 11:03:09 -0400
Accept-language: en-US
Acceptlanguage: en-US
Cc: James McKenzie <James.McKenzie@xxxxxxxxxx>
Delivery-date: Wed, 13 Jul 2011 08:05:23 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Thread-index: AcxBbeR/0/dI+8A2SqOBrBZ+KLNpcQ==
Thread-topic: [PATCH 1/1] Reserve V4V hypercall number

Reserve the V4V hypercall number to prevent its use prior to the up-streaming of the rest of the V4V functionality.

Signed-off-by: Ross Philipson <ross.philipson@xxxxxxxxxx>

Attachment: v4v-hypercall-number.patch
Description: v4v-hypercall-number.patch

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

Follow-Ups:
- Re: [Xen-devel] [PATCH 1/1] Reserve V4V hypercall number
  - From: Tim Deegan

Prev by Date: Re: [Xen-devel] syncing wall clock time from Dom0 to hypervisor
Next by Date: Re: [Xen-devel] syncing wall clock time from Dom0 to hypervisor
Previous by thread: Re: [Xen-devel] syncing wall clock time from Dom0 to hypervisor
Next by thread: Re: [Xen-devel] [PATCH 1/1] Reserve V4V hypercall number
Index(es):
- Date
- Thread

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.