Message-ID: <2c8b7116-56e9-3202-c47e-e42078c85793@collabora.com>
Date:   Wed, 21 Sep 2022 23:26:21 +0500
From:   Muhammad Usama Anjum <usama.anjum@...labora.com>
To:     Andrei Vagin <avagin@...il.com>
Cc:     usama.anjum@...labora.com, Jonathan Corbet <corbet@....net>,
        Alexander Viro <viro@...iv.linux.org.uk>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Shuah Khan <shuah@...nel.org>,
        "open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
        open list <linux-kernel@...r.kernel.org>,
        "open list:PROC FILESYSTEM" <linux-fsdevel@...r.kernel.org>,
        "open list:MEMORY MANAGEMENT" <linux-mm@...ck.org>,
        "open list:KERNEL SELFTEST FRAMEWORK" 
        <linux-kselftest@...r.kernel.org>, kernel@...labora.com,
        Gabriel Krisman Bertazi <krisman@...labora.com>,
        David Hildenbrand <david@...hat.com>,
        Peter Enderborg <peter.enderborg@...y.com>,
        Greg KH <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v3 0/4] Implement IOCTL to get and clear soft dirty PTE

Hi,

Thank you for reviewing.

On 9/19/22 7:58 PM, Andrei Vagin wrote:
>> This ioctl can be used by the CRIU project and other applications which
>> require soft-dirty PTE bit information. The following operations are
>> supported in this ioctl:
>> - Get the pages that are soft-dirty.
> 
> I think this interface doesn't have to be limited by the soft-dirty
> bits only. For example, CRIU needs to know whether file, present and swap bits
> are set or not.
These operations can be performed by pagemap procfs file. Definitely
performing them through IOCTL will be faster. But I'm trying to add a
simple IOCTL by which some specific PTE bit can be read and cleared
atomically. This IOCTL can be extended to include other bits like file,
present and swap bits by keeping the interface simple. The following
mask advice is nice. But if we add that kind of masking, it'll start to
look like a filter on top of pagemap. My intention is to not duplicate
the functionality already provided by the pagemap. One may ask, then why
am I adding "get the soft-dirty pages" functionality? I'm adding it to
complement the get and clear operation. The "get" and "get and clear"
operations with special flag (PAGEMAP_SD_NO_REUSED_REGIONS) can give
results quicker by not splitting the VMAs.

> 
> I mean we should be able to specify for what pages we need to get info
> for. An ioctl argument can have these four fields:
> * required bits (rmask & mask == mask) - all bits from this mask have to be set.
> * any of these bits (amask & mask != 0) - any of these bits is set.
> * exclude masks (emask & mask == 0) = none of these bits are set.
> * return mask - bits that have to be reported to user.
> 
>> - Clear the pages which are soft-dirty.
>> - The optional flag to ignore the VM_SOFTDIRTY and only track per page
>> soft-dirty PTE bit
>>
>> There are two decisions which have been taken about how to get the output
>> from the syscall.
>> - Return offsets of the pages from the start in the vec
> 
> We can conside to return regions that contains pages with the same set
> of bits.
> 
> struct page_region {
> 	void *start;
> 	long size;
> 	u64 bitmap;
> }
> 
> And ioctl returns arrays of page_region-s. I believe it will be more
> compact form for many cases.
Thank you for mentioning this. I'd considered this while development.
But I gave up and used the simple array to return the offsets of the
pages as in the problem I'm trying to solve, the dirty pages may be
present amid non-dirty pages. The range may not be useful in that case.
Also we want to return only a specific number of pages of interest. The
following paragraph explains it.

> 
>> - Stop execution when vec is filled with dirty pages
>> These two arguments doesn't follow the mincore() philosophy where the
>> output array corresponds to the address range in one to one fashion, hence
>> the output buffer length isn't passed and only a flag is set if the page
>> is present. This makes mincore() easy to use with less control. We are
>> passing the size of the output array and putting return data consecutively
>> which is offset of dirty pages from the start. The user can convert these
>> offsets back into the dirty page addresses easily. Suppose, the user want
>> to get first 10 dirty pages from a total memory of 100 pages. He'll
>> allocate output buffer of size 10 and the ioctl will abort after finding the
>> 10 pages. This behaviour is needed to support Windows' getWriteWatch(). The
>> behaviour like mincore() can be achieved by passing output buffer of 100
>> size. This interface can be used for any desired behaviour.
>>
>> [1] https://lore.kernel.org/lkml/54d4c322-cd6e-eefd-b161-2af2b56aae24@collabora.com/
>>
>> Regards,
>> Muhammad Usama Anjum
>>
>> Muhammad Usama Anjum (4):
>>   fs/proc/task_mmu: update functions to clear the soft-dirty PTE bit
>>   fs/proc/task_mmu: Implement IOCTL to get and clear soft dirty PTE bit
>>   selftests: vm: add pagemap ioctl tests
>>   mm: add documentation of the new ioctl on pagemap
>>
>>  Documentation/admin-guide/mm/soft-dirty.rst |  42 +-
>>  fs/proc/task_mmu.c                          | 342 ++++++++++-
>>  include/uapi/linux/fs.h                     |  23 +
>>  tools/include/uapi/linux/fs.h               |  23 +
>>  tools/testing/selftests/vm/.gitignore       |   1 +
>>  tools/testing/selftests/vm/Makefile         |   2 +
>>  tools/testing/selftests/vm/pagemap_ioctl.c  | 649 ++++++++++++++++++++
>>  7 files changed, 1050 insertions(+), 32 deletions(-)
>>  create mode 100644 tools/testing/selftests/vm/pagemap_ioctl.c
>>
>> -- 
>> 2.30.2
>>

-- 
Muhammad Usama Anjum

Powered by blists - more mailing lists