From: Dave Hansen Subject: Re: [RFC] [PATCH] sysfs support for Xen attributes Date: Wed, 11 Jan 2006 17:32:54 -0800 Message-ID: <1137029574.11331.11.camel@localhost.localdomain> References: <43C53DA0.60704@us.ibm.com> <20060111230704.GA32558@kroah.com> <43C5A199.1080708@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <43C5A199.1080708@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Mike D. Day" Cc: Greg KH , xen-devel@lists.xensource.com, lkml List-Id: xen-devel@lists.xenproject.org On Wed, 2006-01-11 at 19:23 -0500, Mike D. Day wrote: > Greg KH wrote: > > > Why is xen special from the rest of the kernel in regards to adding > > files to sysfs? What does your infrastructure add that is not currently > > already present for everyone to use today? > > I think it comes down to simplification for non-driver code, which is > admittedly not the mainstream use model for sysfs. You might also want to take a good look at how things like ACPI do exports in sysfs: in /sys/firmware. Not that ACPI is a good example of _anything_ :), but that is probably more compliant with the current model than your own /sys/xen. Do you have a definitive list of things that you want to export? Are they things that come and go, or are they static? Do you want hotplug events for them? Some of those things may be better fit platform devices. Notice that ACPI has entries in /sys/firmware/acpi and /sys/devices/system/acpi. -- Dave