From: Jiri Olsa <jolsa@redhat.com>
To: Leo Yan <leo.yan@linaro.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Remi Bernon <rbernon@codeweavers.com>,
Nick Gasson <nick.gasson@arm.com>,
Stephane Eranian <eranian@google.com>,
Andi Kleen <ak@linux.intel.com>,
John Garry <john.garry@huawei.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/2] perf: Make tsc testing as a common testing case
Date: Tue, 20 Oct 2020 08:11:59 +0200 [thread overview]
Message-ID: <20201020061159.GB2084117@krava> (raw)
In-Reply-To: <20201019100236.23675-1-leo.yan@linaro.org>
On Mon, Oct 19, 2020 at 06:02:34PM +0800, Leo Yan wrote:
> This patch set is to move tsc testing from x86 specific to common
> testing case. Since Arnaldo found the building failure for patch set
> v4 [1], the first four patches have been merged but the last two patches
> were left out; this patch set is to resend the last two patches with
> fixed the building failure (by removing the header "arch-tests.h" from the
> testing code).
>
> These two patches have been tested on x86_64 and Arm64. Though I don't
> test them on archs MIPS, PowerPC, etc, I tried to search every header so
> ensure included headers are supported for all archs.
>
> These two patches have been rebased on the perf/core branch with its
> latest commit 744aec4df2c5 ("perf c2c: Update documentation for metrics
> reorganization").
>
> Changes from v5:
> * Found the merging confliction on latest perf/core, so rebased it.
>
> [1] https://lore.kernel.org/patchwork/cover/1305382/#1505752
>
>
> Leo Yan (2):
> perf tests tsc: Make tsc testing as a common testing
> perf tests tsc: Add checking helper is_supported()
Acked-by: Jiri Olsa <jolsa@redhat.com>
thanks,
jirka
>
> tools/perf/arch/x86/include/arch-tests.h | 1 -
> tools/perf/arch/x86/tests/Build | 1 -
> tools/perf/arch/x86/tests/arch-tests.c | 4 ----
> tools/perf/tests/Build | 1 +
> tools/perf/tests/builtin-test.c | 5 +++++
> .../{arch/x86 => }/tests/perf-time-to-tsc.c | 19 +++++++++++++++----
> tools/perf/tests/tests.h | 2 ++
> 7 files changed, 23 insertions(+), 10 deletions(-)
> rename tools/perf/{arch/x86 => }/tests/perf-time-to-tsc.c (92%)
>
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-10-20 6:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 10:02 Leo Yan
2020-10-19 10:02 ` [PATCH v6 1/2] perf tests tsc: Make tsc testing as a common testing Leo Yan
2020-10-19 10:02 ` [PATCH v6 2/2] perf tests tsc: Add checking helper is_supported() Leo Yan
2020-10-20 6:11 ` Jiri Olsa [this message]
2020-10-20 12:09 ` [PATCH v6 0/2] perf: Make tsc testing as a common testing case 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=20201020061159.GB2084117@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=john.garry@huawei.com \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nick.gasson@arm.com \
--cc=peterz@infradead.org \
--cc=rbernon@codeweavers.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®