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: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] Sysfs Interface for balloon driver
From: "Satoshi Uchida" <s-uchida@xxxxxxxxxxxxx>
Date: Fri, 22 Sep 2006 11:15:42 +0900
Cc: 'Ian Pratt' <m+Ian.Pratt@xxxxxxxxxxxx>, 'Anthony Liguori' <aliguori@xxxxxxxxxx>, 'John Levon' <levon@xxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 21 Sep 2006 19:16:35 -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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acbd7QDw/naZBMZiRquPfBBtVnudIA==
Thanks Ian, Anthony, John.

> 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.

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

OK.


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

I also think such.

However, where should VM (domain) information is located?
Such location will be probably appeared in future.
And, will a reader (or developer) be perplexed at location which needed 
information is stored?
Currently, information about virtualization stored sparsely.
Should make a location for gathering such information?

It is important not to make the user conscious which native or VM.
It might be better to store information in general location and to use symlink 
for gathering location.
By such reason, balloon information may be better to locate under 
/sys/class/mem.


Regards,
Satoshi UCHIDA

Attachment: smime.p7s
Description: S/MIME cryptographic signature

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