From: Eric B Munson <emunson@akamai.com>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [RESEND PATCH 3/3] Add tests for lock on fault
Date: Tue, 2 Jun 2015 12:05:46 -0400 [thread overview]
Message-ID: <20150602160545.GA2253@akamai.com> (raw)
In-Reply-To: <556DCB05.1010102@osg.samsung.com>
[-- Attachment #1: Type: text/plain, Size: 2136 bytes --]
On Tue, 02 Jun 2015, Shuah Khan wrote:
> On 05/29/2015 08:13 AM, Eric B Munson wrote:
> > Test the mmap() flag, the mlockall() flag, and ensure that mlock limits
> > are respected. Note that the limit test needs to be run a normal user.
> >
> > Signed-off-by: Eric B Munson <emunson@akamai.com>
> > Cc: Shuah Khan <shuahkh@osg.samsung.com>
> > Cc: linux-mm@kvack.org
> > Cc: linux-kernel@vger.kernel.org
> > Cc: linux-api@vger.kernel.org
> > ---
> > tools/testing/selftests/vm/Makefile | 8 +-
> > tools/testing/selftests/vm/lock-on-fault.c | 145 ++++++++++++++++++++++++++++
> > tools/testing/selftests/vm/on-fault-limit.c | 47 +++++++++
> > tools/testing/selftests/vm/run_vmtests | 23 +++++
> > 4 files changed, 222 insertions(+), 1 deletion(-)
> > create mode 100644 tools/testing/selftests/vm/lock-on-fault.c
> > create mode 100644 tools/testing/selftests/vm/on-fault-limit.c
> >
> > diff --git a/tools/testing/selftests/vm/Makefile b/tools/testing/selftests/vm/Makefile
> > index a5ce953..32f3d20 100644
> > --- a/tools/testing/selftests/vm/Makefile
> > +++ b/tools/testing/selftests/vm/Makefile
> > @@ -1,7 +1,13 @@
> > # Makefile for vm selftests
> >
> > CFLAGS = -Wall
> > -BINARIES = hugepage-mmap hugepage-shm map_hugetlb thuge-gen hugetlbfstest
> > +BINARIES = hugepage-mmap
> > +BINARIES += hugepage-shm
> > +BINARIES += hugetlbfstest
> > +BINARIES += lock-on-fault
> > +BINARIES += map_hugetlb
> > +BINARIES += on-fault-limit
> > +BINARIES += thuge-gen
> > BINARIES += transhuge-stress
> >
> > all: $(BINARIES)
> > diff --git a/tools/testing/selftests/vm/lock-on-fault.c b/tools/testing/selftests/vm/lock-on-fault.c
> > new file mode 100644
> > index 0000000..e6a9688
>
> Hi Eric,
>
> Could you please make sure make kselftest run from kernel main
> Makefile works and tools/testing/selftests/kselftest_install.sh
> works. For now you have to be in tools/testing/selftests to run
> kselftest_install.sh
>
I am working on getting V2 ready, I will ensure these work and make any
necessary adjustments before sending V2 out.
Eric
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-02 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 14:13 [RESEND PATCH 0/3] Allow user to request memory to be locked on page fault Eric B Munson
2015-05-29 14:13 ` [RESEND PATCH 1/3] Add flag to request pages are locked after " Eric B Munson
2015-05-29 14:13 ` [RESEND PATCH 2/3] Add mlockall flag for locking pages on fault Eric B Munson
2015-05-29 14:13 ` [RESEND PATCH 3/3] Add tests for lock " Eric B Munson
2015-06-02 15:25 ` Shuah Khan
2015-06-02 16:05 ` Eric B Munson [this message]
2015-06-01 22:27 ` [RESEND PATCH 0/3] Allow user to request memory to be locked on page fault Andrew Morton
2015-06-02 14:25 ` Eric B Munson
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=20150602160545.GA2253@akamai.com \
--to=emunson@akamai.com \
--cc=akpm@linux-foundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuahkh@osg.samsung.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;
as well as URLs for NNTP newsgroup(s).