From: Andre Przywara <andre.przywara@arm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Shuah Khan <shuahkh@osg.samsung.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pavel Emelyanov <xemul@parallels.com>,
Will Deacon <Will.Deacon@arm.com>
Subject: Re: [PATCH 2/2] selftests/userfaultfd: improve syscall number definition
Date: Wed, 23 Sep 2015 14:11:33 +0100 [thread overview]
Message-ID: <5602A505.8090804@arm.com> (raw)
In-Reply-To: <1443002109.9279.1.camel@ellerman.id.au>
Hi Michael,
On 23/09/15 10:55, Michael Ellerman wrote:
> On Tue, 2015-09-22 at 18:15 +0100, Andre Przywara wrote:
>> On 22/09/15 15:06, Andrea Arcangeli wrote:
>>> Andre, could you see if linux-next (which includes -mm) works for you
>>> by just running "cd tools/testing/selftests/vm/ && make"? If there's
>>> any further change required could you diff it against linux-next?
>>
>> This doesn't compile now for me, because it looks into
>> /usr/include/asm/unistd.h, which I keep to the distribution copy of it.
>> Also linux/userfaultfd.h is missing, because it's brand new.
> ...
>> I guess the right solution would be to hack the Makefile to set the
>> include path to the kernel's copy of include/uapi, though I am not sure
>> this works cleanly for different architectures and separate build
>> directories. I will give this a try ...
>
> Not that's not the right solution.
>
> The right solution is to export the kernel headers, the Makefile will pick them
> up (at least in linux-next):
Actually that was I was hoping for, I just missed the possibility of
headers_install to put the files back into the kernel tree (I usually
use it with INSTALL_HDR_PATH for packaging).
>
> $ cd linux
> $ make headers_install
> $ ls usr/include/
> asm/ asm-generic/ drm/ linux/ misc/ mtd/ rdma/ scsi/ sound/ uapi/ video/ xen/
> $ make -C tools/testing/selftests TARGETS=vm
> ...
> $ ls tools/testing/selftests/vm/userfaultfd
> tools/testing/selftests/vm/userfaultfd*
Yes, that works. Now I have just to figure out how to arrange this with
out-of-tree build directories.
Cheers,
Andre.
next prev parent reply other threads:[~2015-09-23 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 10:45 [PATCH 0/2] selftests/userfaultfd: fix build Andre Przywara
2015-09-22 10:45 ` [PATCH 1/2] userfaultfd: remove kernel header include from uapi header Andre Przywara
2015-09-22 10:45 ` [PATCH 2/2] selftests/userfaultfd: improve syscall number definition Andre Przywara
2015-09-22 13:49 ` Shuah Khan
2015-09-22 14:06 ` Andrea Arcangeli
2015-09-22 17:15 ` Andre Przywara
2015-09-23 9:55 ` Michael Ellerman
2015-09-23 13:11 ` Andre Przywara [this message]
2015-09-24 2:04 ` Michael Ellerman
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=5602A505.8090804@arm.com \
--to=andre.przywara@arm.com \
--cc=Will.Deacon@arm.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=shuahkh@osg.samsung.com \
--cc=xemul@parallels.com \
/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
Powered by JetHome