From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
KVM <kvm@vger.kernel.org>
Subject: Re: linux-next: Tree for Jan 24 (kvm)
Date: Fri, 24 Jan 2020 13:33:26 -0800 [thread overview]
Message-ID: <20200124213326.GQ2109@linux.intel.com> (raw)
In-Reply-To: <8f6e1118-85ef-6e0d-b023-1277e7d42a1c@infradead.org>
On Fri, Jan 24, 2020 at 12:59:56PM -0800, Randy Dunlap wrote:
> On 1/24/20 12:51 PM, Randy Dunlap wrote:
> > On 1/23/20 10:33 PM, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> Changes since 20200123:
> >>
> >> The kvm tree gained a conflict against Linus' tree.
> >>
> >
> > on i386:
> >
> > ../arch/x86/kvm/x86.h:363:16: warning: right shift count >= width of type [-Wshift-count-overflow]
> >
> >
>
> Sorry, I missed these 2 warnings:
>
> ../arch/x86/kvm/vmx/vmx.c: In function 'vmx_set_msr':
> ../arch/x86/kvm/vmx/vmx.c:2001:14: warning: '~' on a boolean expression [-Wbool-operation]
> if (data & ~kvm_spec_ctrl_valid_bits(vcpu))
> ^
>
>
> ../arch/x86/kvm/svm.c: In function 'svm_set_msr':
> ../arch/x86/kvm/svm.c:4289:14: warning: '~' on a boolean expression [-Wbool-operation]
> if (data & ~kvm_spec_ctrl_valid_bits(vcpu))
> ^
> ../arch/x86/kvm/svm.c:4289:14: note: did you mean to use logical not?
> if (data & ~kvm_spec_ctrl_valid_bits(vcpu))
> ^
> !
Paolo has a fix in the works for this[1], pretty sure he's going to fixup
the offending commit directly[2].
Thanks!
[1] https://lkml.kernel.org/r/6b725990-f0c2-6577-be7e-44e101e540b5@redhat.com
[2] https://lkml.kernel.org/r/8f43bd04-9f4e-5c06-8d1d-cb84bba40278@redhat.com
>
> --
> ~Randy
>
next prev parent reply other threads:[~2020-01-24 21:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 6:33 linux-next: Tree for Jan 24 Stephen Rothwell
2020-01-24 20:51 ` linux-next: Tree for Jan 24 (kvm) Randy Dunlap
2020-01-24 20:59 ` Randy Dunlap
2020-01-24 21:33 ` Sean Christopherson [this message]
2020-01-24 21:30 ` Sean Christopherson
2020-01-24 21:48 ` Jim Mattson
2020-01-24 22:22 ` Sean Christopherson
2020-01-24 22:33 ` Jim Mattson
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=20200124213326.GQ2109@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--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 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.