WARNING - OLD ARCHIVES

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/
Xen

xen-devel

[Top] [All Lists]

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

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [RFC PATCH 00/35] Xen i386 paravirtualization support
From: "Martin J. Bligh" <mbligh@xxxxxxxxxx>
Date: 2006年5月09日 08:12:33 -0700
Cc: Chris Wright <chrisw@xxxxxxxxxxxx>, virtualization@xxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
Delivery-date: 2006年5月10日 04:51:21 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060509150701.GA14050@xxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20060509084945.373541000@xxxxxxxxxxxx> <4460AC01.5020503@xxxxxxxxxx> <20060509150701.GA14050@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.7 (X11/20051013)
Christoph Hellwig wrote:
On Tue, May 09, 2006 at 07:49:37AM -0700, Martin J. Bligh wrote:
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.
It's also wrong. There's more than one hypervisor and Xen shouldn't just
grab this namespace. make it xen_ or xenhv_.
I think the intent was to create something generic enough for others to
use. There were other projects that already intended to use the same
model ... and please, lets not have one stack of this stuff for each
hypervisor. So in general, I think the approach is correct, I was just
whining about style stuff ;-)
M.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: [Xen-devel] Re: [RFC PATCH 00/35] Xen i386 paravirtualization support , Christoph Hellwig
Next by Date: [Xen-devel] Re: [RFC PATCH 03/35] Add Xen interface header files , Christoph Hellwig
Previous by Thread: [Xen-devel] Re: [RFC PATCH 00/35] Xen i386 paravirtualization support , Chris Wright
Next by Thread: [Xen-devel] VMX status report 9960:1e3977e029fd , Zheng, Jeff
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /