From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] dataplane: RCU dirty memory bitmap for safe RAM hotplug
Date: Thu, 28 Jan 2016 12:05:22 +0100 [thread overview]
Message-ID: <56A9F5F2.3030506@redhat.com> (raw)
In-Reply-To: <20160128104007.GA7206@stefanha-x1.localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 28/01/2016 11:40, Stefan Hajnoczi wrote:
> Paolo, will you take this through your tree/dataplane branch?
>
> I think that would work well since your vring.c removal relies on
> the memory API being thread-safe.
Yes, I'll ensure this gets in before I post the vring.c removal.
I have already reviewed it, but not tested it.
Paolo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJWqfXwAAoJEL/70l94x66DqrgIAI04mitSSu5lY0LzIz8WmewU
04jSj3eVpUfHWhnksGTciwBultpI8VvVUmihip8d26F9qdDnbbXe5ZZTiT7LWK4L
I3cvaWTl++mJQ40AE+aHG4Imq+rjrqPWhFYBUn2hmYpaxGzyrpDryet6uyEkzQt6
b2ZUicDzDD+qkInqpycPSJl7mEvOnbSSLeeVWCRReXPGxJCqATPMETpTJ0NrMWez
pP0ebtEKOTd5OqiUmB5ajyI1Lfia3ePcaOI9RDf+BVPCedhRez7XDRu+t1xACDWm
ofCxO/3/x2GxRB6yNgMj8K5jW9xGrHbYpRu1w5mb84ygY78z6F0ubfDqhdP/Gb8=
=vp25
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2016-01-28 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 13:33 [Qemu-devel] [PATCH 0/2] dataplane: RCU dirty memory bitmap for safe RAM hotplug Stefan Hajnoczi
2016-01-25 13:33 ` [Qemu-devel] [PATCH 1/2] memory: RCU ram_list.dirty_memory[] " Stefan Hajnoczi
2016-01-25 13:33 ` [Qemu-devel] [PATCH 2/2] virtio-blk: drop unused migration.h include Stefan Hajnoczi
2016-01-25 13:46 ` Paolo Bonzini
2016-01-28 10:40 ` [Qemu-devel] [PATCH 0/2] dataplane: RCU dirty memory bitmap for safe RAM hotplug Stefan Hajnoczi
2016-01-28 11:05 ` Paolo Bonzini [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=56A9F5F2.3030506@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@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).