From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Levon Subject: Re: [PATCH] Sysfs Interface for balloon driver Date: Wed, 20 Sep 2006 16:20:06 +0100 Message-ID: <20060920152006.GA32328@totally.trollied.org> References: <20060920011235.GA7931@totally.trollied.org> <00c401c6dc60$f22303f0$4c87380a@ad.spf.cl.nec.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <00c401c6dc60$f22303f0$4c87380a@ad.spf.cl.nec.co.jp> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Satoshi Uchida Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Wed, Sep 20, 2006 at 12:00:36PM +0900, Satoshi Uchida wrote: > In this time, it locate by following reason. > A balloon driver is similar to front-end driver. Not really. Front-end drivers are real drivers, thus it makes sense for them to appear to be attached to a bus, even if that bus is virtual. > I feel that the term "hypervisor" means VMM in general. > And a balloon exists for VM, and not for VMM. I don't understand what you mean here. > Therefore, I think that such information should not be located to /sys/hypervisor. Anyone else have an opinion? > 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