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

[Xen-devel] Re: [RFC PATCH 00/35] Xen i386 paravirtualization support

To: Chris Wright <chrisw@xxxxxxxxxxxx>
From: "Martin J. Bligh" <mbligh@xxxxxxxxxx>
Date: Tue, 09 May 2006 07:49:37 -0700
Cc: virtualization@xxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
Delivery-date: Wed, 10 May 2006 04:47:32 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Congrats on getting this thrashed out. A few comments, most of which are
boring style nits, but nonetheless ... will try to take a proper look
later.

General comment:

Why is this style used:

HYPERVISOR_foo_bar ?

ie the capitalization of HYPERVISOR. Doesn't seem to fit with the rest
of the kernel style.


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

Follow-Ups:
- [Xen-devel] Re: [RFC PATCH 00/35] Xen i386 paravirtualization support
  - From: Christoph Hellwig

References:
- [Xen-devel] [RFC PATCH 00/35] Xen i386 paravirtualization support
  - From: Chris Wright

Prev by Date: [Xen-devel] Re: [RFC PATCH 35/35] Add Xen virtual block device driver.
Next by Date: [Xen-devel] Re: [RFC PATCH 15/35] subarch support for controlling interrupt delivery
Previous by thread: [Xen-devel] [RFC PATCH 10/35] Add a new head.S start-of-day file for booting on Xen.
Next by thread: [Xen-devel] Re: [RFC PATCH 00/35] Xen i386 paravirtualization support
Index(es):
- Date
- Thread

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