From: Ronald G Minnich <rminnich@lanl.gov>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: "Mike D. Day" <ncmike@us.ibm.com>,
xen-devel@lists.xensource.com,
Mark Williamson <mark.williamson@cl.cam.ac.uk>
Subject: Re: [PATCH] [RFC] sysfs support for xen linux
Date: Wed, 11 Jan 2006 09:40:46 -0700 [thread overview]
Message-ID: <43C5350E.5040205@lanl.gov> (raw)
In-Reply-To: <aeb310aa4745fa49bb8592972bda6894@cl.cam.ac.uk>
Keir Fraser wrote:
>
> Probably true, but then it's a pain either needing to create device
> files in /dev, or interface with the devfs/udev du jour. I suppose we
> already have that issue with /dev/xen/evtchn though, and creating the
> device node can be hidden in libxc.
we've observed that as well, one performance toolkit uses a /proc file
to avoid the mess of "devfs/udev du jour" (what a great description ...).
So maybe it oughtta be a device, who knows, but the sys file will save a
lot of trouble.
ron
next prev parent reply other threads:[~2006-01-11 16:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 16:12 [PATCH] [RFC] sysfs support for xen linux Mike D. Day
2006-01-11 16:05 ` Mark Williamson
2006-01-11 16:35 ` Keir Fraser
2006-01-11 16:40 ` Ronald G Minnich [this message]
-- 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=43C5350E.5040205@lanl.gov \
--to=rminnich@lanl.gov \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=mark.williamson@cl.cam.ac.uk \
--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 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.