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

[Xen-devel] [PATCH 1/1] Placeholder for V4V hypercall and VIRQ numbers

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
From: Ross Philipson <Ross.Philipson@xxxxxxxxxx>
Date: Wed, 13 Jul 2011 11:37:00 -0400
Accept-language: en-US
Acceptlanguage: en-US
Cc: James McKenzie <James.McKenzie@xxxxxxxxxx>
Delivery-date: Wed, 13 Jul 2011 08:37:39 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Thread-index: AcxBcgKJ+qyKUmkWRD+h/sd2V5KhHA==
Thread-topic: [PATCH 1/1] Placeholder for V4V hypercall and VIRQ numbers

Placeholder for V4V hypercall and VIRQ numbers.

The V4V Xen functionality is currently in our product trees for XenClient but is not yet in a state suitable for submission. We hope to make available the rest of the V4V functionality in the not too distant future. Since these values are already in use in our product, we would like to reserve them in open source to prevent issues or incompatibilities down the road.

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

Attachment: v4v-hypercall-virq-numbers.patch
Description: v4v-hypercall-virq-numbers.patch

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

Follow-Ups:
- [Xen-devel] Re: [PATCH 1/1] Placeholder for V4V hypercall and VIRQ numbers
  - From: James

Prev by Date: Re: [Xen-devel] Re: Question on "xen-blkfront: handle Xen major numbers other than XENVBD"
Next by Date: [Xen-devel] Re: [PATCH 1/1] Placeholder for V4V hypercall and VIRQ numbers
Previous by thread: [Xen-devel] Passive and Active ACPI Thermal control under Xen?
Next by thread: [Xen-devel] Re: [PATCH 1/1] Placeholder for V4V hypercall and VIRQ numbers
Index(es):
- Date
- Thread

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