From: David Hildenbrand <david@redhat.com>
To: Stefan Roesch <shr@devkernel.io>
Cc: kernel-team@fb.com, linux-mm@kvack.org, riel@surriel.com,
mhocko@suse.com, linux-kselftest@vger.kernel.org,
linux-doc@vger.kernel.org, akpm@linux-foundation.org,
hannes@cmpxchg.org, willy@infradead.org,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH v7 3/3] selftests/mm: add new selftests for KSM
Date: Mon, 17 Apr 2023 10:04:10 +0200 [thread overview]
Message-ID: <12011875-f4f4-2aad-4720-326d872bd3e8@redhat.com> (raw)
In-Reply-To: <qvqw8reugp1s.fsf@devbig1114.prn1.facebook.com>
On 14.04.23 22:54, Stefan Roesch wrote:
>
> David Hildenbrand <david@redhat.com> writes:
>
>> Thanks for moving the functional tests. Some more feedback forksm_functional_tests change. Writing tests in the
>> ksft testing framework can be a bit "special".
>>
>>
>> I'm seeing some weird test failures due to
>>
>> prctl(PR_GET_MEMORY_MERGE, 0)
>>
>> Apparently, these go away when using
>>
>> prctl(PR_GET_MEMORY_MERGE, 0, 0, 0, 0)
>>
>
> I changed the test programs to always specify all the 5 parameters.
>
Thanks!
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2023-04-17 8:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 23:31 [PATCH v7 0/3] mm: process/cgroup ksm support Stefan Roesch
2023-04-13 23:31 ` [PATCH v7 1/3] mm: add new api to enable ksm per process Stefan Roesch
2023-04-14 10:24 ` David Hildenbrand
2023-04-14 20:53 ` Stefan Roesch
2023-04-13 23:31 ` [PATCH v7 2/3] mm: add new KSM process and sysfs knobs Stefan Roesch
2023-04-13 23:31 ` [PATCH v7 3/3] selftests/mm: add new selftests for KSM Stefan Roesch
2023-04-14 14:28 ` David Hildenbrand
2023-04-14 20:54 ` Stefan Roesch
2023-04-17 8:04 ` David Hildenbrand [this message]
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=12011875-f4f4-2aad-4720-326d872bd3e8@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=riel@surriel.com \
--cc=shr@devkernel.io \
--cc=willy@infradead.org \
/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