This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] Sysfs Interface for balloon driver

To: Satoshi Uchida <s-uchida@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Sysfs Interface for balloon driver
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Wed, 20 Sep 2006 16:20:06 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 20 Sep 2006 08:20:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <00c401c6dc60$f22303f0$4c87380a@xxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20060920011235.GA7931@xxxxxxxxxxxxxxxxxxxx> <00c401c6dc60$f22303f0$4c87380a@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
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.


Xen-devel mailing list