[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v1 1/4] softmmu/physmem: Warn with ram_block_discard_range()
From: |
Peter Xu |
Subject: |
Re: [PATCH v1 1/4] softmmu/physmem: Warn with ram_block_discard_range() on MAP_PRIVATE file mapping |
Date: |
Thu, 22 Jun 2023 10:54:34 -0400 |
On Thu, Jun 22, 2023 at 03:10:47PM +0200, David Hildenbrand wrote:
> Maybe ... depends also on the uffd semantics as in 3).
UFFDIO_COPY|ZEROPAGE bypasses page cache for private file mappings, afaict.
We'll still got a limit on the inode size (so we can't COPY|ZEROPAGE over
that offset of vma) but the rest should be all fine.
Feel free to have a quick skim over 5b51072e97d5 ("userfaultfd: shmem:
allocate anonymous memory for MAP_PRIVATE shmem").
Thanks,
--
Peter Xu
[PATCH v1 4/4] virtio-mem: Support "x-ignore-shared" migration, David Hildenbrand, 2023/06/20
[PATCH v1 2/4] virtio-mem: Skip most of virtio_mem_unplug_all() without plugged memory, David Hildenbrand, 2023/06/20