From: Paolo Bonzini <pbonzini@redhat.com>
To: Dmitry Vyukov <dvyukov@google.com>,
syzkaller <syzkaller@googlegroups.com>
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"KVM list" <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Steve Rutherford" <srutherford@google.com>
Subject: Re: kvm: WARNING in kvm_arch_vcpu_ioctl_run
Date: Mon, 14 Nov 2016 15:45:22 +0100 [thread overview]
Message-ID: <8a829321-d79e-95fb-9df6-db032fb78305@redhat.com> (raw)
In-Reply-To: <CACT4Y+bBufzSAC3JvWgNxxWtMBFL6mkDDcxmxjbNoQtKNUdAaw@mail.gmail.com>
On 14/11/2016 15:09, Dmitry Vyukov wrote:
>
> I made dump_vmcs() no-op locally. You should see the warning
> regardless, but probably it is difficult to notice. Or maybe tons of
> output affect timings so that the warning does not happen.
I let it run for several minutes, and only got 50 splats out of several
thousand iterations. Reproducing is not going to help much anyway---if
we can get to the root cause, writing a reliable reproducer would be
easier anyway.
Paolo
next prev parent reply other threads:[~2016-11-14 14:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 14:00 kvm: WARNING in kvm_arch_vcpu_ioctl_run Dmitry Vyukov
2016-11-14 14:03 ` Paolo Bonzini
2016-11-14 14:09 ` Dmitry Vyukov
2016-11-14 14:45 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-09 17:07 Dmitry Vyukov
2017-08-09 17:09 ` Dmitry Vyukov
2017-08-09 17:11 ` Dmitry Vyukov
2017-08-09 20:24 ` David Hildenbrand
2017-08-09 20:35 ` Dmitry Vyukov
2017-08-09 21:53 ` Wanpeng Li
2017-08-10 5:37 ` Wanpeng Li
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=8a829321-d79e-95fb-9df6-db032fb78305@redhat.com \
--to=pbonzini@redhat.com \
--cc=dvyukov@google.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=srutherford@google.com \
--cc=syzkaller@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).