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

Ian Pratt wrote:
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.

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,..} ?

Works for me.

Regards,

Anthony Liguori

Ian





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