From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: /proc/xen -> /proc/sys/xen ? Date: Tue, 03 May 2005 13:38:52 -0500 Message-ID: <4277C53C.20802@us.ibm.com> References: <79bd2a4f05b067a03d37e78e08a02ac1@cl.cam.ac.uk> <200505031729.37114.mark.williamson@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200505031729.37114.mark.williamson@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Mark Williamson Cc: Ian Pratt , Mike Wray , xen-devel@lists.xensource.com, Dan Stekloff List-Id: xen-devel@lists.xenproject.org Mark Williamson wrote: >I suspect the balloon driver file could usefully live with the VM settings - >as Rik said, such a device could be useful for other VMMs. > > While we're on the subject, what's everyone's thoughts on exporting domain information within sysfs in a /proc/ style (perhaps /sys/xen/) instead of exposing the getdomaininfo hypercall to userspace? While Linux-centric, it provides a pretty clean way to make sure that we can always query settable information. Regards, Anthony Liguori