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] [RFC] Cleaning up /proc/xen

To: Anthony Liguori <aliguori@xxxxxxxxxx>
Subject: Re: [Xen-devel] [RFC] Cleaning up /proc/xen
From: Daniel Stekloff <dsteklof@xxxxxxxxxx>
Date: Thu, 08 Sep 2005 15:29:53 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 08 Sep 2005 22:28:09 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <431F97CC.9080007@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <431F97CC.9080007@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2005-09-07 at 20:45 -0500, Anthony Liguori wrote:
> 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?


Hi Anthony, 

If you're serious about option 3, it might be a good idea to post to
lkml and cc the sysfs maintainer - Greg KH. He might have some
suggestions.

Thanks,

Dan


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