From: Heiko Carstens Subject: Re: [ PATCH 2.6.16-rc3-xen 3/3] sysfs: export Xen hypervisor attributes to sysfs Date: Wed, 22 Feb 2006 14:19:18 +0100 Message-ID: <20060222131918.GC9295@osiris.boeblingen.de.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> <43FC61C4.30002@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <43FC61C4.30002@us.ibm.com> Sender: linux-kernel-owner@vger.kernel.org To: "Mike D. Day" Cc: Arjan van de Ven , Dave Hansen , xen-devel@lists.xensource.com, lkml , Greg KH List-Id: xen-devel@lists.xenproject.org On Wed, Feb 22, 2006 at 08:06:12AM -0500, Mike D. Day wrote: > 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. If it's not needed, why include it at all? Heiko