WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: John Levon <levon@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Sysfs Interface for balloon driver
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Wed, 20 Sep 2006 13:26:33 -0500
Cc: Satoshi Uchida <s-uchida@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 20 Sep 2006 11:27:08 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060920152006.GA32328@xxxxxxxxxxxxxxxxxxxx>
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> <20060920152006.GA32328@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.5 (X11/20060728)
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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel