From: "Mike D. Day" Subject: Re: [ PATCH 2.6.16-rc3-xen 3/3] sysfs: export Xen hypervisor attributes to sysfs Date: Wed, 22 Feb 2006 07:37:49 -0500 Message-ID: <43FC5B1D.5040901@us.ibm.com> References: <43FB2642.7020109@us.ibm.com> <1140542130.8693.18.camel@localhost.localdomain> <20060222123250.GB9295@osiris.boeblingen.de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20060222123250.GB9295@osiris.boeblingen.de.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Heiko Carstens Cc: Greg KH , xen-devel@lists.xensource.com, Dave Hansen , lkml List-Id: xen-devel@lists.xenproject.org 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 --