From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Adrien Vergé" <adrienverge@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>,
Ben Dooks <ben.dooks@codethink.co.uk>,
Will Deacon <will.deacon@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
"zhangwei(Jovi)" <jovi.zhangwei@huawei.com>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH 0/3] ARM Coresight: Enhance ETM tracing control
Date: Tue, 3 Dec 2013 23:04:42 -0800 [thread overview]
Message-ID: <20131204070442.GA31665@kroah.com> (raw)
In-Reply-To: <CANsc=4VRLWhaVA15HrBEeM+FJC0tS+b5KKopDb7bP8nxzR8=zA@mail.gmail.com>
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
next prev parent reply other threads:[~2013-12-04 7:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 4:39 [PATCH 0/3] ARM Coresight: Enhance ETM tracing control Adrien Vergé
2013-12-04 7:04 ` Greg Kroah-Hartman [this message]
2013-12-04 16:52 ` Adrien Vergé
2013-12-04 17:07 ` Greg Kroah-Hartman
2013-12-04 21:12 ` Adrien Vergé
2013-12-04 23:02 ` Greg Kroah-Hartman
2013-12-05 3:49 ` Adrien Vergé
2013-12-05 4:01 ` Greg Kroah-Hartman
2013-12-05 20:12 ` Christopher Covington
2013-12-05 20:16 ` Greg Kroah-Hartman
2013-12-05 22:45 ` Christopher Covington
2013-12-05 23:26 ` Greg Kroah-Hartman
2013-12-05 23:54 ` Adrien Vergé
2013-12-06 0:06 ` Greg Kroah-Hartman
2013-12-06 0:23 ` Russell King - ARM Linux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131204070442.GA31665@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adrienverge@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ben.dooks@codethink.co.uk \
--cc=dietmar.eggemann@arm.com \
--cc=jovi.zhangwei@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rdunlap@infradead.org \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox