From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: mark.rutland@arm.com, catalin.marinas@arm.com,
broonie@kernel.org, will@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] arm64/cpufeature: Add get_arm64_ftr_reg_nowarn()
Date: Tue, 26 May 2020 19:33:29 +0530 [thread overview]
Message-ID: <6886ec2e-c2e4-c2d2-faaa-b46ef69cc226@arm.com> (raw)
In-Reply-To: <0726a5b9-fff6-a15c-e705-db7abd4b1abd@arm.com>
On 05/26/2020 07:34 PM, Suzuki K Poulose wrote:
> On 05/26/2020 02:39 PM, Anshuman Khandual wrote:
>> There is no way to proceed when requested register could not be searched in
>> arm64_ftr_reg[]. Requesting for a non present register would be an error as
>> well. Hence lets just WARN_ON() when search fails in get_arm64_ftr_reg()
>> rather than checking for return value and doing a BUG_ON() instead in some
>> individual callers. But there are also caller instances that dont error out
>> when register search fails. Add a new helper get_arm64_ftr_reg_nowarn() for
>> such cases.
>>
>> Cc: Catalin Marinas <catalin.marinas@arm.com>
>> Cc: Will Deacon <will@kernel.org>
>> Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
>> Cc: Mark Brown <broonie@kernel.org>
>> Cc: linux-arm-kernel@lists.infradead.org
>> Cc: linux-kernel@vger.kernel.org
>> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
>> ---
>> Changes in V2:
>>
>> - Added get_arm64_ftr_reg_nowarn() per Will
>> - read_sanitised_ftr_reg() returns 0 when register search fails per Catalin
>>
>> Changes in V1: (https://patchwork.kernel.org/patch/11559083/)
>>
>> arch/arm64/kernel/cpufeature.c | 42 +++++++++++++++++++++++-----------
>> 1 file changed, 29 insertions(+), 13 deletions(-)
>>
>> diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c
>> index bc5048f152c1..f4555b9d145c 100644
>> --- a/arch/arm64/kernel/cpufeature.c
>> +++ b/arch/arm64/kernel/cpufeature.c
>> @@ -548,16 +548,16 @@ static int search_cmp_ftr_reg(const void *id, const void *regp)
>> }
>>
>
> ...
>
>> static u64 arm64_ftr_set_value(const struct arm64_ftr_bits *ftrp, s64 reg,
>> s64 ftr_val)
>> {
>> @@ -632,8 +654,6 @@ static void __init init_cpu_ftr_reg(u32 sys_reg, u64 new)
>> const struct arm64_ftr_bits *ftrp;
>> struct arm64_ftr_reg *reg = get_arm64_ftr_reg(sys_reg);
>> - BUG_ON(!reg);
>> -
>> for (ftrp = reg->ftr_bits; ftrp->width; ftrp++) {
>> u64 ftr_mask = arm64_ftr_mask(ftrp);
>> s64 ftr_new = arm64_ftr_value(ftrp, new);
>> @@ -762,7 +782,6 @@ static int check_update_ftr_reg(u32 sys_id, int cpu, u64 val, u64 boot)
>> {
>> struct arm64_ftr_reg *regp = get_arm64_ftr_reg(sys_id);
>> - BUG_ON(!regp);
>> update_cpu_ftr_reg(regp, val);
>> if ((boot & regp->strict_mask) == (val & regp->strict_mask))
>> return 0;
>> @@ -776,9 +795,6 @@ static void relax_cpu_ftr_reg(u32 sys_id, int field)
>> const struct arm64_ftr_bits *ftrp;
>> struct arm64_ftr_reg *regp = get_arm64_ftr_reg(sys_id);
>> - if (WARN_ON(!regp))
>> - return;
>> -
>
> You need to return here, on !regp. Rest looks fine to me.
Catalin had suggested and agreed on for this change in behavior here.
If the register is not found, there is already some problem.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-05-26 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 13:39 [PATCH V2] arm64/cpufeature: Add get_arm64_ftr_reg_nowarn() Anshuman Khandual
2020-05-26 14:04 ` Suzuki K Poulose
2020-05-26 14:03 ` Anshuman Khandual [this message]
2020-05-26 15:01 ` Catalin Marinas
2020-05-26 19:46 ` Will Deacon
2020-05-27 2:26 ` Anshuman Khandual
2020-05-27 7:53 ` Will Deacon
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=6886ec2e-c2e4-c2d2-faaa-b46ef69cc226@arm.com \
--to=anshuman.khandual@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=suzuki.poulose@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