[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131204070442.GA31665@kroah.com>
Date: Tue, 3 Dec 2013 23:04:42 -0800
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Adrien Vergé <adrienverge@...il.com>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Russell King <linux@....linux.org.uk>,
Ben Dooks <ben.dooks@...ethink.co.uk>,
Will Deacon <will.deacon@....com>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
"zhangwei(Jovi)" <jovi.zhangwei@...wei.com>,
Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCH 0/3] ARM Coresight: Enhance ETM tracing control
On Tue, Dec 03, 2013 at 11:39:21PM -0500, Adrien Vergé wrote:
> Usage of ETM tracing facility is currently very limited: user can
> only start/stop tracing. This set of patches enables management of
> address combinations and PIDs that trigger tracing.
>
> ETM management was done via sysfs entries (trace_info,
> trace_running...), this code adds trace_addrrange and trace_pid to
> let the user read/write custom values.
I have lots to say about this from a sysfs point of view, but first, why
is it in sysfs at all? Shouldn't all of this be in debugfs?
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists