From: James Clark <james.clark@arm.com>
To: Will Deacon <will@kernel.org>, Ian Rogers <irogers@google.com>,
Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Kan Liang <kan.liang@linux.intel.com>,
linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH 1/4] arm_pmu: Add PERF_PMU_CAP_EXTENDED_HW_TYPE capability
Date: Mon, 24 Jul 2023 14:46:35 +0100 [thread overview]
Message-ID: <5876adba-0507-6bfd-6ede-74f8e7aa55f2@arm.com> (raw)
In-Reply-To: <20230721102131.GA12457@willie-the-truck>
On 21/07/2023 11:21, Will Deacon wrote:
> On Thu, Jul 20, 2023 at 10:12:21AM -0700, Ian Rogers wrote:
>> On Tue, Jul 11, 2023 at 7:12 AM James Clark <james.clark@arm.com> wrote:
>>>
>>>
>>>
>>> On 11/07/2023 13:01, Anshuman Khandual wrote:
>>>>
>>>>
>>>> On 7/10/23 17:51, James Clark wrote:
>>>>> This capability gives us the ability to open PERF_TYPE_HARDWARE and
>>>>> PERF_TYPE_HW_CACHE events on a specific PMU for free. All the
>>>>> implementation is contained in the Perf core and tool code so no change
>>>>> to the Arm PMU driver is needed.
>>>>>
>>>>> The following basic use case now results in Perf opening the event on
>>>>> all PMUs rather than picking only one in an unpredictable way:
>>>>>
>>>>> $ perf stat -e cycles -- taskset --cpu-list 0,1 stress -c 2
>>>>>
>>>>> Performance counter stats for 'taskset --cpu-list 0,1 stress -c 2':
>>>>>
>>>>> 963279620 armv8_cortex_a57/cycles/ (99.19%)
>>>>> 752745657 armv8_cortex_a53/cycles/ (94.80%)
>>>>>
>>>>> Fixes: 55bcf6ef314a ("perf: Extend PERF_TYPE_HARDWARE and PERF_TYPE_HW_CACHE")
>>>>> Suggested-by: Ian Rogers <irogers@google.com>
>>>>> Signed-off-by: James Clark <james.clark@arm.com>
>>
>> Hi ARM Linux and ARM Linux PMU people,
>>
>> Could this patch be picked up for Linux 6.5? I don't see it in the
>> tree and it seems a shame to have to wait for it. The other patches do
>> cleanup and so waiting for 6.6 seems okay.
>
> I'm only taking fixes for 6.5 and I don't think this qualifies.
>
> If it was an oversight introduced during the recent merge window, then
> I'd be happier fixing it up, but 55bcf6ef314a was merged ages ago (v5.12?),
> so I think we can wait.
>
> I'll be queuing perf changes for 6.6 next week, so I'll look at this
> then.
>
> Cheers,
>
> Will
Hi Will,
Thanks for looking at this. I've sent a v2 with Anshuman's fixes.
James
next prev parent reply other threads:[~2023-07-24 13:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 12:21 [PATCH 0/4] " James Clark
2023-07-10 12:21 ` [PATCH 1/4] " James Clark
2023-07-10 16:04 ` Ian Rogers
2023-07-11 12:01 ` Anshuman Khandual
2023-07-11 14:12 ` James Clark
2023-07-20 17:12 ` Ian Rogers
2023-07-21 10:21 ` Will Deacon
2023-07-24 13:46 ` James Clark [this message]
2023-07-10 12:21 ` [PATCH 2/4] perf/x86: Remove unused PERF_PMU_CAP_HETEROGENEOUS_CPUS capability James Clark
2023-07-10 16:07 ` Ian Rogers
2023-07-10 12:21 ` [PATCH 3/4] arm_pmu: " James Clark
2023-07-10 16:08 ` Ian Rogers
2023-07-11 12:08 ` Anshuman Khandual
2023-07-11 14:04 ` James Clark
2023-07-10 12:21 ` [PATCH 4/4] perf: " James Clark
2023-07-10 16:09 ` Ian Rogers
2023-07-11 12:10 ` Anshuman Khandual
2023-07-11 14:15 ` James Clark
2023-07-13 7:30 ` Anshuman Khandual
2023-07-13 9:15 ` James Clark
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=5876adba-0507-6bfd-6ede-74f8e7aa55f2@arm.com \
--to=james.clark@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@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®