From: Sudeep Holla <sudeep.holla@arm.com>
To: Michael Kelley <mikelley@microsoft.com>
Cc: mark.rutland@arm.com, lorenzo.pieralisi@arm.com,
steven.price@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH 1/1] firmware: smccc: Fix check for ARCH_SOC_ID not implemented
Date: Mon, 22 Nov 2021 08:35:03 +0000 [thread overview]
Message-ID: <20211122083503.umkqv2t75osypsbx@bogus> (raw)
In-Reply-To: <1637365141-16823-1-git-send-email-mikelley@microsoft.com>
On Fri, Nov 19, 2021 at 03:39:01PM -0800, Michael Kelley wrote:
> The ARCH_FEATURES function ID is a 32-bit SMC call, which returns
> a 32-bit result per the SMCCC spec. Current code is doing a 64-bit
> comparison against -1 (SMCCC_RET_NOT_SUPPORTED) to detect that the
> feature is unimplemented. That check doesn't work in a Hyper-V VM,
> where the upper 32-bits are zero as allowed by the spec.
>
> Cast the result as an 'int' so the comparison works. The change also
> makes the code consistent with other similar checks in this file.
>
> Fixes: 821b67fa4639 ("firmware: smccc: Add ARCH_SOC_ID support")
Good catch.
Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
Can you please re-post with my review tag keeping arm@kernel.org and
soc@kernel.org ? I don't have any other fixes at the moment, we can
ask SoC maintainers to fix this up directly.
--
Regards,
Sudeep
_______________________________________________
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:[~2021-11-22 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 23:39 [PATCH 1/1] firmware: smccc: Fix check for ARCH_SOC_ID not implemented Michael Kelley
2021-11-22 8:35 ` Sudeep Holla [this message]
2021-11-22 10:56 ` Arnd Bergmann
2021-11-22 11:52 ` Sudeep Holla
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=20211122083503.umkqv2t75osypsbx@bogus \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=mikelley@microsoft.com \
--cc=steven.price@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