From: Maxim Levitsky <mlevitsk@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: SVM: Fix a misplaced paranthesis in APICV inhibit mask generation
Date: Sat, 11 Jun 2022 16:44:06 +0300 [thread overview]
Message-ID: <1d71f8acb62120aed87238051ef0f22b1ac58470.camel@redhat.com> (raw)
In-Reply-To: <20220610191813.371682-1-seanjc@google.com>
On Fri, 2022-06-10 at 19:18 +0000, Sean Christopherson wrote:
> Relocate a ")" to its proper place at the end of a BIT usage, the intent
> is most definitely not to have a feedback loop of BITs in the mask.
>
> arch/x86/kvm/svm/avic.c: In function ‘avic_check_apicv_inhibit_reasons’:
> include/vdso/bits.h:7:40: error: left shift count >= width of type [-Werror=shift-count-overflow]
> 7 | #define BIT(nr) (UL(1) << (nr))
> | ^~
> arch/x86/kvm/svm/avic.c:911:27: note: in expansion of macro ‘BIT’
> 911 | BIT(APICV_INHIBIT_REASON_SEV |
> | ^~~
>
> Fixes: 3743c2f02517 ("KVM: x86: inhibit APICv/AVIC on changes to APIC ID or APIC base")
> Cc: Maxim Levitsky <mlevitsk@redhat.com>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> arch/x86/kvm/svm/avic.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/svm/avic.c b/arch/x86/kvm/svm/avic.c
> index 5542d8959e11..d1bc5820ea46 100644
> --- a/arch/x86/kvm/svm/avic.c
> +++ b/arch/x86/kvm/svm/avic.c
> @@ -908,9 +908,9 @@ bool avic_check_apicv_inhibit_reasons(enum kvm_apicv_inhibit reason)
> BIT(APICV_INHIBIT_REASON_PIT_REINJ) |
> BIT(APICV_INHIBIT_REASON_X2APIC) |
> BIT(APICV_INHIBIT_REASON_BLOCKIRQ) |
> - BIT(APICV_INHIBIT_REASON_SEV |
> + BIT(APICV_INHIBIT_REASON_SEV) |
> BIT(APICV_INHIBIT_REASON_APIC_ID_MODIFIED) |
> - BIT(APICV_INHIBIT_REASON_APIC_BASE_MODIFIED));
> + BIT(APICV_INHIBIT_REASON_APIC_BASE_MODIFIED);
>
> return supported & BIT(reason);
> }
>
> base-commit: b23f8810c46978bc05252db03055a61fcadc07d5
Sorry about it!
Best regards,
Maxim Levitsky
prev parent reply other threads:[~2022-06-11 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 19:18 Sean Christopherson
2022-06-11 13:44 ` Maxim Levitsky [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=1d71f8acb62120aed87238051ef0f22b1ac58470.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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
all inboxes | Powered by JetHome®