From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>, Marcelo Tosatti <mtosatti@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
Gleb Natapov <gleb@redhat.com>
Subject: [Qemu-devel] [PATCH 0/9] qemu-kvm: Extended use of upstream code
Date: Fri, 19 Feb 2010 19:22:18 +0100 [thread overview]
Message-ID: <cover.1266603744.git.jan.kiszka@siemens.com> (raw)
Spin-off from my longer series as Marcelo asked for the last patch as
the next step. I don't see any value in reordering the series, so I just
but off the lower bits.
This part mostly cleans up common KVM code that is also present
upstream. It also includes the fixed guest debug writeback, first for
upstream (patch 8 should be queued into uq/master as well), then merged
into qemu-kvm while dropping the qemu-kvm copy of the guest debugging
code.
The differences to previous postings of the full series are:
- rebased over qemu-kvm
- fixed guest state writeback to avoid conflicts with SET_VCPU_EVENTS,
rather use them on modern kernels (I know Gleb will hate me for this,
but I'm convinced it's cleaner that way)
Pull URL is
git://git.kiszka.org/qemu-kvm.git queues/queues-kvm-merge
Jan Kiszka (9):
qemu-kvm: Drop vmport changes
qemu-kvm: Clean up register access API
qemu-kvm: Use upstream kvm_enabled and cpu_synchronize_state
qemu-kvm: Use upstream kvm_setup_guest_memory
qemu-kvm: Use some more upstream prototypes
qemu-kvm: Use upstream kvm_arch_get_supported_cpuid
qemu-kvm: Use upstream kvm_pit_in_kernel
KVM: Rework of guest debug state writing
qemu-kvm: Use upstream guest debug code
hw/i8254.c | 6 +-
hw/i8259.c | 2 +-
hw/ioapic.c | 2 +-
hw/msix.c | 3 +-
hw/pc.c | 4 +-
hw/pcspk.c | 4 +-
hw/piix_pci.c | 2 +-
hw/vmport.c | 13 +--
kvm-all.c | 24 ++---
kvm.h | 11 +--
qemu-kvm-x86.c | 319 ++++++-------------------------------------------
qemu-kvm.c | 110 ++----------------
qemu-kvm.h | 139 +--------------------
target-i386/kvm.c | 43 ++++++-
target-ia64/machine.c | 4 +-
vl.c | 3 +-
16 files changed, 114 insertions(+), 575 deletions(-)
next reply other threads:[~2010-02-19 18:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 18:22 Jan Kiszka [this message]
2010-02-19 18:22 ` [Qemu-devel] [PATCH 1/9] qemu-kvm: Drop vmport changes Jan Kiszka
2010-02-19 18:22 ` [Qemu-devel] [PATCH 2/9] qemu-kvm: Clean up register access API Jan Kiszka
2010-02-21 9:25 ` [Qemu-devel] " Avi Kivity
2010-02-19 18:22 ` [Qemu-devel] [PATCH 3/9] qemu-kvm: Use upstream kvm_enabled and cpu_synchronize_state Jan Kiszka
2010-02-19 18:22 ` [Qemu-devel] [PATCH 4/9] qemu-kvm: Use upstream kvm_setup_guest_memory Jan Kiszka
2010-02-19 18:22 ` [Qemu-devel] [PATCH 5/9] qemu-kvm: Use some more upstream prototypes Jan Kiszka
2010-02-19 18:22 ` [Qemu-devel] [PATCH 6/9] qemu-kvm: Use upstream kvm_arch_get_supported_cpuid Jan Kiszka
2010-02-19 18:22 ` [Qemu-devel] [PATCH 7/9] qemu-kvm: Use upstream kvm_pit_in_kernel Jan Kiszka
2010-02-19 18:22 ` [Qemu-devel] [PATCH 8/9] KVM: Rework of guest debug state writing Jan Kiszka
2010-02-21 9:26 ` [Qemu-devel] " Avi Kivity
2010-02-19 18:22 ` [Qemu-devel] [PATCH 9/9] qemu-kvm: Use upstream guest debug code Jan Kiszka
2010-02-21 9:20 ` [Qemu-devel] Re: [PATCH 0/9] qemu-kvm: Extended use of upstream code Avi Kivity
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.1266603744.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=aliguori@us.ibm.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).