From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org, peterx@redhat.com, clg@kaod.org
Cc: quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] Fixups for non-migratable RAMBlocks
Date: Fri, 15 Jun 2018 12:21:32 +0100 [thread overview]
Message-ID: <20180615112131.GB13796@work-vm> (raw)
In-Reply-To: <20180605162545.80778-1-dgilbert@redhat.com>
* Dr. David Alan Gilbert (git) (dgilbert@redhat.com) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>
> Hi,
> Cédric's b895de50 got merged at about the same
> time as some of Peter's changes and there's a rdma
> case as well; so tidy up those cases that were looping
> over all (rather than just migratable) RAMBlocks
> and poison it so we don't end up doing the same thing
> again.
Queued.
> Dave
>
> Dr. David Alan Gilbert (2):
> migration: Fixes for non-migratable RAMBlocks
> migration: Poison ramblock loops in migration
>
> include/exec/ramlist.h | 4 +++-
> migration/migration.h | 3 +++
> migration/ram.c | 8 +++++---
> migration/rdma.c | 2 +-
> 4 files changed, 12 insertions(+), 5 deletions(-)
>
> --
> 2.17.0
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2018-06-15 11:21 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
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 ` Dr. David Alan Gilbert [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=20180615112131.GB13796@work-vm \
--to=dgilbert@redhat.com \
--cc=clg@kaod.org \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).