From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kernel test robot <lkp@intel.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
llvm@lists.linux.dev, kbuild-all@lists.01.org,
kvm@vger.kernel.org, Robert Hu <robert.hu@intel.com>,
Farrah Chen <farrah.chen@intel.com>,
Danmei Wei <danmei.wei@intel.com>
Subject: Re: [kvm:queue 5/184] arch/x86/kvm/svm/avic.c:913:6: warning: shift count >= width of type
Date: Tue, 14 Jun 2022 15:01:51 +0000 [thread overview]
Message-ID: <Yqii3+EN1SnQYnMJ@google.com> (raw)
In-Reply-To: <7a5d48d0-d1b5-91aa-8966-54d9ac986126@redhat.com>
On Tue, Jun 14, 2022, Paolo Bonzini wrote:
> On 6/13/22 16:49, kernel test robot wrote:
> > 902
> > 903 bool avic_check_apicv_inhibit_reasons(enum kvm_apicv_inhibit reason)
> > 904 {
> > 905 ulong supported = BIT(APICV_INHIBIT_REASON_DISABLE) |
> > 906 BIT(APICV_INHIBIT_REASON_ABSENT) |
> > 907 BIT(APICV_INHIBIT_REASON_HYPERV) |
> > 908 BIT(APICV_INHIBIT_REASON_NESTED) |
> > 909 BIT(APICV_INHIBIT_REASON_IRQWIN) |
> > 910 BIT(APICV_INHIBIT_REASON_PIT_REINJ) |
> > 911 BIT(APICV_INHIBIT_REASON_X2APIC) |
> > 912 BIT(APICV_INHIBIT_REASON_BLOCKIRQ) |
> > > 913 BIT(APICV_INHIBIT_REASON_SEV |
> > 914 BIT(APICV_INHIBIT_REASON_APIC_ID_MODIFIED) |
> > 915 BIT(APICV_INHIBIT_REASON_APIC_BASE_MODIFIED));
>
> Ouch, saw this right after sending a pull request. :(
KVM_WERROR=y is your friend. Or in my case, my enemy for the last few days :-D
WARNING: multiple messages have this Message-ID (diff)
From: Sean Christopherson <seanjc@google.com>
To: kbuild-all@lists.01.org
Subject: Re: [kvm:queue 5/184] arch/x86/kvm/svm/avic.c:913:6: warning: shift count >= width of type
Date: Tue, 14 Jun 2022 15:01:51 +0000 [thread overview]
Message-ID: <Yqii3+EN1SnQYnMJ@google.com> (raw)
In-Reply-To: <7a5d48d0-d1b5-91aa-8966-54d9ac986126@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
On Tue, Jun 14, 2022, Paolo Bonzini wrote:
> On 6/13/22 16:49, kernel test robot wrote:
> > 902
> > 903 bool avic_check_apicv_inhibit_reasons(enum kvm_apicv_inhibit reason)
> > 904 {
> > 905 ulong supported = BIT(APICV_INHIBIT_REASON_DISABLE) |
> > 906 BIT(APICV_INHIBIT_REASON_ABSENT) |
> > 907 BIT(APICV_INHIBIT_REASON_HYPERV) |
> > 908 BIT(APICV_INHIBIT_REASON_NESTED) |
> > 909 BIT(APICV_INHIBIT_REASON_IRQWIN) |
> > 910 BIT(APICV_INHIBIT_REASON_PIT_REINJ) |
> > 911 BIT(APICV_INHIBIT_REASON_X2APIC) |
> > 912 BIT(APICV_INHIBIT_REASON_BLOCKIRQ) |
> > > 913 BIT(APICV_INHIBIT_REASON_SEV |
> > 914 BIT(APICV_INHIBIT_REASON_APIC_ID_MODIFIED) |
> > 915 BIT(APICV_INHIBIT_REASON_APIC_BASE_MODIFIED));
>
> Ouch, saw this right after sending a pull request. :(
KVM_WERROR=y is your friend. Or in my case, my enemy for the last few days :-D
next prev parent reply other threads:[~2022-06-14 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 14:49 [kvm:queue 5/184] arch/x86/kvm/svm/avic.c:913:6: warning: shift count >= width of type kernel test robot
2022-06-14 12:12 ` Paolo Bonzini
2022-06-14 12:12 ` Paolo Bonzini
2022-06-14 15:01 ` Sean Christopherson [this message]
2022-06-14 15:01 ` Sean Christopherson
2022-06-14 16:52 ` Paolo Bonzini
2022-06-14 16:52 ` Paolo Bonzini
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=Yqii3+EN1SnQYnMJ@google.com \
--to=seanjc@google.com \
--cc=danmei.wei@intel.com \
--cc=farrah.chen@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kvm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=robert.hu@intel.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.