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 08:06:12 -0500 Message-ID: <43FC61C4.30002@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> <1140612969.2979.20.camel@laptopd505.fenrus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1140612969.2979.20.camel@laptopd505.fenrus.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Arjan van de Ven Cc: Dave Hansen , xen-devel@lists.xensource.com, Heiko Carstens , lkml , Greg KH List-Id: xen-devel@lists.xenproject.org Arjan van de Ven wrote: > 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 Yes, it is an optional function. The current implementation is a module that can be omitted from the configuration, built-in, or loadable. Mike