From: guohanjun@huawei•com (Hanjun Guo)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 00/14] arm_pmu: ACPI support
Date: Tue, 11 Apr 2017 17:32:09 +0800 [thread overview]
Message-ID: <58ECA299.6060704@huawei.com> (raw)
In-Reply-To: <CAFpQJXVe_=42R+0Ch-tLwCcvhX3xJa20mhgYCWWNty-sn1Gp+g@mail.gmail.com>
On 2017/3/21 2:11, Ganapatrao Kulkarni wrote:
> Hi Hanjun,
>
> On Thu, Mar 16, 2017 at 6:30 PM, Hanjun Guo <guohanjun@huawei•com> wrote:
>> On 2017/3/10 19:04, Mark Rutland wrote:
>>> Hi,
>>>
>>> This series implements ACPI support in the ARM PMU code. It borrows some code
>>> from Jeremy's series [1], but takes a different approach to probing and
>>> association, using the usual hotplug state machine, minimising external changes
>>> required, and simplifying the relationship with the common arm_pmu code.
>>>
>>> The first few patches are preparatory cleanup/refactoring, with the latter half
>>> of the series being specific to ACPI support.
>>>
>>> The series is based on my IRQ rework patches [2]. I've pushed the whole series
>>> out to the arm/perf/acpi branch [3] of my kernel.org repo.
>>>
>>> Due to the innards of the hotplug callback framework, it's not entirely
>>> safe to register a PMU in a hotplug callback. Due to this, we can only
>>> associated hotplugged CPUs with a PMU if a matching CPU was around at
>>> probe time. A similar restriction already applies to DT systems. We may
>>> be able to relax this with some future work.
>>>
>>> I've given this some testing on a Juno platform (using SPIs). To see that IRQs
>>> are correctly associated, I've tested with the following:
>>>
>>> $ taskset -c ${SOME_CPU_HERE} perf record \
>>> -e armv8_pmuv3_0/cpu_cycles/ \
>>> -e armv8_pmuv3_1/cpu_cycles/ \
>>> cat /proc/interrupts
>>>
>>> I've also booted with nr_cpus temporarily capped (passing maxcpus=) to test the
>>> association logic. This has also been tested in a VM using PPIs; I do not have
>>> access to a host machine which itself uses PPIs.
>> Booted OK and 'perf list' got on Hisilicon D03:
>>
>> d03-09:~ # perf list
>>
>> List of pre-defined events (to be used in -e):
>>
>> branch-misses [Hardware event]
>> bus-cycles [Hardware event]
>> cache-misses [Hardware event]
>> cache-references [Hardware event]
>> cpu-cycles OR cycles [Hardware event]
>> instructions [Hardware event]
>>
>> alignment-faults [Software event]
>> context-switches OR cs [Software event]
>> cpu-clock [Software event]
>> cpu-migrations OR migrations [Software event]
>> dummy [Software event]
>> emulation-faults [Software event]
>> major-faults [Software event]
>> minor-faults [Software event]
>> page-faults OR faults [Software event]
>> task-clock [Software event]
>>
>> L1-dcache-load-misses [Hardware cache event]
>> L1-dcache-loads [Hardware cache event]
>> L1-dcache-store-misses [Hardware cache event]
>> L1-dcache-stores [Hardware cache event]
>> L1-icache-load-misses [Hardware cache event]
>> L1-icache-loads [Hardware cache event]
>> branch-load-misses [Hardware cache event]
>> branch-loads [Hardware cache event]
>> dTLB-load-misses [Hardware cache event]
>> iTLB-load-misses [Hardware cache event]
>>
>> armv8_pmuv3_0/br_mis_pred/ [Kernel PMU event]
>> armv8_pmuv3_0/br_pred/ [Kernel PMU event]
>> armv8_pmuv3_0/bus_access/ [Kernel PMU event]
>> armv8_pmuv3_0/bus_cycles/ [Kernel PMU event]
>> armv8_pmuv3_0/cid_write_retired/ [Kernel PMU event]
>> armv8_pmuv3_0/cpu_cycles/ [Kernel PMU event]
>> armv8_pmuv3_0/exc_return/ [Kernel PMU event]
>> armv8_pmuv3_0/exc_taken/ [Kernel PMU event]
>> armv8_pmuv3_0/inst_retired/ [Kernel PMU event]
>> armv8_pmuv3_0/inst_spec/ [Kernel PMU event]
>> armv8_pmuv3_0/l1d_cache/ [Kernel PMU event]
>> armv8_pmuv3_0/l1d_cache_refill/ [Kernel PMU event]
>> armv8_pmuv3_0/l1d_cache_wb/ [Kernel PMU event]
>> armv8_pmuv3_0/l1d_tlb_refill/ [Kernel PMU event]
>> armv8_pmuv3_0/l1i_cache/ [Kernel PMU event]
>> armv8_pmuv3_0/l1i_cache_refill/ [Kernel PMU event]
>> armv8_pmuv3_0/l1i_tlb_refill/ [Kernel PMU event]
>> armv8_pmuv3_0/l2d_cache/ [Kernel PMU event]
>> armv8_pmuv3_0/l2d_cache_refill/ [Kernel PMU event]
>> armv8_pmuv3_0/l2d_cache_wb/ [Kernel PMU event]
>> armv8_pmuv3_0/mem_access/ [Kernel PMU event]
>> armv8_pmuv3_0/memory_error/ [Kernel PMU event]
>> armv8_pmuv3_0/sw_incr/ [Kernel PMU event]
>> armv8_pmuv3_0/ttbr_write_retired/ [Kernel PMU event]
>>
>> rNNN [Raw hardware event descriptor]
>> cpu/t1=v1[,t2=v2,t3 ...]/modifier [Raw hardware event descriptor]
>> (see 'man perf-list' on how to encode it)
>>
>> mem:<addr>[/len][:access] [Hardware breakpoint]
>>
>>
>> Try some basic perf event and it works, anything else I can try in specific?
> you can try perf fuzzer
Sorry, just back from my paternity leave, I will try Mark's v2 (or v3 if there is a
updated one) :)
Thanks
Hanjun
next prev parent reply other threads:[~2017-04-11 9:32 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 11:04 [PATCH 00/14] arm_pmu: ACPI support Mark Rutland
2017-03-10 11:04 ` [PATCH 01/14] drivers/perf: arm_pmu: remove pointless PMU disabling Mark Rutland
2017-03-10 11:04 ` [PATCH 02/14] drivers/perf: arm_pmu: define armpmu_init_fn Mark Rutland
2017-03-10 11:04 ` [PATCH 03/14] drivers/perf: arm_pmu: fold init into alloc Mark Rutland
2017-03-10 11:04 ` [PATCH 04/14] drivers/perf: arm_pmu: factor out pmu registration Mark Rutland
2017-03-10 11:04 ` [PATCH 05/14] drivers/perf: arm_pmu: simplify cpu_pmu_request_irqs() Mark Rutland
2017-03-10 11:04 ` [PATCH 06/14] drivers/perf: arm_pmu: handle no platform_device Mark Rutland
2017-03-10 11:04 ` [PATCH 07/14] drivers/perf: arm_pmu: rename irq request/free functions Mark Rutland
2017-03-10 11:04 ` [PATCH 08/14] drivers/perf: arm_pmu: split cpu-local irq request/free Mark Rutland
2017-03-10 11:04 ` [PATCH 09/14] drivers/perf: arm_pmu: move irq request/free into probe Mark Rutland
2017-03-10 11:04 ` [PATCH 10/14] drivers/perf: arm_pmu: split out platform device probe logic Mark Rutland
2017-03-10 11:04 ` [PATCH 11/14] arm64: add function to get a cpu's MADT GICC table Mark Rutland
2017-03-23 18:33 ` Lorenzo Pieralisi
2017-03-10 11:04 ` [PATCH 12/14] arm64: kill acpi_set_mailbox_entry() Mark Rutland
2017-03-21 18:00 ` Lorenzo Pieralisi
2017-03-21 18:15 ` Mark Rutland
2017-03-21 18:37 ` Lorenzo Pieralisi
2017-03-21 18:53 ` Mark Rutland
2017-03-22 11:38 ` Mark Rutland
2017-03-10 11:04 ` [PATCH 13/14] drivers/perf: arm_pmu: add ACPI framework Mark Rutland
2017-03-10 11:04 ` [PATCH 14/14] arm64: pmuv3: use arm_pmu " Mark Rutland
2017-03-14 6:00 ` Ganapatrao Kulkarni
2017-03-14 10:51 ` Mark Rutland
2017-03-14 12:12 ` Jayachandran C.
2017-03-17 10:24 ` Ganapatrao Kulkarni
2017-04-12 2:40 ` Hanjun Guo
2017-03-10 22:14 ` [PATCH 00/14] arm_pmu: ACPI support Jeremy Linton
2017-03-14 11:49 ` Mark Rutland
2017-03-14 18:47 ` Mark Rutland
2017-03-14 22:06 ` Agustin Vega-Frias
2017-03-15 2:49 ` Hanjun Guo
2017-03-22 12:19 ` Lorenzo Pieralisi
2017-03-22 14:06 ` Agustin Vega-Frias
2017-03-22 23:23 ` Hanjun Guo
2017-03-15 15:34 ` Mark Rutland
2017-03-16 13:00 ` Hanjun Guo
2017-03-20 18:11 ` Ganapatrao Kulkarni
2017-03-22 9:16 ` Ganapatrao Kulkarni
2017-03-22 15:59 ` Mark Rutland
2017-04-03 10:41 ` Ganapatrao Kulkarni
2017-04-03 11:12 ` Mark Rutland
2017-04-11 9:32 ` Hanjun Guo [this message]
2017-03-24 21:36 ` Jeremy Linton
2017-03-28 11:31 ` Mark Rutland
2017-03-28 14:41 ` Jeremy Linton
-- strict thread matches above, loose matches on Subject: below --
2017-03-17 2:11 Itaru Kitayama
2017-03-23 10:54 ` Mark Rutland
2017-03-25 3:18 ` Itaru Kitayama
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=58ECA299.6060704@huawei.com \
--to=guohanjun@huawei$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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