From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>, KVM <kvm@vger.kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warnings after merge of the kvm tree
Date: Fri, 24 Jan 2020 14:10:41 +1100 [thread overview]
Message-ID: <20200124141041.187cb586@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
Hi all,
After merging the kvm tree, today's linux-next build (x86_64 allmodconfig)
produced these warnings:
arch/x86/kvm/svm.c: In function 'svm_set_msr':
arch/x86/kvm/svm.c:4289:14: warning: '~' on a boolean expression [-Wbool-operation]
4289 | if (data & ~kvm_spec_ctrl_valid_bits(vcpu))
| ^
arch/x86/kvm/svm.c:4289:14: note: did you mean to use logical not?
4289 | if (data & ~kvm_spec_ctrl_valid_bits(vcpu))
| ^
| !
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]
2001 | if (data & ~kvm_spec_ctrl_valid_bits(vcpu))
| ^
arch/x86/kvm/vmx/vmx.c:2001:14: note: did you mean to use logical not?
2001 | if (data & ~kvm_spec_ctrl_valid_bits(vcpu))
| ^
| !
Introduced by commit
e71ae535bc24 ("KVM: x86: avoid incorrect writes to host MSR_IA32_SPEC_CTRL")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-01-24 3:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 3:10 Stephen Rothwell [this message]
2021-04-22 8:51 linux-next: build warnings after merge of the kvm tree Stephen Rothwell
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=20200124141041.187cb586@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.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;
as well as URLs for NNTP newsgroup(s).