From: Mike Kravetz <mike.kravetz@oracle.com>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kselftest@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [GIT PULL] Kselftest update for 4.11-rc1
Date: Sun, 26 Feb 2017 12:40:36 -0800 [thread overview]
Message-ID: <06e6875c-18bd-ccac-366d-b796d3200766@oracle.com> (raw)
In-Reply-To: <20170226113744.GA17152@rapoport-lnx>
On 02/26/2017 03:37 AM, Mike Rapoport wrote:
> On Sat, Feb 25, 2017 at 03:42:55PM -0800, Linus Torvalds wrote:
>> On Fri, Feb 24, 2017 at 1:09 PM, Shuah Khan <shuahkh@osg.samsung.com> wrote:
>>>
>>> Stephen saw a conflict during kselftest merge with next
>> [..]
>>
>> There was also a conflict with some of Andrew's new userfaultfd tests.
>>
>> I'm not at all sure I merged that correctly, although I tried to make
>> the resolution at least look sane. The odd thing about those new tests
>> is that it's all the same source file, except built with different
>> compile-time defines to be different test binaries.
>>
>> I didn't find any way to do that with any standard selftest makefile
>> magic, so I just did the build rules by hand.
>>
>> Somebody should actually verify that it does the right thing, please..
>> Adding the two Mike's that did those test additions to the participant
>> list.
>
> The userfaultfd_* tests are built and they are working just fine.
Thanks Mike, I also verified that the tests build/run as they should.
> Maybe it's worth adding userfaultfd_{hugetlb,shmem}.c which will define the
> required defines and include userfaultfd.c?
> Than we can get away with only specifying LDFLAGS += -lpthread in the
> Makefile.
I started the current scheme when adding support for hugetlbfs, which I
thought would be a 'one off'. Did not know about the shmem work that was
in progress.
Another option is to only have a single userfaultfd executable and pass
an option (anon, hugetlb, shmem ...) that indicates the type of pages/mapping
to test.
In any case, the makefile modifications work so this is not urgent. Perhaps
we can discuss with Andrea and figure out what would be the best scheme
moving forward.
--
Mike Kravetz
next prev parent reply other threads:[~2017-02-26 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 21:09 Shuah Khan
2017-02-25 23:42 ` Linus Torvalds
2017-02-26 11:37 ` Mike Rapoport
2017-02-26 20:40 ` Mike Kravetz [this message]
2017-02-27 22:14 ` Andrea Arcangeli
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=06e6875c-18bd-ccac-366d-b796d3200766@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=aarcange@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=shuahkh@osg.samsung.com \
--cc=torvalds@linux-foundation.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
Powered by JetHome