From mboxrd@z Thu Jan 1 00:00:00 1970 From: NAHieu Subject: Re: [RFC] Cleaning up /proc/xen Date: Thu, 8 Sep 2005 17:09:36 +0900 Message-ID: <5d7aca9505090801093be48e74@mail.gmail.com> References: <431F97CC.9080007@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <431F97CC.9080007@us.ibm.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Anthony Liguori Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 9/8/05, Anthony Liguori wrote: > Today, in /proc/xen we have: >=20 > /proc/xen/balloon - displays information about memory allocations and > allows for ballooning by echoing a byte value into file >=20 > /proc/xen/privcmd - allows for userspace invocation of hypercalls and > mapping of other domains memory >=20 > /proc/xen/grant - allows grant table operations to be accessed from > userspace >=20 > /proc/xen/xenbus - allows xenbus to be accessed from userspace (in dom= Us) >=20 > I propose we do the following: >=20 > 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: >=20 > 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 >=20 The good thing about /proc is that we do not need to register any major/minor stuffs (which is very annoying), like what we do with device. So I vote for moving things to under /sys. But hold on, that would not be compatible with others OS like *BSD, correct ? Thanks, Hieu.