Hi,
Andrew had already accepted the patch. I'll send an iteration.
On 2/26/22 5:35 AM, Shuah Khan wrote:
>> +#define PAGEMAP_PATH "/proc/self/pagemap"
>
> Why is this names PATH - it is the file name right?
I'll update the names of the macros.
>> +
>> +int clear_refs;
>> +int pagemap;
>> +
>
> Get rid of these globals and pass these in - please find name
> that clearly indicates them as fds
>
I'll update their names to indicate fds. This is a standalone test
application. Shouldn't the usage of global variables be fine?
>> +static int check_page(char *start, int page_num, int clear)
>> +{
>> + unsigned long pfn = (unsigned long)start / pagesize;
>> + uint64_t entry;
>> + int ret;
>> +
>> + ret = pread(pagemap, &entry, sizeof(entry), (pfn + page_num) *
>> sizeof(entry));
>> + if (ret != sizeof(entry))
>> + ksft_exit_fail_msg("reading pagemap failed\n");
>> + if (clear)
>> + clear_all_refs();
>> +
>> + return ((entry >> 55) & 1);
>
> Add a define for 55 insead of hardcoding with a meaningful name
> that describes what this value is.
>
Sure.
>> +}
>> +
>> +static void test_simple(void)
>> +{
>> + int i;
>> + char *map;
>> +
>> + map = aligned_alloc(pagesize, mmap_size);
>> + if (!map)
>> + ksft_exit_fail_msg("mmap failed\n");
>> +
>> + clear_all_refs();
>
> If clear_all_refs() fails and exits, when does map get freed?
I'll fix this.
>> +/*
>> + * read_pmd_pagesize(), check_for_pattern() and check_huge() adapted
>> + * from 'tools/testing/selftest/vm/split_huge_page_test.c'
>
> Don't use the full path here - just use the file name
I'll update the comment.
>> +
>> +int main(int argc, char **argv)
>> +{
>> + ksft_print_header();
>> + ksft_set_plan(5);
>> +
>> + pagemap = open(PAGEMAP_PATH, O_RDONLY);
>> + if (pagemap < 0)
>> + ksft_exit_fail_msg("Failed to open %s\n", PAGEMAP_PATH);
>
> Can non-root user open this file? If not, when non-root user fails to
> open, it is a skip not fail
Yes, non-root user can open this file. I'll check the usage of skip
macros as well.
>> + test_simple();
>> + test_vma_reuse();
>> + test_hugepage();
>
> What happens when these tests fail?
They are independent. Each of them marks the test pass or fail on its
own. If one of them fails, others will keep on executing next.
>> +
>> + return ksft_exit_pass();
>> +}
>>
>
> Where do CLEAR_REFS_PATH etc. get closed. Please take a look
> at the error paths carefully. I would like to see the output for
> this test. Please include it in the change log.
I'll update and include the output as well.
> thanks,
> -- Shuah
