From: "tip-bot2 for Shreenidhi Shedi" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Shreenidhi Shedi <sshedi@vmware.com>,
Borislav Petkov <bp@suse.de>,
"Srivatsa S. Bhat (VMware)" <srivatsa@csail.mit.edu>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/vmware] x86/vmware: Use BIT() macro for shifting
Date: Wed, 22 Jun 2022 09:42:36 -0000 [thread overview]
Message-ID: <165589095635.4207.5855422927608587338.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20220601101820.535031-1-sshedi@vmware.com>
The following commit has been merged into the x86/vmware branch of tip:
Commit-ID: 4745ca43104b422354f06dc814d3f13661f217af
Gitweb: https://git.kernel.org/tip/4745ca43104b422354f06dc814d3f13661f217af
Author: Shreenidhi Shedi <sshedi@vmware.com>
AuthorDate: Wed, 01 Jun 2022 15:48:20 +05:30
Committer: Borislav Petkov <bp@suse.de>
CommitterDate: Wed, 22 Jun 2022 11:23:14 +02:00
x86/vmware: Use BIT() macro for shifting
VMWARE_CMD_VCPU_RESERVED is bit 31 and that would mean undefined
behavior when shifting an int but the kernel is built with
-fno-strict-overflow which will wrap around using two's complement.
Use the BIT() macro to improve readability and avoid any potential
overflow confusion because it uses an unsigned long.
[ bp: Clarify commit message. ]
Signed-off-by: Shreenidhi Shedi <sshedi@vmware.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Srivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu>
Link: https://lore.kernel.org/r/20220601101820.535031-1-sshedi@vmware.com
---
arch/x86/kernel/cpu/vmware.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/cpu/vmware.c b/arch/x86/kernel/cpu/vmware.c
index c04b933..02039ec 100644
--- a/arch/x86/kernel/cpu/vmware.c
+++ b/arch/x86/kernel/cpu/vmware.c
@@ -476,8 +476,8 @@ 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 &&
- (eax & (1 << VMWARE_CMD_LEGACY_X2APIC)) != 0;
+ return !(eax & BIT(VMWARE_CMD_VCPU_RESERVED)) &&
+ (eax & BIT(VMWARE_CMD_LEGACY_X2APIC));
}
#ifdef CONFIG_AMD_MEM_ENCRYPT
prev parent reply other threads:[~2022-06-22 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 10:18 [PATCH v4] x86/vmware: use " Shreenidhi Shedi
2022-06-02 13:01 ` Srivatsa S. Bhat
2022-06-22 9:42 ` tip-bot2 for 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=165589095635.4207.5855422927608587338.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=srivatsa@csail.mit.edu \
--cc=sshedi@vmware.com \
--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®