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 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [PATCH 2.6.16-rc6-xen] export Xen Hypervisor attributes

To: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 2.6.16-rc6-xen] export Xen Hypervisor attributes to sysfs
From: "Mike D. Day" <ncmike@xxxxxxxxxx>
Date: Tue, 21 Mar 2006 06:32:53 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, gregkh@xxxxxxx
Delivery-date: Tue, 21 Mar 2006 11:34:01 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1142939444.3077.55.camel@xxxxxxxxxxxxxxxxxxxxx>
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: <200603202335.k2KNZEjo005673@xxxxxxxxxxxxxxxxxxxxx> <1142925269.3077.10.camel@xxxxxxxxxxxxxxxxxxxxx> <441FD8F3.208@xxxxxxxxxx> <1142939444.3077.55.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5 (Macintosh/20051201)
Arjan van de Ven wrote:

I appreciate the counter argument as well, but think this should be a configurable option.

"a config option" is a cop-out. By proposing a config option you even
admit it's not essential for userspace. The last thing this should be is
a config option; it either is needed and important, and should be there
always, or it's redundant and should be done in userspace. "A config
option" is just admitting that it is the later, but that you need to
justify the time you spent on the kernel patch somewhere ;-)

No, not at all. There are two types of Xen kernels: privileged and non-privileged. A privileged kernel has access to real hardware devices. This patch is intended for privileged xen kernel. That's why it needs to be a configurable option.

Mike

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