From: Paolo Bonzini <pbonzini@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>, peter.maydell@linaro.org
Cc: lvivier@redhat.com, mtosatti@redhat.com, qemu-ppc@nongnu.org,
agraf@suse.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vl: Move cpu_synchronize_all_states() into qemu_system_reset()
Date: Mon, 4 Apr 2016 09:31:16 +0200 [thread overview]
Message-ID: <57021844.6030605@redhat.com> (raw)
In-Reply-To: <1459745351-13138-1-git-send-email-david@gibson.dropbear.id.au>
On 04/04/2016 06:49, David Gibson wrote:
> There are currently 3 calls to qemu_system_reset() in vl.c. Two of them
> are immediately preceded by a cpu_synchronize_all_states9) and the
> remaining one should be.
>
> The one which doesn't is the very first reset called directly from main().
> Without a cpu_synchronize_all_states(), kvm_vcpu_dirty is false at this
> point from the earlier cpu_synchronize_all_post_init(). That's incorrect
> because the reset path is quite likely to update the CPU state, and that
> updated state should be pushed back to KVM, not overwritten with stale
> data pushed to KVM immediately after init.
>
> This patch moves the call to cpu_synchronize_all_states() into
> qemu_system_reset() for safety, so it is always called. AFAICT this should
> be safe for the handful of callers outside vl.c - these all appear to be in
> places where the cpu state is already synchronized so the extra call
> will be a no-op.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> vl.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> This fixes a real but on ppc - the incorrect state of kvm_vcpu_dirty
> means that an extra cpu_synchronize_state() in revised code for
> updating the MSR is not a no-op as expected and loads a stale MSR
> value, resulting in an incorrect MSR value on entry to the guest.
>
> Therefore, I'm hoping to apply this ASAP to 2.6.
>
> Laurent, could you please verify that this does indeed address the
> problem with an incorrect MSR on entry.
>
> diff --git a/vl.c b/vl.c
> index bd81ea9..3629336 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -1745,6 +1745,8 @@ void qemu_system_reset(bool report)
>
> mc = current_machine ? MACHINE_GET_CLASS(current_machine) : NULL;
>
> + cpu_synchronize_all_states();
> +
> if (mc && mc->reset) {
> mc->reset();
> } else {
> @@ -1893,7 +1895,6 @@ static bool main_loop_should_exit(void)
> }
> if (qemu_reset_requested()) {
> pause_all_vcpus();
> - cpu_synchronize_all_states();
> qemu_system_reset(VMRESET_REPORT);
> resume_all_vcpus();
> if (!runstate_check(RUN_STATE_RUNNING) &&
> @@ -1903,7 +1904,6 @@ static bool main_loop_should_exit(void)
> }
> if (qemu_wakeup_requested()) {
> pause_all_vcpus();
> - cpu_synchronize_all_states();
> qemu_system_reset(VMRESET_SILENT);
> notifier_list_notify(&wakeup_notifiers, &wakeup_reason);
> wakeup_reason = QEMU_WAKEUP_REASON_NONE;
>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
next prev parent reply other threads:[~2016-04-04 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 4:49 [Qemu-devel] [PATCH] vl: Move cpu_synchronize_all_states() into qemu_system_reset() David Gibson
2016-04-04 7:31 ` Paolo Bonzini [this message]
2016-04-04 7:54 ` David Gibson
2016-04-04 8:33 ` Paolo Bonzini
2016-04-04 8:24 ` Laurent Vivier
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=57021844.6030605@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=mtosatti@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.