From: "Michael S. Tsirkin" <mst@redhat.com>
To: Wei Wang <wei.w.wang@intel.com>
Cc: virtio-dev@lists.oasis-open.org, linux-kernel@vger.kernel.org,
qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org,
kvm@vger.kernel.org, linux-mm@kvack.org, david@redhat.com,
dave.hansen@intel.com, cornelia.huck@de.ibm.com,
akpm@linux-foundation.org, mgorman@techsingularity.net,
aarcange@redhat.com, amit.shah@redhat.com, pbonzini@redhat.com,
liliang.opensource@gmail.com
Subject: Re: [PATCH kernel v8 3/4] mm: add inerface to offer info about unused pages
Date: Fri, 17 Mar 2017 03:21:21 +0200 [thread overview]
Message-ID: <20170317023556-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1489648127-37282-4-git-send-email-wei.w.wang@intel.com>
On Thu, Mar 16, 2017 at 03:08:46PM +0800, Wei Wang wrote:
> +/*
> + * The record_unused_pages() function is used to record the system unused
> + * pages. The unused pages can be skipped to transfer during live migration.
> + * Though the unused pages are dynamically changing, dirty page logging
> + * mechanisms are able to capture the newly used pages though they were
> + * recorded as unused pages via this function.
You will keep confusing people as long as you keep using
this terminology which only makes sense in a very specific
use and a very specific implementation.
How does guest developer know this does the right thing wrt locking etc?
Look at hypervisor spec and try to figure it all out together?
So stop saying what caller should do, describe what does the *API* does.
You want something like this:
Get a list of pages in the system that are unused at some point between
record_unused_pages is called and before it returns, implying that any
data that was present in these pages before record_unused_pages was
called is safe to discard. Pages can be used immediately after
this point and any data written after this point is not safe to discard,
it is caller's responsibility to either prevent the use or
detect such pages.
--
MST
next prev parent reply other threads:[~2017-03-17 1:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 7:08 [PATCH kernel v8 0/4] Extend virtio-balloon for fast (de)inflating & fast live migration Wei Wang
2017-03-16 7:08 ` [PATCH kernel v8 1/4] virtio-balloon: deflate via a page list Wei Wang
2017-03-16 7:08 ` [PATCH kernel v8 2/4] virtio-balloon: VIRTIO_BALLOON_F_CHUNK_TRANSFER Wei Wang
2017-04-05 3:31 ` Wang, Wei W
2017-04-05 3:53 ` Michael S. Tsirkin
2017-04-05 4:31 ` Wang, Wei W
2017-04-05 7:47 ` Wang, Wei W
2017-03-16 7:08 ` [PATCH kernel v8 3/4] mm: add inerface to offer info about unused pages Wei Wang
2017-03-16 21:28 ` Andrew Morton
2017-03-17 6:55 ` Wei Wang
2017-03-22 10:52 ` Wang, Wei W
2017-03-29 17:48 ` Michael S. Tsirkin
2017-03-31 9:53 ` Wei Wang
2017-03-31 16:25 ` Michael S. Tsirkin
2017-04-13 11:07 ` Wei Wang
2017-03-17 1:21 ` Michael S. Tsirkin [this message]
2017-03-16 7:08 ` [PATCH kernel v8 4/4] virtio-balloon: VIRTIO_BALLOON_F_HOST_REQ_VQ Wei Wang
2017-03-17 1:39 ` Michael S. Tsirkin
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=20170317023556-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=amit.shah@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=dave.hansen@intel.com \
--cc=david@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=liliang.opensource@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wei.w.wang@intel.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).