From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the perf tree
Date: Wed, 6 Dec 2023 09:33:45 -0300 [thread overview]
Message-ID: <ZXBqKaGRF8y/2K9b@kernel.org> (raw)
In-Reply-To: <20231206091433.68f59ba1@canb.auug.org.au>
Em Wed, Dec 06, 2023 at 09:14:33AM +1100, Stephen Rothwell escreveu:
> Commit
> 08b953508560 ("perf evsel: Fallback to "task-clock" when not system wide")
> is missing a Signed-off-by from its author.
Thanks for the report, fixed, the issue was that Ian's S-o-B was after a
--- line and thus git-am chopped it up :-\
===============================================================================
When the cycles event isn't available evsel will fallback to the
cpu-clock software event. task-clock is similar to cpu-clock but only
runs when the process is running. Falling back to cpu-clock when not
system wide leads to confusion, by falling back to task-clock it is
hoped the confusion is less.
Pass the target to determine if task-clock is more appropriate. Update
a nearby comment and debug string for the change.
---
v2. Use target__has_cpu as suggested by Namhyung.
https://lpc.events/event/17/contributions/1556/
Signed-off-by: Ian Rogers <irogers@google.com>
---
tools/perf/builtin-record.c | 2 +-
tools/perf/builtin-stat.c | 2 +-
tools/perf/builtin-top.c | 2 +-
tools/perf/util/evsel.c | 18 ++++++++++--------
tools/perf/util/evsel.h | 3 ++-
5 files changed, 15 insertions(+), 12 deletions(-
--
===============================================================================
I'll check my pre-commit hooks to see why this didn't get flagged...
- Arnaldo
next prev parent reply other threads:[~2023-12-06 12:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 22:14 linux-next: Signed-off-by missing for commit in the perf tree Stephen Rothwell
2023-12-06 12:33 ` Arnaldo Carvalho de Melo [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-04 22:24 Stephen Rothwell
2025-12-04 22:52 ` Ian Rogers
2025-12-04 23:41 ` Namhyung Kim
2024-12-15 21:27 Stephen Rothwell
2024-12-17 0:33 ` Arnaldo Carvalho de Melo
2024-12-17 0:39 ` Stephen Rothwell
2024-12-17 0:55 ` Arnaldo Carvalho de Melo
2023-09-14 21:26 Stephen Rothwell
2023-09-15 2:50 ` Namhyung Kim
2022-12-13 21:34 Stephen Rothwell
2022-12-13 21:36 ` Arnaldo Carvalho de Melo
2022-12-13 21:40 ` Ian Rogers
2022-10-30 20:45 Stephen Rothwell
2022-10-31 14:04 ` Arnaldo Carvalho de Melo
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=ZXBqKaGRF8y/2K9b@kernel.org \
--to=acme@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sfr@canb.auug.org.au \
/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.