From: Shreenidhi Shedi <yesshedi@gmail.com>
To: "Srivatsa S. Bhat" <srivatsa@csail.mit.edu>,
Borislav Petkov <bp@alien8.de>
Cc: amakhalov@vmware.com, tglx@linutronix.de, mingo@redhat.com,
dave.hansen@linux.intel.com, hpa@zytor.com,
virtualization@lists.linux-foundation.org, pv-drivers@vmware.com,
x86@kernel.org, linux-kernel@vger.kernel.org,
Shreenidhi Shedi <sshedi@vmware.com>
Subject: Re: [PATCH] x86/vmware: use unsigned integer for shifting
Date: Fri, 20 May 2022 17:12:57 +0530 [thread overview]
Message-ID: <53809b87-9b39-0aa9-dbc9-d5b40b3b46a6@gmail.com> (raw)
In-Reply-To: <c3219731-5f7e-80ea-b193-f8c93d7c1bdc@csail.mit.edu>
On 20/05/22 4:59 pm, Srivatsa S. Bhat wrote:
> Hi Shreenidhi,
>
> Thank you for the patch!
>
> On 5/20/22 2:26 AM, Borislav Petkov wrote:
>> On Fri, May 20, 2022 at 12:58:57PM +0530, Shreenidhi Shedi wrote:
>>> Shifting signed 32-bit value by 31 bits is implementation-defined
>>> behaviour. Using unsigned is better option for this.
>>>
>
> Can you also add a "Fixes:" tag with the commit that introduced the
> issue? I believe it is 4cca6ea04d31 ("x86/apic: Allow x2apic without
> IR on VMware platform").
>
>>> Signed-off-by: Shreenidhi Shedi <sshedi@vmware.com>
>>> ---
>>> arch/x86/kernel/cpu/vmware.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/arch/x86/kernel/cpu/vmware.c b/arch/x86/kernel/cpu/vmware.c
>>> index c04b933f48d3..b28f789d3c56 100644
>>> --- a/arch/x86/kernel/cpu/vmware.c
>>> +++ b/arch/x86/kernel/cpu/vmware.c
>>> @@ -476,7 +476,7 @@ static bool __init vmware_legacy_x2apic_available(void)
>>> {
>>> uint32_t eax, ebx, ecx, edx;
>>> VMWARE_CMD(GETVCPU_INFO, eax, ebx, ecx, edx);
>>> - return (eax & (1 << VMWARE_CMD_VCPU_RESERVED)) == 0 &&
>>> + return (eax & (1U << VMWARE_CMD_VCPU_RESERVED)) == 0 &&
>>> (eax & (1 << VMWARE_CMD_LEGACY_X2APIC)) != 0;
>>
>> Or you can use the BIT() macro and simplify this expression even more:
>>
>> return !(eax & BIT(VMWARE_CMD_VCPU_RESERVED)) &&
>> (eax & BIT(VMWARE_CMD_LEGACY_X2APIC));
>>
>>
>
> That's better indeed.
>
> Regards,
> Srivatsa
Thanks for the quick reviews Boris and Srivatsa. I will make the changes and push the another patch soon.
--
Shedi
prev parent reply other threads:[~2022-05-20 11:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 7:28 Shreenidhi Shedi
2022-05-20 9:26 ` Borislav Petkov
2022-05-20 11:29 ` Srivatsa S. Bhat
2022-05-20 11:42 ` Shreenidhi Shedi [this message]
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=53809b87-9b39-0aa9-dbc9-d5b40b3b46a6@gmail.com \
--to=yesshedi@gmail.com \
--cc=amakhalov@vmware.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pv-drivers@vmware.com \
--cc=srivatsa@csail.mit.edu \
--cc=sshedi@vmware.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@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®