From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Frederic Weisbecker" <fweisbec@gmail.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Török Edwin" <edwintorok@gmail.com>,
"Jason Baron" <jbaron@redhat.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -v2] tracing: lockdep tracepoints
Date: Wed, 4 Mar 2009 12:43:19 +0100 [thread overview]
Message-ID: <20090304114319.GA4916@elte.hu> (raw)
In-Reply-To: <1236166375.5330.7209.camel@laptop>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Wed, 2009-03-04 at 12:23 +0100, Frederic Weisbecker wrote:
> > > ---
> > > Subject: tracing: lockdep tracepoints
> > > From: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > > Date: Tue Mar 03 22:03:08 CET 2009
> > >
> > > Augment the traces with lock names when lockdep is available:
> > >
> > > 1) | down_read_trylock() {
> > > 1) | _spin_lock_irqsave() {
> > > 1) | /* lock_acquire: name: &sem->wait_lock */
> > > 1) 4.201 us | }
> > > 1) | _spin_unlock_irqrestore() {
> > > 1) | /* lock_release: name: &sem->wait_lock */
> >
> > Nice idea.
> > I would just suggest to drop the "name:" since the comment is intuitive enough
> > to figure out what we have after lock_{release,acquire}:
>
> Makes sense I guess..
>
> Here goes.. one s/name: //g later
>
> ---
> Subject: tracing: lockdep tracepoints
> From: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Date: Tue Mar 03 22:03:08 CET 2009
>
> Augment the traces with lock names when lockdep is available:
>
> 1) | down_read_trylock() {
> 1) | _spin_lock_irqsave() {
> 1) | /* lock_acquire: &sem->wait_lock */
> 1) 4.201 us | }
> 1) | _spin_unlock_irqrestore() {
> 1) | /* lock_release: &sem->wait_lock */
> 1) 3.523 us | }
> 1) | /* lock_acquire: try read &mm->mmap_sem */
> 1) + 13.386 us | }
very nice! :-)
> 1) 1.460 us | page_add_file_rmap();
> 1) | _spin_unlock() {
> 1) | /* lock_release: __pte_lockptr(page) */
> 1) 3.115 us | }
> 1) | unlock_page() {
> 1) 1.421 us | page_waitqueue();
> 1) 1.220 us | __wake_up_bit();
> 1) 6.519 us | }
btw., we might want to add tracepoints for
pagelock-acquire/release events too?
> +TRACE_FORMAT(lock_contended,
> + TPPROTO(struct lockdep_map *lock, unsigned long ip),
> + TPARGS(lock, ip),
> + TPFMT("%s", lock->name)
> + );
Would it be possible to use the C syntax tracepoints perhaps?
They are bigger:
TRACE_EVENT_FORMAT(sched_switch,
TPPROTO(struct rq *rq, struct task_struct *prev,
struct task_struct *next),
TPARGS(rq, prev, next),
TPFMT("task %s:%d ==> %s:%d",
prev->comm, prev->pid, next->comm, next->pid),
TRACE_STRUCT(
TRACE_FIELD(pid_t, prev_pid, prev->pid)
TRACE_FIELD(int, prev_prio, prev->prio)
TRACE_FIELD_SPECIAL(char next_comm[TASK_COMM_LEN],
next_comm,
TPCMD(memcpy(TRACE_ENTRY->next_comm,
next->comm,
TASK_COMM_LEN)))
TRACE_FIELD(pid_t, next_pid, next->pid)
TRACE_FIELD(int, next_prio, next->prio)
),
TPRAWFMT("prev %d:%d ==> next %s:%d:%d")
);
but a lot faster.
Ingo
next prev parent reply other threads:[~2009-03-04 11:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 11:03 [PATCH] tracing: lockdep tracepoints Peter Zijlstra
2009-03-04 11:23 ` Frederic Weisbecker
2009-03-04 11:32 ` [PATCH -v2] " Peter Zijlstra
2009-03-04 11:43 ` Ingo Molnar [this message]
2009-03-04 11:58 ` Peter Zijlstra
2009-03-04 12:12 ` Frederic Weisbecker
2009-03-04 13:01 ` Peter Zijlstra
2009-03-04 13:07 ` Steven Rostedt
2009-03-04 12:02 ` Török Edwin
2009-03-04 17:57 ` [tip:tracing/ftrace] tracing: add lockdep tracepoints for lock acquire/release Peter Zijlstra
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=20090304114319.GA4916@elte.hu \
--to=mingo@elte.hu \
--cc=edwintorok@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
/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