My impression is was that sysfs files are mostly meant to be very simple
get/set attributes and not have magic properties like the privcmd file - do
any other sysfs files even support ioctls().
Also, for things like privcmd() which are used to perform operations, isn't it
cleanest to make them a character device than a proc file?
$0.02,
Mark
On Wednesday 11 January 2006 16:12, Mike D. Day wrote:
> 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
--
> Just a question. What use is a unicyle with no seat? And no pedals!
Me: To answer a question with a question: What use is a skateboard?
> Skateboards have wheels.
Me: My wheel has a wheel!
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home