From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: "Andrey Korolyov" <andrey@xdel.ru>,
"Marcin Gibuła" <m.gibula@beyond.pl>,
"Marcelo Tosatti" <mtosatti@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] kvmclock: Add comment explaining why we need cpu_clean_all_dirty()
Date: Wed, 05 Nov 2014 11:27:34 +0100 [thread overview]
Message-ID: <5459FB96.9020208@redhat.com> (raw)
In-Reply-To: <1415036734-24310-1-git-send-email-ehabkost@redhat.com>
On 03/11/2014 18:45, Eduardo Habkost wrote:
> Try to explain why commit 317b0a6d8ba44e9bf8f9c3dbd776c4536843d82c
> needed a cpu_clean_all_dirty() call just after calling
> cpu_synchronize_all_states().
>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> Cc: Andrey Korolyov <andrey@xdel.ru>
> Cc: Marcin Gibuła <m.gibula@beyond.pl>
> Cc: Marcelo Tosatti <mtosatti@redhat.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> ---
> hw/i386/kvm/clock.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/hw/i386/kvm/clock.c b/hw/i386/kvm/clock.c
> index 1ac60d6..58be2bd 100644
> --- a/hw/i386/kvm/clock.c
> +++ b/hw/i386/kvm/clock.c
> @@ -127,7 +127,21 @@ static void kvmclock_vm_state_change(void *opaque, int running,
> }
>
> cpu_synchronize_all_states();
> + /* In theory, the cpu_synchronize_all_states() call above wouldn't
> + * affect the rest of the code, as the VCPU state inside CPUState
> + * is supposed to always match the VCPU state on the kernel side.
> + *
> + * In practice, calling cpu_synchronize_state() too soon will load the
> + * kernel-side APIC state into X86CPU.apic_state too early, APIC state
> + * won't be reloaded later because CPUState.vcpu_dirty==true, and
> + * outdated APIC state may be migrated to another host.
> + *
> + * The real fix would be to make sure outdated APIC state is read
> + * from the kernel again when necessary. While this is not fixed, we
> + * need the cpu_clean_all_dirty() call below.
> + */
> cpu_clean_all_dirty();
> +
> ret = kvm_vm_ioctl(kvm_state, KVM_GET_CLOCK, &data);
> if (ret < 0) {
> fprintf(stderr, "KVM_GET_CLOCK failed: %s\n", strerror(ret));
>
Thanks, applying to uq/master.
Paolo
prev parent reply other threads:[~2014-11-05 10:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 17:45 [Qemu-devel] [PATCH] kvmclock: Add comment explaining why we need cpu_clean_all_dirty() Eduardo Habkost
2014-11-05 10:27 ` Paolo Bonzini [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=5459FB96.9020208@redhat.com \
--to=pbonzini@redhat.com \
--cc=andrey@xdel.ru \
--cc=ehabkost@redhat.com \
--cc=m.gibula@beyond.pl \
--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).