From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Otte Subject: Re: [PATCH 05/10] AXFS: axfs_profiling.c Date: Thu, 21 Aug 2008 12:20:16 +0200 Message-ID: <48AD4160.7000408@de.ibm.com> References: <48AD00F8.1030004@gmail.com> <48AD2AFF.5060609@de.ibm.com> <1219308560.2988.247.camel@pmac.infradead.org> Reply-To: carsteno@de.ibm.com Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1219308560.2988.247.camel@pmac.infradead.org> Sender: linux-embedded-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: David Woodhouse Cc: carsteno@de.ibm.com, jaredeh@gmail.com, Linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org, linux-mtd , =?ISO-8859-1?Q?J=F6rn_Engel?= , tim.bird@AM.SONY.COM, nickpiggin@yahoo.com.au David Woodhouse wrote: > On Thu, 2008-08-21 at 10:44 +0200, Carsten Otte wrote: >> Jared Hulbert wrote: >>> Profiling is a fault instrumentation and /proc formating system. >>> This is used to get an accurate picture of what the pages are actually used. >>> Using this info the image can be optimized for XIP > >> Exporting profiling data for a file system in another file system >> (/proc) seems not very straigtforward to me. I think it is worth >> considering to export this information via the same mount point. > > I would have said sysfs, rather than 'the same mount point'. Well, filesystems are usually not represented in the device model. It'd be possible to add a system device for it, but that does'nt feel like the right solution to me.