From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Ilya Maximets <i.maximets@samsung.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [RFC 0/2] vhost+postcopy fixes
Date: Wed, 10 Oct 2018 09:28:57 +0200 [thread overview]
Message-ID: <d33b389d-34ac-bd32-4915-a94cc239d7cc@redhat.com> (raw)
In-Reply-To: <20181008160536.6332-1-i.maximets@samsung.com>
On 10/08/2018 06:05 PM, Ilya Maximets wrote:
> Sending as RFC because it's not fully tested yet.
>
> Ilya Maximets (2):
> migration: Stop postcopy fault thread before notifying
> vhost-user: Fix userfaultfd leak
>
> hw/virtio/vhost-user.c | 7 +++++++
> migration/postcopy-ram.c | 11 ++++++-----
> 2 files changed, 13 insertions(+), 5 deletions(-)
>
For the series:
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
next prev parent reply other threads:[~2018-10-10 7:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20181008160317eucas1p12156552c6876786bd3087d3922d49399@eucas1p1.samsung.com>
2018-10-08 16:05 ` [Qemu-devel] [RFC 0/2] vhost+postcopy fixes Ilya Maximets
[not found] ` <CGME20181008160325eucas1p23bd6b6ce112175d274db884fb2a83f54@eucas1p2.samsung.com>
2018-10-08 16:05 ` [Qemu-devel] [RFC 1/2] migration: Stop postcopy fault thread before notifying Ilya Maximets
2018-10-10 19:01 ` Dr. David Alan Gilbert
[not found] ` <CGME20181008160328eucas1p14fff8e1e5e5f065019353fb86b845340@eucas1p1.samsung.com>
2018-10-08 16:05 ` [Qemu-devel] [RFC 2/2] vhost-user: Fix userfaultfd leak Ilya Maximets
2018-10-10 19:05 ` Dr. David Alan Gilbert
2018-10-10 7:28 ` Maxime Coquelin [this message]
2018-10-11 17:43 ` [Qemu-devel] [RFC 0/2] vhost+postcopy fixes 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=d33b389d-34ac-bd32-4915-a94cc239d7cc@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dgilbert@redhat.com \
--cc=i.maximets@samsung.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@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).