From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Mike D. Day" Subject: Re: [PATCH] [RFC] sysfs support for xen linux Date: Tue, 10 Jan 2006 07:58:09 -0500 Message-ID: <43C3AF61.8090102@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 5:13 AM Keir Fraser wrote: > xen_sysfs.c looks to contain a lot of code that I would expect to be > part of a generic sysfs library. Does every subsystem that uses sysfs > really have to implement all that stuff for itself? No, they don't. Drivers get sysfs attributes by using the driver core (registering a subsystem, defining attributes, etc.). However, if all you want to do is create and remove files under /sys (without using all the driver core), there is no simple way to do so (at least not that I could find). I am assuming that folks will want something that works like /proc does now. I wrote xen_sysfs.c to provide simple sysfs interfaces for non-drivers. It seems as though it would be a crime against nature to write a device driver just to create a file under /sys. > (I am not a sysfs expert, by the way :-) . Neither am I, but perhaps some such person will give feedback. :-) Mike -- Mike D. Day STSM and Architect, Open Virtualization IBM Linux Technology Center ncmike@us.ibm.com