From: sashiko-bot@kernel.org
To: "Zack Rusin" <zack.rusin@broadcom.com>
Cc: virtualization@lists.linux.dev,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH v4 3/3] x86/cpufeatures: Remove unused VMware hypercall feature bits
Date: Wed, 18 Nov 2026 06:43:45 +0000 [thread overview]
Message-ID: <sashiko-outbox-220268@kernel.org> (raw)
In-Reply-To: <bcc9b471c176d5b162e6935b2c0c7f96c65ac8a6.1794206170.git.zack.rusin@broadcom.com>
> The static-call conversion removed the alternative instruction templates
> that used X86_FEATURE_VMCALL and X86_FEATURE_VMW_VMMCALL. Their remaining
> users only force the bits during VMware setup; no code tests either bit.
>
> Remove the forced capabilities and mark both positions free in the kernel
> header. Neither feature has a cpuinfo name, so this changes no
> userspace-visible flag.
>
> Signed-off-by: Zack Rusin <zack.rusin@broadcom.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1794206170.git.zack.rusin@broadcom.com?part=3
prev parent reply other threads:[~2026-11-18 6:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 6:40 [PATCH v4 0/3] x86/vmware: Clean up the hypercall code Zack Rusin
2026-11-18 6:40 ` [PATCH v4 1/3] x86/vmware: Move high-bandwidth hypercalls out of line Zack Rusin
2026-11-18 6:40 ` [PATCH v4 2/3] x86/vmware: Route low-bandwidth hypercalls through a static call Zack Rusin
2026-11-18 6:40 ` [PATCH v4 3/3] x86/cpufeatures: Remove unused VMware hypercall feature bits Zack Rusin
2026-11-18 6:43 ` sashiko-bot [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=sashiko-outbox-220268@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=eperezma@redhat.com \
--cc=mst@redhat.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=virtualization@lists.linux.dev \
--cc=zack.rusin@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.