From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [Qemu-devel] [PATCH 0/7] kvm: fix system reset & rework slot management
Date: Fri, 17 Apr 2009 09:27:54 -0500 [thread overview]
Message-ID: <49E891EA.6040300@us.ibm.com> (raw)
In-Reply-To: <20090411172025.32383.77687.stgit@mchn012c.ww002.siemens.net>
Jan Kiszka wrote:
> This is the promised series to improve KVM's memory slot management.
> Things turned out to be more complicated and ugly than planned due to an
> unfortunate bug in KVM's kernel code, see [1] and patch 5 of this
> series.
>
> The most important impact of this series is that it finally enables
> support for resetting qemu guests in KVM mode. Path 1 and 2 lay the
> groundwork for this, and the slot management rework fixes the remaining
> issues around memory remapping via PAM.
>
> Find the patches also at git://git.kiszka.org/qemu.git queues/kvm
>
> Jan Kiszka (7):
> kvm: Sync CPU state on reset
> kvm: Apply SMM-already-initialized workaround on reset
> kvm: Cleanup unmap condition in kvm_set_phys_mem
> kvm: Add sanity checks to slot management
> kvm: improve handling of overlapping slots
> vga: Fix inconsistent tracking of map_addr
> vga: Cleanup dirty logging
>
> hw/acpi.c | 17 +++--
> hw/cirrus_vga.c | 17 ----
> hw/vga.c | 27 +------
> hw/vga_int.h | 1 -
> kvm-all.c | 219 +++++++++++++++++++++++++++++++++++++++----------------
> kvm.h | 7 +-
> vl.c | 2 +
> 7 files changed, 177 insertions(+), 113 deletions(-)
>
> [1] http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/30680
>
>
I've applied this series but please submit a cleanup to #1.
I decided to just apply this to trunk. It's a lot of churn for stable
and I consider KVM experimental for 0.10.x. If you think it should go
in stable though, I'm willing to reconsider.
Thanks,
Regards,
Anthony Liguori
prev parent reply other threads:[~2009-04-17 14:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 17:20 [Qemu-devel] [PATCH 0/7] kvm: fix system reset & rework slot management Jan Kiszka
2009-04-11 17:20 ` [Qemu-devel] [PATCH 7/7] vga: Cleanup dirty logging Jan Kiszka
2009-04-11 17:20 ` [Qemu-devel] [PATCH 3/7] kvm: Cleanup unmap condition in kvm_set_phys_mem Jan Kiszka
2009-04-11 17:20 ` [Qemu-devel] [PATCH 6/7] vga: Fix inconsistent tracking of map_addr Jan Kiszka
2009-04-11 17:20 ` [Qemu-devel] [PATCH 5/7] kvm: improve handling of overlapping slots Jan Kiszka
2009-04-13 11:00 ` [Qemu-devel] [PATCH 5/7 v2] " Jan Kiszka
2009-04-17 14:36 ` Anthony Liguori
2009-04-11 17:20 ` [Qemu-devel] [PATCH 2/7] kvm: Apply SMM-already-initialized workaround on reset Jan Kiszka
2009-04-11 17:20 ` [Qemu-devel] [PATCH 1/7] kvm: Sync CPU state " Jan Kiszka
2009-04-17 14:26 ` Anthony Liguori
2009-04-11 17:20 ` [Qemu-devel] [PATCH 4/7] kvm: Add sanity checks to slot management Jan Kiszka
2009-04-29 10:31 ` Liu Yu-B13201
2009-04-29 10:38 ` Jan Kiszka
2009-04-29 11:10 ` Liu Yu-B13201
2009-04-29 11:36 ` Jan Kiszka
2009-04-29 17:10 ` Hollis Blanchard
2009-04-29 17:30 ` Jan Kiszka
2009-04-29 17:37 ` Hollis Blanchard
2009-04-29 18:08 ` Jan Kiszka
2009-04-30 2:39 ` Liu Yu-B13201
2009-04-29 17:38 ` Anthony Liguori
2009-04-29 18:02 ` Hollis Blanchard
2009-04-29 18:54 ` Blue Swirl
2009-04-17 14:27 ` Anthony Liguori [this message]
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=49E891EA.6040300@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.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).