From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Alexander Graf <agraf@suse.de>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
qemu-ppc <qemu-ppc@nongnu.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] spapr: reset @kvm_vcpu_dirty before starting CPU
Date: Tue, 21 Jan 2014 02:02:37 +1100 [thread overview]
Message-ID: <52DD3A8D.4050508@ozlabs.ru> (raw)
In-Reply-To: <2A4B3B3D-EA5D-41F0-A986-ABCB2020BFA3@suse.de>
On 01/21/2014 01:45 AM, Alexander Graf wrote:
>
> On 15.01.2014, at 05:57, Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
>
>> Normally QEMU kvm_arch_get_registers() reads registers and sets a dirty
>> flag which prevents further registers reading from KVM till
>> kvm_arch_put_registers() executes and resets the flag.
>>
>> However if we run QEMU with "-S" ("suspended"), then execute "info cpus"
>> from the QEMU monitor, we end up with not reading registers in
>> rtas_start_cpu() as qmp_query_cpus() calls kvm_cpu_synchronize_state()
>> which leaves @kvm_vcpu_dirty=true what prevents kvm_cpu_synchronize_state()
>> from synchronizing registers and we loose the values.
>
> But that's fine because the values are already synchronized and couldn't
> have changed because the guest cpu wasn't running, no?
Discovered today that "[PATCH] spapr: fix H_SET_MODE to sync LPCR with KVM"
seems to be v2 of this as that patch solves the issue this patch was
intended to solve so I'll drop this one.
>
>
> Alex
>
>>
>> This resets @kvm_vcpu_dirty flag as we do not have content which we really want to
>> keep at this point as the CPU is halted.
>>
>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>> ---
>>
>> We could also reset @kvm_vcpu_dirty in qmp_query_cpus() but that would be
>> racy.
>> ---
>> hw/ppc/spapr_rtas.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/hw/ppc/spapr_rtas.c b/hw/ppc/spapr_rtas.c
>> index 1cb276d..3dade5e 100644
>> --- a/hw/ppc/spapr_rtas.c
>> +++ b/hw/ppc/spapr_rtas.c
>> @@ -185,6 +185,8 @@ static void rtas_start_cpu(PowerPCCPU *cpu_, sPAPREnvironment *spapr,
>> /* This will make sure qemu state is up to date with kvm, and
>> * mark it dirty so our changes get flushed back before the
>> * new cpu enters */
>> +
>> + cs->kvm_vcpu_dirty = false;
>> kvm_cpu_synchronize_state(cs);
>>
>> env->msr = (1ULL << MSR_SF) | (1ULL << MSR_ME);
>> --
>> 1.8.4.rc4
>>
>
--
Alexey
next prev parent reply other threads:[~2014-01-20 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 4:57 [Qemu-devel] [PATCH] spapr: reset @kvm_vcpu_dirty before starting CPU Alexey Kardashevskiy
2014-01-15 22:47 ` Alexey Kardashevskiy
2014-01-20 14:45 ` Alexander Graf
2014-01-20 15:02 ` Alexey Kardashevskiy [this message]
2014-01-20 16:20 ` Andreas Färber
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=52DD3A8D.4050508@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=pbonzini@redhat.com \
--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 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).