qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, peterx@redhat.com, clg@kaod.org
Subject: Re: [Qemu-devel] [PATCH 2/2] migration: Poison ramblock loops in migration
Date: Wed, 6 Jun 2018 11:37:41 +0800	[thread overview]
Message-ID: <20180606033741.GB2606@xz-mi> (raw)
In-Reply-To: <20180606033600.GA2606@xz-mi>

On Wed, Jun 06, 2018 at 11:36:00AM +0800, Peter Xu wrote:
> On Tue, Jun 05, 2018 at 05:25:45PM +0100, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> > 
> > The migration code should be using the
> >   RAMBLOCK_FOREACH_MIGRATABLE and qemu_ram_foreach_block_migratable
> > not the all-block versions;  poison them so that we can't accidentally
> > use them.
> > 
> > Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> > ---
> >  include/exec/ramlist.h | 4 +++-
> >  migration/migration.h  | 3 +++
> >  migration/ram.c        | 4 +++-
> >  3 files changed, 9 insertions(+), 2 deletions(-)
> > 
> > diff --git a/include/exec/ramlist.h b/include/exec/ramlist.h
> > index 2e2ac6cb99..bc4faa1b00 100644
> > --- a/include/exec/ramlist.h
> > +++ b/include/exec/ramlist.h
> > @@ -56,8 +56,10 @@ typedef struct RAMList {
> >  extern RAMList ram_list;
> >  
> >  /* Should be holding either ram_list.mutex, or the RCU lock. */
> > -#define  RAMBLOCK_FOREACH(block)  \
> > +#define  INTERNAL_RAMBLOCK_FOREACH(block)  \
> >      QLIST_FOREACH_RCU(block, &ram_list.blocks, next)
> > +/* Never use the INTERNAL_ version except for defining other macros */
> > +#define RAMBLOCK_FOREACH(block) INTERNAL_RAMBLOCK_FOREACH(block)
> >  
> >  void qemu_mutex_lock_ramlist(void);
> >  void qemu_mutex_unlock_ramlist(void);
> > diff --git a/migration/migration.h b/migration/migration.h
> > index 5af57d616c..31d3ed12dc 100644
> > --- a/migration/migration.h
> > +++ b/migration/migration.h
> > @@ -284,4 +284,7 @@ void migrate_send_rp_resume_ack(MigrationIncomingState *mis, uint32_t value);
> >  void dirty_bitmap_mig_before_vm_start(void);
> >  void init_dirty_bitmap_incoming_migration(void);
> >  
> > +#define qemu_ram_foreach_block \
> > +  #warning "Use qemu_ram_foreach_block_migratable in migration code"
> > +
> >  #endif
> > diff --git a/migration/ram.c b/migration/ram.c
> > index a7807cea84..e0d19305ee 100644
> > --- a/migration/ram.c
> > +++ b/migration/ram.c
> > @@ -159,9 +159,11 @@ out:
> >  
> >  /* Should be holding either ram_list.mutex, or the RCU lock. */
> >  #define RAMBLOCK_FOREACH_MIGRATABLE(block)             \
> > -    RAMBLOCK_FOREACH(block)                            \
> > +    INTERNAL_RAMBLOCK_FOREACH(block)                   \
> >          if (!qemu_ram_is_migratable(block)) {} else
> >  
> > +#undef RAMBLOCK_FOREACH
> 
> This will only cover the ram.c file.  How about we move
> RAMBLOCK_FOREACH_MIGRATABLE() directly into migration.h then undef
> RAMBLOCK_FOREACH there?  Then since migration.h should be used in all
> the migration internal source files so the poisoned bit can be used in
> a broader aspect?

(I forgot to reply-all.... forwarding to the list)

> 
> Thanks,
> 
> > +
> >  static void ramblock_recv_map_init(void)
> >  {
> >      RAMBlock *rb;
> > -- 
> > 2.17.0
> > 
> 
> -- 
> Peter Xu

-- 
Peter Xu

  parent reply	other threads:[~2018-06-06  3:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 16:25 [Qemu-devel] [PATCH 0/2] Fixups for non-migratable RAMBlocks Dr. David Alan Gilbert (git)
2018-06-05 16:25 ` [Qemu-devel] [PATCH 1/2] migration: Fixes " Dr. David Alan Gilbert (git)
2018-06-06  3:38   ` Peter Xu
2018-06-06 18:04   ` Cédric Le Goater
2018-06-05 16:25 ` [Qemu-devel] [PATCH 2/2] migration: Poison ramblock loops in migration Dr. David Alan Gilbert (git)
     [not found]   ` <20180606033600.GA2606@xz-mi>
2018-06-06  3:37     ` Peter Xu [this message]
2018-06-06  8:35       ` Dr. David Alan Gilbert
2018-06-06  9:09         ` Peter Xu
2018-06-06 18:05   ` Cédric Le Goater
2018-06-15 11:21 ` [Qemu-devel] [PATCH 0/2] Fixups for non-migratable RAMBlocks Dr. David Alan Gilbert

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=20180606033741.GB2606@xz-mi \
    --to=peterx@redhat.com \
    --cc=clg@kaod.org \
    --cc=dgilbert@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).