This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] [RFC] sysfs support for xen linux

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] [PATCH] [RFC] sysfs support for xen linux
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Wed, 11 Jan 2006 16:05:00 +0000
Cc: "Mike D. Day" <ncmike@xxxxxxxxxx>
Delivery-date: Wed, 11 Jan 2006 16:24:30 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43C52E6F.9090901@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <43C52E6F.9090901@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.1
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?


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