From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Alexey Perevalov <a.perevalov@samsung.com>,
qemu-devel@nongnu.org, i.maximets@samsung.com,
quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 2/3] migration: introduce qemu_ufd_copy_ioctl helper
Date: Fri, 16 Jun 2017 17:39:39 +0100 [thread overview]
Message-ID: <20170616163938.GD2179@work-vm> (raw)
In-Reply-To: <20170616084936.GG30118@pxdev.xzpeter.org>
* Peter Xu (peterx@redhat.com) wrote:
> On Thu, Jun 15, 2017 at 07:36:14PM +0300, Alexey Perevalov wrote:
> > Just for placing auxilary operations inside helper,
> > auxilary operations like: track received pages,
> > notify about copying operation in futher patches.
> >
> > Signed-off-by: Alexey Perevalov <a.perevalov@samsung.com>
> > ---
> > migration/postcopy-ram.c | 35 ++++++++++++++++++++++-------------
> > 1 file changed, 22 insertions(+), 13 deletions(-)
> >
> > diff --git a/migration/postcopy-ram.c b/migration/postcopy-ram.c
> > index 743ca6c..38a429a 100644
> > --- a/migration/postcopy-ram.c
> > +++ b/migration/postcopy-ram.c
> > @@ -561,6 +561,26 @@ int postcopy_ram_enable_notify(MigrationIncomingState *mis)
> > return 0;
> > }
> >
> > +static int qemu_ufd_copy_ioctl(int userfault_fd, void *host_addr,
> > + void *from_addr, uint64_t pagesize)
> > +{
> > + if (from_addr) {
> > + struct uffdio_copy copy_struct;
> > + copy_struct.dst = (uint64_t)(uintptr_t)host_addr;
> > + copy_struct.src = (uint64_t)(uintptr_t)from_addr;
> > + copy_struct.len = pagesize;
> > + copy_struct.mode = 0;
> > + return ioctl(userfault_fd, UFFDIO_COPY, ©_struct);
> > + } else {
> > + struct uffdio_zeropage zero_struct;
> > + zero_struct.range.start = (uint64_t)(uintptr_t)host_addr;
> > + zero_struct.range.len = pagesize;
> > + zero_struct.mode = 0;
> > + return ioctl(userfault_fd, UFFDIO_ZEROPAGE, &zero_struct);
> > + }
> > + return 0;
>
> Remove this line?
Yes, probably should; only minor.
> > +}
> > +
> > /*
> > * Place a host page (from) at (host) atomically
> > * returns 0 on success
> > @@ -568,20 +588,14 @@ int postcopy_ram_enable_notify(MigrationIncomingState *mis)
> > int postcopy_place_page(MigrationIncomingState *mis, void *host, void *from,
> > RAMBlock *rb)
> > {
> > - struct uffdio_copy copy_struct;
> > size_t pagesize = qemu_ram_pagesize(rb);
> >
> > - copy_struct.dst = (uint64_t)(uintptr_t)host;
> > - copy_struct.src = (uint64_t)(uintptr_t)from;
> > - copy_struct.len = pagesize;
> > - copy_struct.mode = 0;
> > -
> > /* copy also acks to the kernel waking the stalled thread up
> > * TODO: We can inhibit that ack and only do it if it was requested
> > * which would be slightly cheaper, but we'd have to be careful
> > * of the order of updating our page state.
> > */
> > - if (ioctl(mis->userfault_fd, UFFDIO_COPY, ©_struct)) {
> > + if (qemu_ufd_copy_ioctl(mis->userfault_fd, host, from, pagesize)) {
>
> (hmm I know "from" won't be zero, but naturally if without the context
> I would doubt it. Shall we add an assert here? You call.)
Doesn't seem worth it.
> Besides:
>
> Reviewed-by: Peter Xu <peterx@redhat.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>
> Thanks,
>
> > int e = errno;
> > error_report("%s: %s copy host: %p from: %p (size: %zd)",
> > __func__, strerror(e), host, from, pagesize);
> > @@ -605,12 +619,7 @@ int postcopy_place_page_zero(MigrationIncomingState *mis, void *host,
> >
> > pagesize = qemu_ram_pagesize(rb);
> > if (pagesize == getpagesize()) {
> > - struct uffdio_zeropage zero_struct;
> > - zero_struct.range.start = (uint64_t)(uintptr_t)host;
> > - zero_struct.range.len = getpagesize();
> > - zero_struct.mode = 0;
> > -
> > - if (ioctl(mis->userfault_fd, UFFDIO_ZEROPAGE, &zero_struct)) {
> > + if (qemu_ufd_copy_ioctl(mis->userfault_fd, host, 0, getpagesize())) {
> > int e = errno;
> > error_report("%s: %s zero host: %p",
> > __func__, strerror(e), host);
> > --
> > 1.9.1
> >
>
> --
> Peter Xu
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2017-06-16 16:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170615163628eucas1p29770ee263d64d3ad254c1fbaa43a46b2@eucas1p2.samsung.com>
2017-06-15 16:36 ` [Qemu-devel] [PATCH v2 0/3] Add bitmap for received pages in postcopy migration Alexey Perevalov
[not found] ` <CGME20170615163629eucas1p1f0abc79e0d893f6b442a380630821e5d@eucas1p1.samsung.com>
2017-06-15 16:36 ` [Qemu-devel] [PATCH v2 1/3] migration: postcopy_place_page factoring out Alexey Perevalov
2017-06-16 8:46 ` Peter Xu
2017-06-16 16:24 ` Dr. David Alan Gilbert
[not found] ` <CGME20170615163630eucas1p1f7fc8849597e8402e1c537769f4255d6@eucas1p1.samsung.com>
2017-06-15 16:36 ` [Qemu-devel] [PATCH v2 2/3] migration: introduce qemu_ufd_copy_ioctl helper Alexey Perevalov
2017-06-16 8:49 ` Peter Xu
2017-06-16 16:39 ` Dr. David Alan Gilbert [this message]
[not found] ` <CGME20170615163630eucas1p24f8f92a8acc7e408849696645f9557f2@eucas1p2.samsung.com>
2017-06-15 16:36 ` [Qemu-devel] [PATCH v2 3/3] migration: add bitmap for received page Alexey Perevalov
2017-06-16 9:06 ` Peter Xu
2017-06-16 11:55 ` Alexey Perevalov
2017-06-16 17:20 ` Dr. David Alan Gilbert
2017-06-16 17:14 ` Dr. David Alan Gilbert
2017-06-16 17:38 ` Alexey Perevalov
2017-06-16 18:46 ` Dr. David Alan Gilbert
2017-06-16 19:14 ` Alexey Perevalov
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=20170616163938.GD2179@work-vm \
--to=dgilbert@redhat.com \
--cc=a.perevalov@samsung.com \
--cc=i.maximets@samsung.com \
--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).