From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 82211] [Nested xen on kvm] L1 guest panic and reboot when L1 guest boot up.
Date: Tue, 12 Aug 2014 07:36:04 +0000 [thread overview]
Message-ID: <bug-82211-28872-mJO0zdehIp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-82211-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=82211
--- Comment #1 from Zhou, Chao <chao.zhou@intel.com> ---
the first bad commit is:
commit 6addfc42992be4b073c39137ecfdf4b2aa2d487f
Author: Paolo Bonzini <pbonzini@redhat.com>
Date: Thu Mar 27 11:29:28 2014 +0100
KVM: x86: avoid useless set of KVM_REQ_EVENT after emulation
Despite the provisions to emulate up to 130 consecutive instructions, in
practice KVM will emulate just one before exiting
handle_invalid_guest_state
because x86_emulate_instruction always sets KVM_REQ_EVENT.
However, we only need to do this if an interrupt could be injected,
which happens a) if an interrupt shadow bit (STI or MOV SS) has gone
away; b) if the interrupt flag has just been set (other instructions
than STI can set it without enabling an interrupt shadow).
This cuts another 700-900 cycles from the cost of emulating an
instruction (measured on a Sandy Bridge Xeon: 1650-2600 cycles
before the patch on kvm-unit-tests, 925-1700 afterwards).
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-12 7:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 7:35 [Bug 82211] New: [Nested xen on kvm] L1 guest panic and reboot when L1 guest boot up bugzilla-daemon
2014-08-12 7:36 ` bugzilla-daemon [this message]
2014-08-12 7:40 ` [Bug 82211] " bugzilla-daemon
2014-08-21 17:56 ` [Bug 82211] [BISECTED][Nested " bugzilla-daemon
2014-09-01 12:46 ` bugzilla-daemon
2014-09-01 13:09 ` [Bug 82211] Cannot boot Xen under KVM with X2APIC enabled bugzilla-daemon
2014-09-01 13:19 ` bugzilla-daemon
2014-09-02 4:50 ` bugzilla-daemon
2014-09-02 6:31 ` bugzilla-daemon
2014-09-03 1:50 ` bugzilla-daemon
2014-09-03 1:58 ` bugzilla-daemon
2014-09-03 11:25 ` bugzilla-daemon
2015-03-17 3:53 ` bugzilla-daemon
2015-03-17 17:01 ` bugzilla-daemon
2015-03-18 18:56 ` bugzilla-daemon
2015-03-20 5:17 ` bugzilla-daemon
2015-04-08 8:36 ` 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-82211-28872-mJO0zdehIp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox