From: David Hildenbrand <david@redhat.com>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: selftests/vm madv_populate.c test
Date: Fri, 15 Oct 2021 17:47:03 +0200 [thread overview]
Message-ID: <b99b5960-b1ec-b968-1d9c-d125a23c59fe@redhat.com> (raw)
In-Reply-To: <3a06d58e-7301-6fbc-a305-d9f7c7220843@linuxfoundation.org>
On 15.10.21 17:45, Shuah Khan wrote:
> On 9/18/21 1:41 AM, David Hildenbrand wrote:
>> On 18.09.21 00:45, Shuah Khan wrote:
>>> Hi David,
>>>
>>> I am running into the following warning when try to build this test:
>>>
>>> madv_populate.c:334:2: warning: #warning "missing MADV_POPULATE_READ or MADV_POPULATE_WRITE definition" [-Wcpp]
>>> 334 | #warning "missing MADV_POPULATE_READ or MADV_POPULATE_WRITE definition"
>>> | ^~~~~~~
>>>
>>>
>>> I see that the following handling is in place. However there is no
>>> other information to explain why the check is necessary.
>>>
>>> #if defined(MADV_POPULATE_READ) && defined(MADV_POPULATE_WRITE)
>>>
>>> #else /* defined(MADV_POPULATE_READ) && defined(MADV_POPULATE_WRITE) */
>>>
>>> #warning "missing MADV_POPULATE_READ or MADV_POPULATE_WRITE definition"
>>>
>>> I do see these defined in:
>>>
>>> include/uapi/asm-generic/mman-common.h:#define MADV_POPULATE_READ 22
>>> include/uapi/asm-generic/mman-common.h:#define MADV_POPULATE_WRITE 23
>>>
>>> Is this the case of missing include from madv_populate.c?
>>
>> Hi Shuan,
>>
>> note that we're including "#include <sys/mman.h>", which in my
>> understanding maps to the version installed on your system instead
>> of the one in our build environment.ing.
>>
>> So as soon as you have a proper kernel + the proper headers installed
>> and try to build, it would pick up MADV_POPULATE_READ and
>> MADV_POPULATE_WRITE from the updated headers. That makes sense: you
>> annot run any MADV_POPULATE_READ/MADV_POPULATE_WRITE tests on a kernel
>> that doesn't support it.
>>
>> See vm/userfaultfd.c where we do something similar.
>>
>
> Kselftest is for testing the kernel with kernel headers. That is the
> reason why there is the dependency on header install.
>
>>
>> As soon as we have a proper environment, it seems to work just fine:
>>
>> Linux vm-0 5.15.0-0.rc1.20210915git3ca706c189db.13.fc36.x86_64 #1 SMP Thu Sep 16 11:32:54 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
>> [root@vm-0 linux]# cat /etc/redhat-release
>> Fedora release 36 (Rawhide)
>
> This is a distro release. We don't want to have dependency on headers
> from the distro to run selftests. Hope this makes sense.
>
> I still see this on my test system running Linux 5.15-rc5.
Did you also install Linux headers? I assume no, correct?
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-10-15 15:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 22:45 Shuah Khan
2021-09-18 7:41 ` David Hildenbrand
2021-10-15 15:45 ` Shuah Khan
2021-10-15 15:47 ` David Hildenbrand [this message]
2021-10-15 16:06 ` David Hildenbrand
2021-10-15 16:15 ` David Hildenbrand
2021-10-15 16:19 ` David Hildenbrand
2021-10-15 16:25 ` Shuah Khan
2021-10-15 16:28 ` David Hildenbrand
2021-10-15 16:34 ` David Hildenbrand
2021-10-15 16:40 ` Shuah Khan
2021-10-15 16:46 ` David Hildenbrand
2021-10-15 16:21 ` Shuah Khan
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=b99b5960-b1ec-b968-1d9c-d125a23c59fe@redhat.com \
--to=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®