From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>, Marcelo Tosatti <mtosatti@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] [PATCH v4 00/10] qemu-kvm: Hook cleanups and yet more use of upstream code
Date: Mon, 1 Mar 2010 18:17:19 +0100 [thread overview]
Message-ID: <cover.1267463833.git.jan.kiszka@siemens.com> (raw)
Rebased over latest master.
Pull URL is
git://git.kiszka.org/qemu-kvm.git queues/queues-kvm-merge
Jan Kiszka (10):
qemu-kvm: Add KVM_CAP_X86_ROBUST_SINGLESTEP-awareness
qemu-kvm: Rework VCPU state writeback API
x86: Extend validity of cpu_is_bsp
qemu-kvm: Clean up mpstate synchronization
KVM: x86: Restrict writeback of VCPU state
qemu-kvm: Use VCPU event state for reset and vmsave/load
qemu-kvm: Cleanup/fix TSC and PV clock writeback
qemu-kvm: Clean up KVM's APIC hooks
qemu-kvm: Move kvm_set_boot_cpu_id
qemu-kvm: Bring qemu_init_vcpu back home
exec.c | 17 -----
hw/apic.c | 47 ++-------------
hw/pc.c | 12 +---
hw/ppc_newworld.c | 3 -
hw/ppc_oldworld.c | 3 -
hw/s390-virtio.c | 1 -
kvm-all.c | 31 ++++++++--
kvm.h | 28 ++++++++-
qemu-kvm-ia64.c | 6 +-
qemu-kvm-x86.c | 164 ++++++++++++++++++++++++-------------------------
qemu-kvm.c | 46 ++++----------
qemu-kvm.h | 27 +-------
savevm.c | 4 +
sysemu.h | 4 +
target-i386/helper.c | 2 +
target-i386/kvm.c | 94 +++++++++++++++++-----------
target-i386/machine.c | 27 --------
target-ia64/machine.c | 5 +-
target-ppc/kvm.c | 2 +-
target-ppc/machine.c | 4 -
target-s390x/kvm.c | 3 +-
vl.c | 29 +++++++++
22 files changed, 259 insertions(+), 300 deletions(-)
next reply other threads:[~2010-03-01 17:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 17:17 Jan Kiszka [this message]
2010-03-01 17:17 ` [Qemu-devel] [PATCH v4 01/10] qemu-kvm: Add KVM_CAP_X86_ROBUST_SINGLESTEP-awareness Jan Kiszka
2010-03-01 17:17 ` [Qemu-devel] [PATCH v4 02/10] qemu-kvm: Rework VCPU state writeback API Jan Kiszka
2010-03-01 17:17 ` [Qemu-devel] [PATCH v4 03/10] x86: Extend validity of cpu_is_bsp Jan Kiszka
2010-03-03 16:00 ` [Qemu-devel] " Gleb Natapov
2010-03-03 23:34 ` Jan Kiszka
2010-03-04 6:47 ` Gleb Natapov
2010-03-04 8:23 ` Jan Kiszka
2010-03-04 8:35 ` Gleb Natapov
2010-03-04 11:35 ` Jan Kiszka
2010-03-04 12:03 ` Gleb Natapov
2010-03-07 6:36 ` Gleb Natapov
2010-03-07 10:48 ` Jan Kiszka
2010-03-07 13:44 ` Jan Kiszka
2010-03-07 13:50 ` Gleb Natapov
2010-03-01 17:17 ` [Qemu-devel] [PATCH v4 04/10] qemu-kvm: Clean up mpstate synchronization Jan Kiszka
2010-03-01 17:17 ` [Qemu-devel] [PATCH v4 05/10] KVM: x86: Restrict writeback of VCPU state Jan Kiszka
2010-03-01 17:17 ` [Qemu-devel] [PATCH v4 06/10] qemu-kvm: Use VCPU event state for reset and vmsave/load Jan Kiszka
2010-03-01 17:17 ` [Qemu-devel] [PATCH v4 07/10] qemu-kvm: Cleanup/fix TSC and PV clock writeback Jan Kiszka
2010-03-01 17:17 ` [Qemu-devel] [PATCH v4 08/10] qemu-kvm: Clean up KVM's APIC hooks Jan Kiszka
2010-03-01 17:17 ` [Qemu-devel] [PATCH v4 09/10] qemu-kvm: Move kvm_set_boot_cpu_id Jan Kiszka
2010-03-01 17:17 ` [Qemu-devel] [PATCH v4 10/10] qemu-kvm: Bring qemu_init_vcpu back home Jan Kiszka
2010-03-01 17:21 ` [Qemu-devel] Re: [PATCH v4 00/10] qemu-kvm: Hook cleanups and yet more use of upstream code Jan Kiszka
2010-03-01 20:01 ` Marcelo Tosatti
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=cover.1267463833.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.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).