Subject: Re: [ PATCH 2.6.16-rc3-xen 3/3] sysfs: export Xen hypervisor
	attributes to sysfs
From: Arjan van de Ven <arjan@infradead.org>
To: "Mike D. Day" <ncmike@us.ibm.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
       Dave Hansen <haveblue@us.ibm.com>, xen-devel@lists.xensource.com,
       lkml <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>
In-Reply-To: <43FC5B1D.5040901@us.ibm.com>
References: <43FB2642.7020109@us.ibm.com>
	 <1140542130.8693.18.camel@localhost.localdomain>
	 <20060222123250.GB9295@osiris.boeblingen.de.ibm.com>
	 <43FC5B1D.5040901@us.ibm.com>
Content-Type: text/plain
Date: Wed, 22 Feb 2006 13:56:09 +0100
Message-Id: <1140612969.2979.20.camel@laptopd505.fenrus.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 987
Lines: 24

On Wed, 2006-02-22 at 07:37 -0500, Mike D. Day wrote:
> Heiko Carstens wrote:
> >> You can also set the standard that any other hypervisor has to
> >> follow! :)
> > 
> > I doubt that there is much that different hypervisors can share.
> > Why should all this be visible for user space anyway? What's the purpose?
> 
> In Xen at least, hypervisor management and control programs run in user 
> space in a "privileged" domain (or virtual machine). Systems management 
> agents in user space on the privileged domain need to know this 
> information, and sysfs is a good place to expose it.


surely those tools already talk to the hypervisor.. so they might as
well ask for this information themselves... no need to bloat the kernel
for this


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/