qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
Cc: Pankaj Gupta <pankaj.gupta@ionos.com>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	Rik van Riel <riel@surriel.com>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
	Qemu Developers <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Dan Williams <dan.j.williams@intel.com>
Subject: Re: [RFC] virtio_pmem: enable live migration support
Date: Wed, 12 Jan 2022 16:49:32 +0100	[thread overview]
Message-ID: <d0fc0d8e-fe38-1ab2-2d56-23345de783e7@redhat.com> (raw)
In-Reply-To: <CAM9Jb+hvCZoXLx4_xx8KTq4oBts7MCe-ozp5ZuX2yPW6=tyLGQ@mail.gmail.com>

>>
>> I mean, that would be fundamentally broken, because the fsync() would
>> corrupt the file. So I assume in a sane environment, the dst could only
>> have stale clean pagecache pages. And we'd have to get rid of these to
>> re-read everything from file.
> 
> In case of write back cache mode, we could still have stale dirty
> pages at the destination
> host and destination fsync is not the right thing to do. We need to
> invalidate these pages
> (Can we invalidate dirty pages resident in page cache with
> POSIX_FADV_DONTNEED as
> well?) man pages say, we cannot (unless i misunderstood it).
> 

I think you'd have to fsync + POSIX_FADV_DONTNEED. But I am still
confused how we could end up with dirty pagecache pages on the
destination. In my opinion, there should only be clean pagecache pages
-- can someone enlighten me? :)

>>
>> IIRC, an existing mmap of the file on the dst should not really be
>> problematic *as long as* we didn't actually access file content that way
>> and faulted in the pages. So *maybe*, if we do the POSIX_FADV_DONTNEED
>> on the dst before accessing file content via the mmap, there shouldn't
>> be an issue. Unless the mmap itself is already problematic.
> 
> mmap with shared=ON, might result in stale dirty page cache pages?

But only if actually accessing memory, especially writing to it, no?

> 
>>
>> I think we can assume that once QEMU starts on the dst and wants to mmap
>> the file that it's not mapped into any other process yet. vhost-user
>> will only mmap *after* being told from QEMU about the mmap region and
>> the location in GPA.
> 
> maybe we have an old stale dirty page cache page even if there no mmap process
> alive before mmaping virtio-pmem backend file in destination?

But how could that happen in a sane environment? As I said, any
writeback on that file from the destination would actually corrupt the
file that has been used+modified on the source in the meantime, no?


-- 
Thanks,

David / dhildenb



  reply	other threads:[~2022-01-12 15:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-31 12:01 [RFC] virtio_pmem: enable live migration support Pankaj Gupta
2022-01-12 10:36 ` David Hildenbrand
2022-01-12 15:44   ` Pankaj Gupta
2022-01-12 15:49     ` David Hildenbrand [this message]
2022-01-12 16:08       ` Pankaj Gupta
2022-01-12 16:26         ` David Hildenbrand
2022-01-12 16:42           ` Pankaj Gupta
2022-01-12 16:48             ` Pankaj Gupta

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=d0fc0d8e-fe38-1ab2-2d56-23345de783e7@redhat.com \
    --to=david@redhat.com \
    --cc=dan.j.williams@intel.com \
    --cc=dgilbert@redhat.com \
    --cc=mst@redhat.com \
    --cc=pankaj.gupta.linux@gmail.com \
    --cc=pankaj.gupta@ionos.com \
    --cc=qemu-devel@nongnu.org \
    --cc=riel@surriel.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).