From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 3 Oct 2018 07:32:33 -0700 From: Greg Kroah-Hartman To: Jiri Kosina Message-ID: <20181003143233.GA29980@kroah.com> References: <20181002161730.GA7119@kroah.com> <20181002163001.GA11068@kroah.com> <20181002183743.78eac32d@coco.lan> <0e19e6d0-47bd-d57f-8e31-e3521c467fe0@kernel.org> <20181002222238.GA11788@kroah.com> <20181003125916.GB21043@quack2.suse.cz> <20181003134012.GA13071@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: Mauro Carvalho Chehab , ksummit Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Moving debugfs file systems into sysfs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, Oct 03, 2018 at 03:44:37PM +0200, Jiri Kosina wrote: > On Wed, 3 Oct 2018, Greg Kroah-Hartman wrote: > > > > Not really. We need those configs to be enabled to be able to troubleshoot > > > customer's problems - e.g., asking customer to enable some trace points or > > > show some stats from debugfs is pretty common... > > > > trace points should not be in debugfs. And what stats are in debugfs > > that are not availble in other tools? If you rely on them, shouldn't we > > move them to a "stable" location so that they can always be accessed? > > So I for example quite often make use of the HID debugfs entries both for > reading the descriptor, and also for analyzing the parsed events (which > appear there as well). for descriptors, both usb and pci expose them through other means that are always present, perhaps you want to do the same thing for hid? > Surely it can be moved whereever else (where?), but it seems to fit to > debugfs (it's used solely to debug dysfunctional devices / linux with > those devices), and provides exactly the data you need from the owner of > the system to provide in order to be able to debug remotely. hidfs might be needed to match usbfs :) thanks, greg k-h