From: Ingo Molnar <mingo@kernel.org>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: akpm@linux-foundation.org,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
"H . Peter Anvin" <hpa@zytor.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH v4] selftest/vm: Move the 128 TB mmap boundary test to the generic VM directory
Date: Mon, 8 Jan 2018 17:14:35 +0100 [thread overview]
Message-ID: <20180108161435.e3jjrttk57lib63a@gmail.com> (raw)
In-Reply-To: <20171123165226.32582-1-aneesh.kumar@linux.vnet.ibm.com>
* Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> wrote:
> Architectures like ppc64 do support mmap hint addr based large address space
> selection. This test can be run on those architectures too. Move the test to
> selftest/vm so that other archs can use the same.
>
> We also add a few new test scenarios in this patch. We do test few boundary
> condition before we do a high address mmap. ppc64 use the addr limit to validate
> addr in the fault path. We had bugs in this area w.r.t slb fault handling
> before we updated the addr limit.
>
> We also touch the allocated space to make sure we don't have any bugs in the
> fault handling path.
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> ---
> Changes from V2:
> * Rebase on top of -tip tree.
> * update the correct license
> * use memset to touch the full mmap range.
>
> tools/testing/selftests/vm/Makefile | 1 +
> tools/testing/selftests/vm/run_vmtests | 11 ++
> tools/testing/selftests/vm/va_128TBswitch.c | 297 ++++++++++++++++++++++++++++
> tools/testing/selftests/x86/5lvl.c | 177 -----------------
> 4 files changed, 309 insertions(+), 177 deletions(-)
> create mode 100644 tools/testing/selftests/vm/va_128TBswitch.c
> delete mode 100644 tools/testing/selftests/x86/5lvl.c
This will now apply (almost) cleanly to Linus's latest tree - I fixed up a trivial
conflict in selftests/vm/Makefile.
Note that I also improved the changelog.
Note #2: I'd suggest this patch to be split into two patches:
- patch 1 moves the testcase to vm/selftests
- patch 2 does all the additional improvements
because this way all the deltas will be much easier to see and review.
Thanks,
Ingo
=================>
next prev parent reply other threads:[~2018-01-08 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 16:52 [PATCH V3] selftest/vm: Move 128TB mmap boundary test to generic directory Aneesh Kumar K.V
2018-01-08 16:14 ` Ingo Molnar [this message]
2018-01-08 16:51 ` [PATCH v4] selftest/vm: Move the 128 TB mmap boundary test to the generic VM directory Philippe Ombredanne
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=20180108161435.e3jjrttk57lib63a@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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