All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: "David S. Ahern" <daahern@cisco.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf symbols: reuse of name in dso__load when starting second pass
Date: Mon, 22 Nov 2010 10:35:30 -0200	[thread overview]
Message-ID: <20101122123530.GA9129@ghostprotocols.net> (raw)
In-Reply-To: <4CE9BE66.3060109@cisco.com>

Em Sun, Nov 21, 2010 at 05:50:46PM -0700, David S. Ahern escreveu:
> On 11/21/10 15:03, Arnaldo Carvalho de Melo wrote:
> > Em Sun, Nov 21, 2010 at 08:03:50AM -0700, David Ahern escreveu:
> >> continue statement in default case applies when a second pass is
> >> wanted as well. As it stands the code drops down to the open
> >> re-using the value in name from the previous origin attempt.
> >>
> >> Signed-off-by: David Ahern <daahern@cisco.com>
> >> ---
> >>  tools/perf/util/symbol.c |    4 ++--
> >>  1 files changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/tools/perf/util/symbol.c b/tools/perf/util/symbol.c
> >> index d30136e..861be8b 100644
> >> --- a/tools/perf/util/symbol.c
> >> +++ b/tools/perf/util/symbol.c
> >> @@ -1488,8 +1488,8 @@ int dso__load(struct dso *self, struct map *map, symbol_filter_t filter)
> >>  			if (want_symtab) {
> >>  				want_symtab = 0;
> >>  				self->origin = DSO__ORIG_BUILD_ID_CACHE;
> >> -			} else
> >> -				continue;
> >> +			}
> >> +			continue;

> > But we want to restart at DSO__ORIG_BUILD_ID_CACHE, right? If you do
> > your change we keep a existing mistake and will instead restart at
> > DSO__ORIG_BUILD_ID_CACHE + 1, please take a look to validate my
> > understanding that we need to set self->origin to
> > DSO__ORIG_BUILD_ID_CACHE - 1.
> 
> Correct. In working on the rootfs change I noticed that the default case
> falls through to the open using the 'name' value set from the previous
> origin so it is tried twice. This patch fixes that bug.
> 
> I also noted that the BUILD_ID_CACHE was skipped, but I was not sure if
> that was desired or not. If it is then correcting the proper 'next
> origin' is another trivial bug fix.
> 
> Some projects like single focused bug fixes for bisecting. I am fine
> with combining if that is wanted.

Agreed, two is better, I'll apply yours and add a followup fixing this
other issue, thanks.

- Arnaldo

      reply	other threads:[~2010-11-22 12:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-21 15:03 [PATCH] perf symbols: reuse of name in dso__load when starting second pass David Ahern
2010-11-21 22:03 ` Arnaldo Carvalho de Melo
2010-11-22  0:50   ` David S. Ahern
2010-11-22 12:35     ` Arnaldo Carvalho de Melo [this message]

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=20101122123530.GA9129@ghostprotocols.net \
    --to=acme@ghostprotocols.net \
    --cc=daahern@cisco.com \
    --cc=linux-perf-users@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.