From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Ilkka Koskinen <ilkka@os.amperecomputing.com>
Cc: Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Besar Wicaksono <bwicaksono@nvidia.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Mark Rutland <mark.rutland@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v6 1/4] perf: arm_cspmu: Split 64-bit write to 32-bit writes
Date: Wed, 16 Aug 2023 15:00:18 +0100 [thread overview]
Message-ID: <ad63e8fa-6437-872b-0bc3-ef87a5150652@arm.com> (raw)
In-Reply-To: <e04669ee-d547-dbbe-e87b-5d7efa6ee8@os.amperecomputing.com>
On 15/08/2023 21:46, Ilkka Koskinen wrote:
>
> Hi Suzuki,
>
> On Tue, 15 Aug 2023, Suzuki K Poulose wrote:
>> On 15/08/2023 07:35, Ilkka Koskinen wrote:
>>> Split the 64-bit register accesses if 64-bit access is not supported
>>> by the PMU.
>>>
>>> Signed-off-by: Ilkka Koskinen <ilkka@os.amperecomputing.com>
>>> Reviewed-by: Besar Wicaksono <bwicaksono@nvidia.com>
>>
>> Do we need a Fixes tag ?
>
> I believe, NVIDIA's PMU supports 64-bit access while Ampere's one
> doesn't and since this patchset enables support for the latter one, it
> doesn't seem like we need a Fixes tag here.
Ok, makes sense.
Suzuki
>
> Cheers, Ilkka
>
>>
>> With that:
>>
>> Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
>>
>> Suzuki
>>
>>> ---
>>> drivers/perf/arm_cspmu/arm_cspmu.c | 5 ++++-
>>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/perf/arm_cspmu/arm_cspmu.c
>>> b/drivers/perf/arm_cspmu/arm_cspmu.c
>>> index 04be94b4aa48..6387cbad7a7d 100644
>>> --- a/drivers/perf/arm_cspmu/arm_cspmu.c
>>> +++ b/drivers/perf/arm_cspmu/arm_cspmu.c
>>> @@ -715,7 +715,10 @@ static void arm_cspmu_write_counter(struct
>>> perf_event *event, u64 val)
>>> if (use_64b_counter_reg(cspmu)) {
>>> offset = counter_offset(sizeof(u64), event->hw.idx);
>>> - writeq(val, cspmu->base1 + offset);
>>> + if (cspmu->has_atomic_dword)
>>> + writeq(val, cspmu->base1 + offset);
>>> + else
>>> + lo_hi_writeq(val, cspmu->base1 + offset);
>>
>>
>>> } else {
>>> offset = counter_offset(sizeof(u32), event->hw.idx);
>>>
>>
>>
next prev parent reply other threads:[~2023-08-16 14:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 6:35 [PATCH v6 0/4] perf: arm_cspmu: ampere: Add support for Ampere SoC PMUs Ilkka Koskinen
2023-08-15 6:35 ` [PATCH v6 1/4] perf: arm_cspmu: Split 64-bit write to 32-bit writes Ilkka Koskinen
2023-08-15 10:24 ` Suzuki K Poulose
2023-08-15 20:46 ` Ilkka Koskinen
2023-08-16 14:00 ` Suzuki K Poulose [this message]
2023-08-15 6:35 ` [PATCH v6 2/4] perf: arm_cspmu: Support implementation specific filters Ilkka Koskinen
2023-08-16 14:03 ` Suzuki K Poulose
2023-08-15 6:35 ` [PATCH v6 3/4] perf: arm_cspmu: Support implementation specific validation Ilkka Koskinen
2023-08-16 14:05 ` Suzuki K Poulose
2023-08-15 6:35 ` [PATCH v6 4/4] perf: arm_cspmu: ampere_cspmu: Add support for Ampere SoC PMU Ilkka Koskinen
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=ad63e8fa-6437-872b-0bc3-ef87a5150652@arm.com \
--to=suzuki.poulose@arm.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=bwicaksono@nvidia.com \
--cc=corbet@lwn.net \
--cc=ilkka@os.amperecomputing.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robin.murphy@arm.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®