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: "Anthony Liguori" <aliguori@xxxxxxxxxx>, "John Levon" <levon@xxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] Sysfs Interface for balloon driver
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Thu, 21 Sep 2006 00:23:34 +0100
Cc: Satoshi Uchida <s-uchida@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 20 Sep 2006 16:24:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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> <451187D9.7080609@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acbc4n9ortLjkT7+RSOBxAZdxnfK3AAJ9aUw
Thread-topic: [Xen-devel] [PATCH] Sysfs Interface for balloon driver
> 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
> module parameter and appear in the sysfs module path.  I've always
> thought /sys/hypervisor ought to expose information from the

I don't think the memory target stuff is a driver. 'balloon' should not
appear in the name anyhow -- this stuff is getting ever more closely
integrated with Linux's core memory management anyhow, it's definitely
not a driver.

I sort of slightly buy Anthony's argument that /sys/hypervisor should
just expose information about the hypervisor.

/sys/devices/system/memory/{target,current,max,..} ?


Xen-devel mailing list