From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 72381] [Nested] L1 call trace when create windows 7 guest as L2 guest.
Date: Fri, 08 Aug 2014 05:36:00 +0000 [thread overview]
Message-ID: <bug-72381-28872-nxweDfiuIa@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-72381-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=72381
--- Comment #4 from Zhou, Chao <chao.zhou@intel.com> ---
this commit fixed the bug:
commit 9242b5b60df8b13b469bc6b7be08ff6ebb551ad3
Author: Bandan Das <bsd@redhat.com>
Date: Tue Jul 8 00:30:23 2014 -0400
KVM: x86: Check for nested events if there is an injectable interrupt
With commit b6b8a1451fc40412c57d1 that introduced
vmx_check_nested_events, checks for injectable interrupts happen
at different points in time for L1 and L2 that could potentially
cause a race. The regression occurs because KVM_REQ_EVENT is always
set when nested_run_pending is set even if there's no pending interrupt.
Consequently, there could be a small window when check_nested_events
returns without exiting to L1, but an interrupt comes through soon
after and it incorrectly, gets injected to L2 by inject_pending_event
Fix this by adding a call to check for nested events too when a check
for injectable interrupt returns true
Signed-off-by: Bandan Das <bsd@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-08-08 5:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 7:43 [Bug 72381] New: [Nested] L1 call trace when create windows 7 guest as L2 guest bugzilla-daemon
2014-03-24 17:38 ` [Bug 72381] " bugzilla-daemon
2014-03-26 8:38 ` bugzilla-daemon
2014-08-08 5:35 ` bugzilla-daemon
2014-08-08 5:36 ` bugzilla-daemon [this message]
2014-08-08 5:38 ` bugzilla-daemon
2014-08-08 5:38 ` bugzilla-daemon
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=bug-72381-28872-nxweDfiuIa@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.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 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.