Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759189AbYGBVk0 (ORCPT ); Wed, 2 Jul 2008 17:40:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752657AbYGBVkP (ORCPT ); Wed, 2 Jul 2008 17:40:15 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:38749 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753805AbYGBVkO (ORCPT ); Wed, 2 Jul 2008 17:40:14 -0400 From: "Rafael J. Wysocki" To: Greg KH Subject: Removing sysdevs? (was: Re: Is sysfs the right place to get cache and CPU topology info?) Date: Wed, 2 Jul 2008 23:41:44 +0200 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) Cc: Andi Kleen , Nathan Lynch , Andrew Morton , Paul Mackerras , torvalds@linux-foundation.org, linux-kernel@vger.kernel.org References: <18539.8141.683072.967851@cargo.ozlabs.ibm.com> <486B9B3A.4060709@firstfloor.org> <20080702185145.GB20938@kroah.com> In-Reply-To: <20080702185145.GB20938@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807022341.44965.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1785 Lines: 38 On Wednesday, 2 of July 2008, Greg KH wrote: > On Wed, Jul 02, 2008 at 05:14:02PM +0200, Andi Kleen wrote: > > Nathan Lynch wrote: > > > Andi Kleen wrote: > > >> Andrew Morton writes: > > >>> sysfs is part of the kernel ABI. We should design our interfaces there > > >>> as carefully as we design any others. > > >> The basic problem is that sysfs exports an internal kernel object model > > >> and these tend to change. To really make it stable would require > > >> splitting it into internal and presented interface. > > > > > > True, but... /sys/devices/system/cpu has been there since around 2.6.5 > > > iirc. A google code search for that path shows plenty of programs > > > (including hal) that hard-code it. Exposed object model or not, > > > changing that path would break lots of software. > > > > Yes it would. > > > > But Greg is making noises of getting rid of sysdevs and it wouldn't > > surprise me if that ended up being user visible since most object > > model changes end up being visible. > > I hope to make sysdevs go away in such a manner that the sysfs tree does > not change at all. That's my goal, but we still have a long ways to go > before we can even consider attempting to do this, so don't worry about > putting things in this location if you feel it is the best fit. Speaking of which, I'm very interested in the removing of sysdevs, since they don't fit into the new suspend/hibernation framework I'm working on. Can you please tell me what the plan is? Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/