From: Jan Kiszka <jan.kiszka@web.de>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 2/4] KVM: Rework VCPU state writeback API
Date: Tue, 02 Mar 2010 09:00:04 +0100 [thread overview]
Message-ID: <4B8CC584.1060106@web.de> (raw)
In-Reply-To: <20100302001415.GA22627@amt.cnet>
[-- Attachment #1: Type: text/plain, Size: 2039 bytes --]
Marcelo Tosatti wrote:
> On Mon, Mar 01, 2010 at 07:10:30PM +0100, Jan Kiszka wrote:
>> This grand cleanup drops all reset and vmsave/load related
>> synchronization points in favor of four(!) generic hooks:
>>
>> - cpu_synchronize_all_states in qemu_savevm_state_complete
>> (initial sync from kernel before vmsave)
>> - cpu_synchronize_all_post_init in qemu_loadvm_state
>> (writeback after vmload)
>> - cpu_synchronize_all_post_init in main after machine init
>> - cpu_synchronize_all_post_reset in qemu_system_reset
>> (writeback after system reset)
>>
>> These writeback points + the existing one of VCPU exec after
>> cpu_synchronize_state map on three levels of writeback:
>>
>> - KVM_PUT_RUNTIME_STATE (during runtime, other VCPUs continue to run)
>> - KVM_PUT_RESET_STATE (on synchronous system reset, all VCPUs stopped)
>> - KVM_PUT_FULL_STATE (on init or vmload, all VCPUs stopped as well)
>>
>> This level is passed to the arch-specific VCPU state writing function
>> that will decide which concrete substates need to be written. That way,
>> no writer of load, save or reset functions that interact with in-kernel
>> KVM states will ever have to worry about synchronization again. That
>> also means that a lot of reasons for races, segfaults and deadlocks are
>> eliminated.
>>
>> cpu_synchronize_state remains untouched, just as Anthony suggested. We
>> continue to need it before reading or writing of VCPU states that are
>> also tracked by in-kernel KVM subsystems.
>>
>> Consequently, this patch removes many cpu_synchronize_state calls that
>> are now redundant, just like remaining explicit register syncs.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>
> Jan,
>
> This patch breaks system reset of WinXP.32 install (more easily
> reproducible without iothread enabled).
>
> Screenshot attached.
>
Strange - no issues with qemu-kvm? Any special command line switch? /me
goes scrounging for some installation XP32 CD in the meantime...
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2010-03-02 8:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 18:10 [Qemu-devel] [PATCH 0/4] [uq/master] VCPU writeback rework and related bits Jan Kiszka
2010-03-01 18:10 ` [Qemu-devel] [PATCH 1/4] KVM: Rework of guest debug state writing Jan Kiszka
2010-03-01 18:10 ` [Qemu-devel] [PATCH 2/4] KVM: Rework VCPU state writeback API Jan Kiszka
2010-03-02 0:14 ` [Qemu-devel] " Marcelo Tosatti
2010-03-02 8:00 ` Jan Kiszka [this message]
2010-03-02 11:55 ` Marcelo Tosatti
2010-03-02 16:31 ` Jan Kiszka
2010-03-03 2:29 ` Marcelo Tosatti
2010-03-04 4:21 ` Marcelo Tosatti
2010-03-04 5:58 ` Kevin O'Connor
2010-03-04 18:35 ` Marcelo Tosatti
2010-03-06 2:37 ` Kevin O'Connor
2010-03-08 20:33 ` Marcelo Tosatti
2010-03-09 13:56 ` Anthony Liguori
2010-03-11 8:32 ` Avi Kivity
2010-03-11 18:49 ` Marcelo Tosatti
2010-03-01 18:10 ` [Qemu-devel] [PATCH 3/4] KVM: x86: Restrict writeback of VCPU state Jan Kiszka
2010-03-01 18:10 ` [Qemu-devel] [PATCH 4/4] x86: Extend validity of bsp_to_cpu Jan Kiszka
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=4B8CC584.1060106@web.de \
--to=jan.kiszka@web.de \
--cc=avi@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).