From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Greg Kurz <groug@kaod.org>,
clg@kaod.org, aik@ozlabs.ru, mdroth@linux.vnet.ibm.com,
nikunj@linux.vnet.ibm.com, agraf@suse.de, abologna@redhat.com,
armbru@redhat.com, qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
quintela@redhat.com, sursingh@redhat.com, sbobroff@redhat.com
Subject: Re: [Qemu-devel] [PATCHv4 2/5] migration: Mark CPU states dirty before incoming migration/loadvm
Date: Tue, 30 May 2017 10:14:17 +0100 [thread overview]
Message-ID: <20170530091416.GF2120@work-vm> (raw)
In-Reply-To: <20170530061523.GD12163@umbus.fritz.box>
* David Gibson (david@gibson.dropbear.id.au) wrote:
> On Mon, May 29, 2017 at 10:46:05PM +0200, Greg Kurz wrote:
> > On Fri, 26 May 2017 15:23:16 +1000
> > David Gibson <david@gibson.dropbear.id.au> wrote:
> >
> > > As a rule, CPU internal state should never be updated when
> > > !cpu->kvm_vcpu_dirty (or the HAX equivalent). If that is done, then
> > > subsequent calls to cpu_synchronize_state() - usually safe and idempotent -
> > > will clobber state.
> > >
> > > However, we routinely do this during a loadvm or incoming migration.
> > > Usually this is called shortly after a reset, which will clear all the cpu
> > > dirty flags with cpu_synchronize_all_post_reset(). Nothing is expected
> > > to set the dirty flags again before the cpu state is loaded from the
> > > incoming stream.
> > >
> > > This means that it isn't safe to call cpu_synchronize_state() from a
> > > post_load handler, which is non-obvious and potentially inconvenient.
> > >
> > > We could cpu_synchronize_all_state() before the loadvm, but that would be
> > > overkill since a) we expect the state to already be synchronized from the
> > > reset and b) we expect to completely rewrite the state with a call to
> > > cpu_synchronize_all_post_init() at the end of qemu_loadvm_state().
> > >
> > > To clear this up, this patch introduces cpu_synchronize_pre_loadvm() and
> > > associated helpers, which simply marks the cpu state as dirty without
> > > actually changing anything. i.e. it says we want to discard any existing
> > > KVM (or HAX) state and replace it with what we're going to load.
> > >
> >
> > This makes sense and looks nicer than adding a post-load specific path to
> > ppc_set_compat() indeed.
> >
> > Just one remark below.
> >
> > > Cc: Juan Quintela <quintela@redhat.com>
> > > Cc: Dave Gilbert <dgilbert@redhat.com>
> > > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> > > ---
> > > cpus.c | 9 +++++++++
> > > include/sysemu/cpus.h | 1 +
> > > include/sysemu/hax.h | 1 +
> > > include/sysemu/hw_accel.h | 10 ++++++++++
> > > include/sysemu/kvm.h | 1 +
> > > kvm-all.c | 10 ++++++++++
> > > migration/savevm.c | 2 ++
> > > target/i386/hax-all.c | 10 ++++++++++
> > > 8 files changed, 44 insertions(+)
> > >
> > > diff --git a/cpus.c b/cpus.c
> > > index 516e5cb..6398439 100644
> > > --- a/cpus.c
> > > +++ b/cpus.c
> > > @@ -921,6 +921,15 @@ void cpu_synchronize_all_post_init(void)
> > > }
> > > }
> > >
> > > +void cpu_synchronize_all_pre_loadvm(void)
> > > +{
> > > + CPUState *cpu;
> > > +
> > > + CPU_FOREACH(cpu) {
> > > + cpu_synchronize_pre_loadvm(cpu);
> > > + }
> > > +}
> > > +
> > > static int do_vm_stop(RunState state)
> > > {
> > > int ret = 0;
> > > diff --git a/include/sysemu/cpus.h b/include/sysemu/cpus.h
> > > index a8053f1..731756d 100644
> > > --- a/include/sysemu/cpus.h
> > > +++ b/include/sysemu/cpus.h
> > > @@ -27,6 +27,7 @@ void qemu_timer_notify_cb(void *opaque, QEMUClockType type);
> > > void cpu_synchronize_all_states(void);
> > > void cpu_synchronize_all_post_reset(void);
> > > void cpu_synchronize_all_post_init(void);
> > > +void cpu_synchronize_all_pre_loadvm(void);
> > >
> > > void qtest_clock_warp(int64_t dest);
> > >
> > > diff --git a/include/sysemu/hax.h b/include/sysemu/hax.h
> > > index d9f0239..232a68a 100644
> > > --- a/include/sysemu/hax.h
> > > +++ b/include/sysemu/hax.h
> > > @@ -33,6 +33,7 @@ int hax_populate_ram(uint64_t va, uint32_t size);
> > > void hax_cpu_synchronize_state(CPUState *cpu);
> > > void hax_cpu_synchronize_post_reset(CPUState *cpu);
> > > void hax_cpu_synchronize_post_init(CPUState *cpu);
> > > +void hax_cpu_synchronize_pre_loadvm(CPUState *cpu);
> > >
> > > #ifdef CONFIG_HAX
> > >
> > > diff --git a/include/sysemu/hw_accel.h b/include/sysemu/hw_accel.h
> > > index c9b3105..469ffda 100644
> > > --- a/include/sysemu/hw_accel.h
> > > +++ b/include/sysemu/hw_accel.h
> > > @@ -45,4 +45,14 @@ static inline void cpu_synchronize_post_init(CPUState *cpu)
> > > }
> > > }
> > >
> > > +static inline void cpu_synchronize_pre_loadvm(CPUState *cpu)
> > > +{
> > > + if (kvm_enabled()) {
> > > + kvm_cpu_synchronize_pre_loadvm(cpu);
> > > + }
> > > + if (hax_enabled()) {
> > > + hax_cpu_synchronize_pre_loadvm(cpu);
> > > + }
> > > +}
> > > +
> > > #endif /* QEMU_HW_ACCEL_H */
> > > diff --git a/include/sysemu/kvm.h b/include/sysemu/kvm.h
> > > index 5cc83f2..a45c145 100644
> > > --- a/include/sysemu/kvm.h
> > > +++ b/include/sysemu/kvm.h
> > > @@ -459,6 +459,7 @@ int kvm_physical_memory_addr_from_host(KVMState *s, void *ram_addr,
> > > void kvm_cpu_synchronize_state(CPUState *cpu);
> > > void kvm_cpu_synchronize_post_reset(CPUState *cpu);
> > > void kvm_cpu_synchronize_post_init(CPUState *cpu);
> > > +void kvm_cpu_synchronize_pre_loadvm(CPUState *cpu);
> > >
> > > void kvm_init_cpu_signals(CPUState *cpu);
> > >
> > > diff --git a/kvm-all.c b/kvm-all.c
> > > index 90b8573..a8485bd 100644
> > > --- a/kvm-all.c
> > > +++ b/kvm-all.c
> > > @@ -1896,6 +1896,16 @@ void kvm_cpu_synchronize_post_init(CPUState *cpu)
> > > run_on_cpu(cpu, do_kvm_cpu_synchronize_post_init, RUN_ON_CPU_NULL);
> > > }
> > >
> > > +static void do_kvm_cpu_synchronize_pre_loadvm(CPUState *cpu, run_on_cpu_data arg)
> > > +{
> > > + cpu->kvm_vcpu_dirty = true;
> > > +}
> > > +
> > > +void kvm_cpu_synchronize_pre_loadvm(CPUState *cpu)
> > > +{
> > > + run_on_cpu(cpu, do_kvm_cpu_synchronize_pre_loadvm, RUN_ON_CPU_NULL);
> >
> > Do we really need to run_on_cpu() since we only set the dirty flag ?
>
> Um.. yeah.. I'm not sure. I left it in out of paranoia, because I
> wasn't sure if there could be memory ordering issues between the qemu
> threads if we just set it from the migration thread.
>
> I'm hoping Dave or Juan will have a better idea.
I don't know the kvm cpu sync stuff well enough.
Dave
> --
> David Gibson | I'll have my music baroque, and my code
> david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
> | _way_ _around_!
> http://www.ozlabs.org/~dgibson
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2017-05-30 9:14 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 5:23 [Qemu-devel] [PATCHv4 0/5] Clean up compatibility mode handling David Gibson
2017-05-26 5:23 ` [Qemu-devel] [PATCHv4 1/5] qapi: add explicit null to string input and output visitors David Gibson
2017-05-26 5:23 ` [Qemu-devel] [PATCHv4 2/5] migration: Mark CPU states dirty before incoming migration/loadvm David Gibson
2017-05-29 20:46 ` Greg Kurz
2017-05-30 6:15 ` David Gibson
2017-05-30 9:14 ` Dr. David Alan Gilbert [this message]
2017-05-30 13:03 ` Juan Quintela
2017-05-26 5:23 ` [Qemu-devel] [PATCHv4 3/5] pseries: Move CPU compatibility property to machine David Gibson
2017-06-01 5:44 ` [Qemu-devel] [Qemu-ppc] " Suraj Jitindar Singh
2017-06-01 7:13 ` David Gibson
2017-06-01 7:29 ` Greg Kurz
2017-06-01 12:24 ` David Gibson
2017-06-01 15:44 ` Greg Kurz
2017-05-26 5:23 ` [Qemu-devel] [PATCHv4 4/5] pseries: Reset CPU compatibility mode David Gibson
2017-05-26 5:23 ` [Qemu-devel] [PATCHv4 5/5] ppc: Rework CPU compatibility testing across migration David Gibson
2017-06-01 6:23 ` [Qemu-devel] [Qemu-ppc] " Suraj Jitindar Singh
2017-06-01 8:23 ` [Qemu-devel] " Greg Kurz
2017-06-02 2:25 ` David Gibson
2017-05-29 23:14 ` [Qemu-devel] [PATCHv4 0/5] Clean up compatibility mode handling Greg Kurz
2017-05-30 6:18 ` David Gibson
2017-05-30 8:01 ` Greg Kurz
2017-05-31 2:57 ` David Gibson
2017-05-31 8:58 ` Greg Kurz
2017-06-01 6:52 ` David Gibson
2017-06-01 11:59 ` Cédric Le Goater
2017-06-01 13:09 ` Greg Kurz
2017-06-02 2:00 ` David Gibson
2017-06-02 8:15 ` Greg Kurz
2017-06-04 11:09 ` David Gibson
2017-06-02 1:55 ` David Gibson
2017-06-01 6:59 ` no-reply
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=20170530091416.GF2120@work-vm \
--to=dgilbert@redhat.com \
--cc=abologna@redhat.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=armbru@redhat.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=mdroth@linux.vnet.ibm.com \
--cc=nikunj@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=quintela@redhat.com \
--cc=sbobroff@redhat.com \
--cc=sursingh@redhat.com \
/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).