[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [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 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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.