All of lore.kernel.org
 help / color / mirror / Atom feed
From: NAHieu <nahieu@gmail.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [RFC] Cleaning up /proc/xen
Date: Thu, 8 Sep 2005 17:09:36 +0900	[thread overview]
Message-ID: <5d7aca9505090801093be48e74@mail.gmail.com> (raw)
In-Reply-To: <431F97CC.9080007@us.ibm.com>

On 9/8/05, Anthony Liguori <aliguori@us.ibm.com> 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
> 

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.

  reply	other threads:[~2005-09-08  8:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-08  1:45 [RFC] Cleaning up /proc/xen Anthony Liguori
2005-09-08  8:09 ` NAHieu [this message]
2005-09-08 18:59   ` Anthony Liguori
2005-09-09  2:18     ` Jed Davis
2005-09-08 22:29 ` Daniel Stekloff
  -- strict thread matches above, loose matches on Subject: below --
2005-09-08  2:26 Ian Pratt
2005-09-08  2:50 ` Adam Heath
2005-09-08  2:51 ` Steven Hand
2005-09-08  3:24   ` Anthony Liguori
2005-09-08 16:39     ` Chris Wright
2005-09-08 12:54   ` Vincent Hanquez
2005-09-08  9:28 Ian Pratt
2005-09-08 12:54 ` Andrew Theurer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5d7aca9505090801093be48e74@mail.gmail.com \
    --to=nahieu@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.