From: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Greg KH <greg@kroah.com>,
xen-devel@lists.xensource.com,
lkml <linux-kernel@vger.kernel.org>,
"Mike D. Day" <ncmike@us.ibm.com>
Subject: Re: [Xen-devel] Re: [RFC] [PATCH] sysfs support for Xen attributes
Date: Thu, 12 Jan 2006 10:04:30 +0000 [thread overview]
Message-ID: <00466d4b0eb7fe1603cd7f54448d37ff@cl.cam.ac.uk> (raw)
In-Reply-To: <1137029574.11331.11.camel@localhost.localdomain>
On 12 Jan 2006, at 01:32, Dave Hansen wrote:
> Do you have a definitive list of things that you want to export? Are
> they things that come and go, or are they static? Do you want hotplug
> events for them? Some of those things may be better fit platform
> devices. Notice that ACPI has entries in /sys/firmware/acpi
> and /sys/devices/system/acpi.
This is a good set of questions. We have about half dozen files in
/proc/xen right now. One is an obvious canididate to stick in /dev, as
it has primarily an ioctl() interface. The remainder are static, are
read-only or read-write with ascii text, and we don't want hotplug
events and other baggage.
Maybe making these attributes of a Xen system device makes sense. Are
there examples in the kernel of other subsystems/modules with a similar
miscellaneous set of files?
-- Keir
next prev parent reply other threads:[~2006-01-12 9:58 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 17:17 Mike D. Day
2006-01-11 17:19 ` Arjan van de Ven
2006-01-11 17:56 ` Stephen Hemminger
2006-01-11 18:45 ` Dave Hansen
2006-01-11 23:07 ` Greg KH
2006-01-12 0:23 ` Mike D. Day
2006-01-12 0:57 ` Greg KH
2006-01-12 1:49 ` Mike D. Day
2006-01-12 2:17 ` [Xen-devel] " Mark Williamson
2006-01-12 7:10 ` Greg KH
2006-01-12 14:44 ` [Xen-devel] " Mike D. Day
2006-01-12 14:53 ` Mark Williamson
2006-01-12 15:42 ` Anthony Liguori
2006-01-12 15:57 ` Anthony Liguori
2006-01-12 17:34 ` Greg KH
2006-01-12 18:44 ` Anthony Liguori
2006-01-12 17:43 ` Greg KH
2006-01-12 9:10 ` Dave Hansen
2006-01-12 14:52 ` [Xen-devel] " Mike D. Day
2006-01-12 15:28 ` Dave Hansen
2006-01-12 15:50 ` Mike D. Day
2006-01-12 12:54 ` Gerd Hoffmann
2006-01-12 13:21 ` Arjan van de Ven
2006-01-12 14:42 ` Gerd Hoffmann
2006-01-12 17:39 ` Greg KH
2006-01-12 18:53 ` Anthony Liguori
2006-01-12 18:55 ` Arjan van de Ven
2006-01-12 18:59 ` Anthony Liguori
2006-01-12 19:11 ` Mike D. Day
2006-01-12 19:31 ` Greg KH
2006-01-12 19:08 ` Greg KH
2006-01-12 19:18 ` Mike D. Day
2006-01-12 19:30 ` Greg KH
2006-01-12 17:38 ` Greg KH
2006-01-12 1:32 ` Dave Hansen
2006-01-12 10:04 ` Keir Fraser [this message]
2006-01-12 15:14 ` [Xen-devel] " Dave Hansen
2006-01-12 15:06 ` Mark Williamson
2006-01-12 15:26 ` Keir Fraser
2006-01-12 15:37 ` Dave Hansen
2006-01-12 15:49 ` Anthony Liguori
2006-01-11 23:31 ` Pavel Machek
2006-01-12 19:01 ` Greg KH
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=00466d4b0eb7fe1603cd7f54448d37ff@cl.cam.ac.uk \
--to=keir.fraser@cl.cam.ac.uk \
--cc=greg@kroah.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncmike@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®