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

["Satoshi Uchida" <s-uchida@xxxxxxxxxxxxx>]

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

smime.p7s
Description: S/MIME cryptographic signature

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