All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Longpeng (Mike)" <longpeng2@huawei.com>
To: <aarcange@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, kvm <kvm@vger.kernel.org>,
	QEMU-DEV <qemu-devel@nongnu.org>,
	"Huangweidong (C)" <weidong.huang@huawei.com>,
	"wangxin (U)" <wangxinxin.wang@huawei.com>,
	Zhanghailiang <zhang.zhanghailiang@huawei.com>,
	Gonglei <arei.gonglei@huawei.com>,
	"Longpeng(Mike)" <longpeng2@huawei.com>
Subject: [RESEND] Question about the userfaultfd write-protect support
Date: Mon, 11 Sep 2017 15:06:46 +0800	[thread overview]
Message-ID: <59B63606.6050900@huawei.com> (raw)

(Add Zhanghailiang and Gonglei)


Hi Andrea,

We've implemented a demo of KVM live memory snapshot based on the userfaultfd
write-protect series in your private
tree(https://git.kernel.org/pub/scm/linux/kernel/git/andrea/aa.git/log/). We did
a little hack on that series to make the demo works.

Zhang had discussed with you about this one or two years ago([1][2]), so do you
have any plan to make this series upstream ? If you will, then what is the time
schedule ? We really expect the userfaultfd write-protect series would be merged.

References:
[1] https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg00664.html
[2] https://lists.nongnu.org/archive/html/qemu-devel/2014-11/msg02891.html

-- 
Regards,
Longpeng(Mike)

WARNING: multiple messages have this Message-ID (diff)
From: "Longpeng (Mike)" <longpeng2@huawei.com>
To: aarcange@redhat.com
Cc: linux-kernel@vger.kernel.org, kvm <kvm@vger.kernel.org>,
	QEMU-DEV <qemu-devel@nongnu.org>,
	"Huangweidong (C)" <weidong.huang@huawei.com>,
	"wangxin (U)" <wangxinxin.wang@huawei.com>,
	Zhanghailiang <zhang.zhanghailiang@huawei.com>,
	Gonglei <arei.gonglei@huawei.com>,
	"Longpeng(Mike)" <longpeng2@huawei.com>
Subject: [Qemu-devel] [RESEND] Question about the userfaultfd write-protect support
Date: Mon, 11 Sep 2017 15:06:46 +0800	[thread overview]
Message-ID: <59B63606.6050900@huawei.com> (raw)

(Add Zhanghailiang and Gonglei)


Hi Andrea,

We've implemented a demo of KVM live memory snapshot based on the userfaultfd
write-protect series in your private
tree(https://git.kernel.org/pub/scm/linux/kernel/git/andrea/aa.git/log/). We did
a little hack on that series to make the demo works.

Zhang had discussed with you about this one or two years ago([1][2]), so do you
have any plan to make this series upstream ? If you will, then what is the time
schedule ? We really expect the userfaultfd write-protect series would be merged.

References:
[1] https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg00664.html
[2] https://lists.nongnu.org/archive/html/qemu-devel/2014-11/msg02891.html

-- 
Regards,
Longpeng(Mike)

             reply	other threads:[~2017-09-11  7:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-11  7:06 Longpeng (Mike) [this message]
2017-09-11  7:06 ` [Qemu-devel] [RESEND] Question about the userfaultfd write-protect support Longpeng (Mike)

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=59B63606.6050900@huawei.com \
    --to=longpeng2@huawei.com \
    --cc=aarcange@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=wangxinxin.wang@huawei.com \
    --cc=weidong.huang@huawei.com \
    --cc=zhang.zhanghailiang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.