From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [PATCH] Sysfs Interface for balloon driver Date: Wed, 20 Sep 2006 13:26:33 -0500 Message-ID: <451187D9.7080609@us.ibm.com> References: <20060920011235.GA7931@totally.trollied.org> <00c401c6dc60$f22303f0$4c87380a@ad.spf.cl.nec.co.jp> <20060920152006.GA32328@totally.trollied.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20060920152006.GA32328@totally.trollied.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: John Levon Cc: Satoshi Uchida , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org John Levon wrote: >> Therefore, I think that such information should not be located to /sys/hypervisor. >> > > Anyone else have an opinion? > I *always* have an opinion :-) Personally, I think the ballooning information ought to be exposed as a module parameter and appear in the sysfs module path. I've always thought /sys/hypervisor ought to expose information from the hypervisor. Regards, Anthony Liguori >> Should new location make for storing such (VM's) information ? >> For example, as following. >> /sys/virtualization -+--- domain >> +--- hypervisor >> > > Why would we need this? We already have xenstore for representing other > domain's information, and /sys/ is always specific to that particular > operating system instantiation. > > regards > john > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > >