From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: jan.kiszka@siemens.com, gnatapov@redhat.com, mtosatti@redhat.com,
kvm@vger.kernel.org
Subject: [Qemu-devel] [PATCH uq/master 0/2] CPU reset (INIT#) support for KVM
Date: Sat, 9 Mar 2013 07:48:48 +0100 [thread overview]
Message-ID: <1362811730-6716-1-git-send-email-pbonzini@redhat.com> (raw)
This is a follow up to the series I posted earlier this week to
support CPU soft reset. It is a no-op without that series, but
it can be applied independently.
The combined series is available at branch x86-soft-reset of
my github repository (git://github.com/bonzini/qemu.git). With
this series and the corresponding hypervisor patches, the init
test of kvm-unit-tests now passes:
$ x86_64-softmmu/qemu-system-x86_64 \
-kernel ../../kvm-unit-tests/x86/init.flat \
-serial mon:stdio -display none \
-device isa-debug-exit,iobase=0xf4 \
--enable-kvm -machine kernel_irqchip=on
enabling apic
testing port 92 init... enabling apic
testing kbd controller reset... enabling apic
testing kbd controller init... enabling apic
testing 0xcf9h init... enabling apic
testing init to BSP... enabling apic
Paolo
Paolo Bonzini (2):
kvm: report errors from kvm_arch_process_async_events
kvm: forward INIT signals coming from the chipset
kvm-all.c | 8 +++++++-
target-i386/kvm.c | 34 +++++++++++++++++++++++-----------
2 files changed, 30 insertions(+), 12 deletions(-)
--
1.8.1.4
next reply other threads:[~2013-03-09 6:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-09 6:48 Paolo Bonzini [this message]
2013-03-09 6:48 ` [Qemu-devel] [PATCH uq/master 1/2] kvm: detect errors from kvm_arch_process_async_events Paolo Bonzini
2013-03-09 6:48 ` [Qemu-devel] [PATCH uq/master 2/2] kvm: forward INIT signals coming from the chipset Paolo Bonzini
2013-03-10 11:54 ` Gleb Natapov
2013-03-10 14:28 ` Paolo Bonzini
2013-03-10 14:55 ` Gleb Natapov
2013-03-10 15:04 ` Paolo Bonzini
2013-03-10 15:24 ` Gleb Natapov
2013-03-11 7:35 ` Paolo Bonzini
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=1362811730-6716-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=gnatapov@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.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).