Message-ID: <43FC5B1D.5040901@us.ibm.com>
Date: Wed, 22 Feb 2006 07:37:49 -0500
From: "Mike D. Day" <ncmike@us.ibm.com>
User-Agent: Thunderbird 1.5 (Macintosh/20051201)
MIME-Version: 1.0
To: Heiko Carstens <heiko.carstens@de.ibm.com>
CC: Dave Hansen <haveblue@us.ibm.com>, xen-devel@lists.xensource.com,
       lkml <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>
Subject: Re: [ PATCH 2.6.16-rc3-xen 3/3] sysfs: export Xen hypervisor attributes
 to sysfs
References: <43FB2642.7020109@us.ibm.com> <1140542130.8693.18.camel@localhost.localdomain> <20060222123250.GB9295@osiris.boeblingen.de.ibm.com>
In-Reply-To: <20060222123250.GB9295@osiris.boeblingen.de.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 770
Lines: 22

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.

Mike

-- 


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