public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
Cc: Marcin Slusarz <marcin.slusarz@gmail.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf lock: fix sorting by wait_min
Date: Mon, 14 Mar 2011 16:23:03 -0300	[thread overview]
Message-ID: <20110314192303.GB9388@ghostprotocols.net> (raw)
In-Reply-To: <20110314165458.GA2693@joi.lan>

Em Mon, Mar 14, 2011 at 05:54:58PM +0100, Marcin Slusarz escreveu:
> On Tue, Feb 22, 2011 at 06:47:15PM +0100, Marcin Slusarz wrote:
> > if lock was uncontended, wait_time_min == ULLONG_MAX, so we need to handle
> > this case differently to show high wait times first
> > 
> > Signed-off-by: Marcin Slusarz <marcin.slusarz@gmail.com>
> > ---
> >  tools/perf/builtin-lock.c |   13 ++++++++++++-
> >  1 files changed, 12 insertions(+), 1 deletions(-)
> > 
> > diff --git a/tools/perf/builtin-lock.c b/tools/perf/builtin-lock.c
> > index 0305a40..812ad26 100644
> > --- a/tools/perf/builtin-lock.c
> > +++ b/tools/perf/builtin-lock.c
> > @@ -202,9 +202,20 @@ static struct thread_stat *thread_stat_findnew_first(u32 tid)
> >  SINGLE_KEY(nr_acquired)
> >  SINGLE_KEY(nr_contended)
> >  SINGLE_KEY(wait_time_total)
> > -SINGLE_KEY(wait_time_min)
> >  SINGLE_KEY(wait_time_max)
> >  
> > +static int lock_stat_key_wait_time_min(struct lock_stat *one,
> > +					struct lock_stat *two)
> > +{
> > +	u64 s1 = one->wait_time_min;
> > +	u64 s2 = two->wait_time_min;
> > +	if (s1 == ULLONG_MAX)
> > +		s1 = 0;
> > +	if (s2 == ULLONG_MAX)
> > +		s2 = 0;
> > +	return s1 > s2;
> > +}
> > +
> >  struct lock_key {
> >  	/*
> >  	 * name: the value for specify by user
> > -- 
> 
> Anything wrong with this patch?
> I can't find it in linux-next.

Hitoshi-san, can I have your acked-by for this one?

Thanks,

- Arnaldo

  reply	other threads:[~2011-03-14 19:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22 17:47 [PATCH] perf lock: fix sorting by wait_min Marcin Slusarz
2011-03-14 16:54 ` Marcin Slusarz
2011-03-14 19:23   ` Arnaldo Carvalho de Melo [this message]
2011-03-15  8:08     ` Hitoshi Mitake
2011-03-17 11:04 ` [tip:perf/urgent] perf lock: Fix " tip-bot for Marcin Slusarz

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=20110314192303.GB9388@ghostprotocols.net \
    --to=acme@infradead.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=mingo@elte.hu \
    --cc=mitake@dcl.info.waseda.ac.jp \
    --cc=paulus@samba.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