From: Zhangshaokun <zhangshaokun@hisilicon.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: <will.deacon@arm.com>, <jonathan.cameron@huawei.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linuxarm@huawei.com>, Anurup M <anurup.m@huawei.com>
Subject: Re: [PATCH v5 3/6] perf: hisi: Add support for HiSilicon SoC L3C PMU driver
Date: Wed, 18 Oct 2017 22:08:15 +0800 [thread overview]
Message-ID: <2cf90805-e176-fe6f-2c37-59ce71c51781@hisilicon.com> (raw)
In-Reply-To: <20171018135530.qo54qe36zplp4etp@lakrids.cambridge.arm.com>
Hi Mark,
Thanks for your further explanation.
On 2017/10/18 21:55, Mark Rutland wrote:
> On Wed, Oct 18, 2017 at 09:33:30PM +0800, Zhangshaokun wrote:
>> On 2017/10/17 23:16, Mark Rutland wrote:
>>> On Tue, Aug 22, 2017 at 04:07:54PM +0800, Shaokun Zhang wrote:
>>>> +static int hisi_l3c_pmu_init_data(struct platform_device *pdev,
>>>> + struct hisi_pmu *l3c_pmu)
>>>> +{
>>>> + unsigned long long id;
>>>> + struct resource *res;
>>>> + acpi_status status;
>>>> + int cpu;
>>>> +
>>>> + status = acpi_evaluate_integer(ACPI_HANDLE(&pdev->dev),
>>>> + "_UID", NULL, &id);
>>>> + if (ACPI_FAILURE(status))
>>>> + return -EINVAL;
>>>> +
>>>> + l3c_pmu->id = id;
>>>> +
>>>> + /*
>>>> + * Use the SCCL_ID and CCL_ID to identify the L3C PMU, while
>>>> + * SCCL_ID is in MPIDR[aff2] and CCL_ID is in MPIDR[aff1].
>>>> + */
>>>> + if (device_property_read_u32(&pdev->dev, "hisilicon,scl-id",
>>>> + &l3c_pmu->sccl_id)) {
>>>> + dev_err(&pdev->dev, "Can not read l3c sccl-id!\n");
>>>> + return -EINVAL;
>>>> + }
>>>> +
>>>> + if (device_property_read_u32(&pdev->dev, "hisilicon,ccl-id",
>>>> + &l3c_pmu->ccl_id)) {
>>>> + dev_err(&pdev->dev, "Can not read l3c ccl-id!\n");
>>>> + return -EINVAL;
>>>> + }
>>>> +
>>>> + /* Initialise the associated cpumask of the PMU */
>>>> + for_each_present_cpu(cpu)
>>>> + smp_call_function_single(cpu, hisi_l3c_pmu_set_cpumask_by_ccl,
>>>> + (void *)l3c_pmu, 1);
>
>>> Rather than a proble-time smp_call_function_single(), can you follow the
>>> qcom l2's approach of associating CPUs with a PMU instance in the
>>> notifier? That will work even if CPUs are brought online very late.
>>
>> A good guidance, but HHA and DDRC PMUs are different from L3C PMU, the former
>> share the same SCCL and the latter share the same SCCL and CCL. I will
>> try to deal with this difference in online notifier.
>
> FWIW, I think it makes sense for each PMU to have its own notifier
> (perhaps with some shared code that each calls to do the migration).
>
> I just want to avoid the smp_call_function_single() at probe time, as
> that doesn't work in some cases.
>
Got it, i shall update the hisi_pmu::associated_cpus only in online
and offline notifiers.
Thanks,
Shaokun
> Thanks,
> Mark.
>
> .
>
next prev parent reply other threads:[~2017-10-18 14:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 8:07 [PATCH v5 0/6] Add HiSilicon SoC uncore Performance Monitoring Unit driver Shaokun Zhang
2017-08-22 8:07 ` [PATCH v5 1/6] Documentation: perf: hisi: Documentation for HiSilicon SoC PMU driver Shaokun Zhang
2017-08-22 8:07 ` [PATCH v5 2/6] perf: hisi: Add support for HiSilicon SoC uncore " Shaokun Zhang
2017-10-17 15:06 ` Mark Rutland
2017-10-18 13:19 ` Zhangshaokun
2017-08-22 8:07 ` [PATCH v5 3/6] perf: hisi: Add support for HiSilicon SoC L3C " Shaokun Zhang
2017-10-17 15:16 ` Mark Rutland
2017-10-18 13:33 ` Zhangshaokun
2017-10-18 13:55 ` Mark Rutland
2017-10-18 14:08 ` Zhangshaokun [this message]
2017-08-22 8:07 ` [PATCH v5 4/6] perf: hisi: Add support for HiSilicon SoC HHA " Shaokun Zhang
2017-10-17 15:18 ` Mark Rutland
2017-10-18 13:35 ` Zhangshaokun
2017-08-22 8:07 ` [PATCH v5 5/6] perf: hisi: Add support for HiSilicon SoC DDRC " Shaokun Zhang
2017-10-17 15:21 ` Mark Rutland
2017-10-18 13:37 ` Zhangshaokun
2017-08-22 8:07 ` [PATCH v5 6/6] arm64: MAINTAINERS: hisi: Add HiSilicon SoC PMU support Shaokun Zhang
2017-08-29 12:28 ` [PATCH v5 0/6] Add HiSilicon SoC uncore Performance Monitoring Unit driver Zhangshaokun
2017-09-21 10:40 ` Zhangshaokun
2017-10-09 8:17 ` Zhangshaokun
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=2cf90805-e176-fe6f-2c37-59ce71c51781@hisilicon.com \
--to=zhangshaokun@hisilicon.com \
--cc=anurup.m@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=will.deacon@arm.com \
/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®