All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike D. Day" <ncmike@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] [RFC] sysfs support for xen linux
Date: Wed, 11 Jan 2006 11:12:31 -0500	[thread overview]
Message-ID: <43C52E6F.9090901@us.ibm.com> (raw)

On 5:21 AM Keir Fraser wrote:
> Well, here's a question, and I really don't know the answer: It of 
> course makes sense that the kernel maintainers want drivers to 
> install themselves under /sys, and fit in with the whole kobject and 
> hotplug infrastructure. But, for a few odds-and-ends special files 
> that don't really relate to a device, is /proc also out of bounds 
> these days? Seems to me that the kernel proc interfaces were designed 
> to have a few random files thrown at them, in a way that the sysfs 
> interfaces aren't. If the argument is really that random special 
> files are a bad idea, that would continue to hold regardless of 
> whether we move e.g., /proc/xen/privcmd to /sys.

I think that /sys is clearly the right place to put information about 
Xen, including version, domains and domain info, and perhaps info about 
xenstore. This is according to feedback received when I submitted my 
first (braindead) patch moving /proc/xen to /proc/sys/xen.

Still I agree that we need input from lkml and am going to cross-post an 
  RFC so we can move forward.

regards,

Mike


-- 

Mike D. Day
STSM and Architect, Open Virtualization
IBM Linux Technology Center
ncmike@us.ibm.com

             reply	other threads:[~2006-01-11 16:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11 16:12 Mike D. Day [this message]
2006-01-11 16:05 ` [PATCH] [RFC] sysfs support for xen linux Mark Williamson
2006-01-11 16:35   ` Keir Fraser
2006-01-11 16:40     ` Ronald G Minnich
  -- strict thread matches above, loose matches on Subject: below --
2006-01-11 16:28 Mike D. Day
2006-01-11 16:28 ` Mark Williamson
2006-01-11 16:50   ` Anthony Liguori
2006-01-11 17:03     ` Daniel Stekloff
2006-01-10 12:58 Mike D. Day
2006-01-11 10:21 ` Keir Fraser
2006-01-09 23:35 Mike D. Day
2006-01-10  1:09 ` Christopher G. Stach II
2006-01-10 10:13 ` Keir Fraser
2006-01-10 13:23 ` Gawain Lynch
2006-01-12  1:44 ` Chris Wright

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=43C52E6F.9090901@us.ibm.com \
    --to=ncmike@us.ibm.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --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.