From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: [RFC] Cleaning up /proc/xen Date: Wed, 07 Sep 2005 20:45:48 -0500 Message-ID: <431F97CC.9080007@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Today, in /proc/xen we have: /proc/xen/balloon - displays information about memory allocations and allows for ballooning by echoing a byte value into file /proc/xen/privcmd - allows for userspace invocation of hypercalls and mapping of other domains memory /proc/xen/grant - allows grant table operations to be accessed from userspace /proc/xen/xenbus - allows xenbus to be accessed from userspace (in domUs) I propose we do the following: Change /proc/xen/{privcmd,grant,xenbus} to character devices (that use random major/minors; we'll always access them by name). We have a few options for /proc/xen/balloon. We could: 1) Get rid of it completely--not sure it's a good idea but it's been suggested since it's redundant (in dom0 at least). 2) Move it to /proc/sys/ 3) Move it to /sys/xen I'm partial to the last option (maybe even /sys/hypervisor/xen--that seems to compliment /sys/firmware). Thoughts? Regards, Anthony Liguori