From: Sean Christopherson <seanjc@google•com>
To: Mark Brown <broonie@kernel•org>
Cc: Paolo Bonzini <pbonzini@redhat•com>, KVM <kvm@vger•kernel.org>,
Babu Moger <babu.moger@amd•com>, Borislav Petkov <bp@alien8•de>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Xin Li <xin@zytor•com>
Subject: Re: linux-next: manual merge of the kvm tree with the origin tree
Date: Thu, 2 Oct 2025 11:39:05 -0700 [thread overview]
Message-ID: <aN7GyQU6q8fKsJ7J@google.com> (raw)
In-Reply-To: <aN6hwNUa3Kh08yog@sirena.org.uk>
On Thu, Oct 02, 2025, Mark Brown wrote:
> Hi all,
>
> Today's linux-next merge of the kvm tree got a conflict in:
>
> arch/x86/include/asm/cpufeatures.h
>
> between commit:
>
> e19c06219985f ("x86/cpufeatures: Add support for Assignable Bandwidth Monitoring Counters (ABMC)")
>
> from the origin tree and commit:
>
> 3c7cb84145336 ("x86/cpufeatures: Add a CPU feature bit for MSR immediate form instructions")
>
> from the kvm tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
> diff --cc arch/x86/include/asm/cpufeatures.h
> index b2a562217d3ff,f1a9f40622cdc..0000000000000
> --- a/arch/x86/include/asm/cpufeatures.h
> +++ b/arch/x86/include/asm/cpufeatures.h
> @@@ -496,7 -497,7 +497,8 @@@
> #define X86_FEATURE_TSA_L1_NO (21*32+12) /* AMD CPU not vulnerable to TSA-L1 */
> #define X86_FEATURE_CLEAR_CPU_BUF_VM (21*32+13) /* Clear CPU buffers using VERW before VMRUN */
> #define X86_FEATURE_IBPB_EXIT_TO_USER (21*32+14) /* Use IBPB on exit-to-userspace, see VMSCAPE bug */
> -#define X86_FEATURE_MSR_IMM (21*32+15) /* MSR immediate form instructions */
> +#define X86_FEATURE_ABMC (21*32+15) /* Assignable Bandwidth Monitoring Counters */
> ++#define X86_FEATURE_MSR_IMM (21*32+16) /* MSR immediate form instructions */
Just in case anyone else is starled by the change in bit number, these are
synthetic (or scattered) flags, i.e. the the bit number is arbitrary and not
tied to hardware.
next prev parent reply other threads:[~2025-10-02 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 16:01 linux-next: manual merge of the kvm tree with the origin tree Mark Brown
2025-10-02 18:39 ` Sean Christopherson [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-01 16:59 Mark Brown
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=aN7GyQU6q8fKsJ7J@google.com \
--to=seanjc@google$(echo .)com \
--cc=babu.moger@amd$(echo .)com \
--cc=bp@alien8$(echo .)de \
--cc=broonie@kernel$(echo .)org \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=pbonzini@redhat$(echo .)com \
--cc=xin@zytor$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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