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: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] [RFC] sysfs support for xen linux
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Wed, 11 Jan 2006 10:50:56 -0600
Cc: "Mike D. Day" <ncmike@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 11 Jan 2006 16:57:55 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200601111628.49811.mark.williamson@xxxxxxxxxxxx>
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: <43C53237.2020802@xxxxxxxxxx> <200601111628.49811.mark.williamson@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.7 (X11/20051013)
Mark Williamson wrote:

Yes, true. I think privcmd might be more appropriate for /proc, but
would like to see how it works as a binary file under /sys. ioctl's are
not supported by sysfs that I can see, so privcmd would have to be a
read/write interface.

Regardless of privcmd there are numerous simple attributes related to
Xen that are consistent with "zen" of sysfs. :-)

Agreed. It's an ideal place for many of the things that are in proc, and many things we'd want to add in the future.

You could possibly abuse sysfs into supporting ioctl but I'm pretty sure the kernel people would find that quite distressing ;-) I had the impression binary files under sysfs were also a no-no (all meant to be cat-able - addressing one of the other problems of /proc), but I could be mistaken.
There was a discussion a while back about this.


I think the consensus was to move any ioctl interface to a char device and everything else to sysfs.

You'll probably want a proper kobject hierarchy too which means working with GKH et al to figure out where out stuff should be (/sys/hypervisor/xen??)


Anthony Liguori


Xen-devel mailing list