From: Chaitanya S Prakash <chaitanyas.prakash@arm.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: Chaitanya S Prakash <chaitanyas.prakash@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: [PATCH 4/5] selftests/mm: Configure nr_hugepages for arm64
Date: Thu, 23 Mar 2023 16:22:42 +0530 [thread overview]
Message-ID: <20230323105243.2807166-5-chaitanyas.prakash@arm.com> (raw)
In-Reply-To: <20230323105243.2807166-1-chaitanyas.prakash@arm.com>
Arm64 has a default hugepage size of 512MB when CONFIG_ARM64_64K_PAGES=y
is enabled. While testing on arm64 platforms having up to 4PB of virtual
address space, a minimum of 6 hugepages were required for all test cases
to pass. Support for this requirement has been added.
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Cc: Shuah Khan <shuah@kernel.org>
Cc: linux-mm@kvack.org
Cc: linux-kselftest@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Chaitanya S Prakash <chaitanyas.prakash@arm.com>
---
tools/testing/selftests/mm/run_vmtests.sh | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/mm/run_vmtests.sh b/tools/testing/selftests/mm/run_vmtests.sh
index eb9823a6959a..7616b3e4a0f0 100644
--- a/tools/testing/selftests/mm/run_vmtests.sh
+++ b/tools/testing/selftests/mm/run_vmtests.sh
@@ -222,8 +222,16 @@ CATEGORY="hugetlb" run_test ./thuge-gen
if [ $VADDR64 -ne 0 ]; then
CATEGORY="hugevm" run_test ./virtual_address_range
- # virtual address 128TB switch test
+ # va high address boundary switch test
+ ARCH_ARM64="arm64"
+ prev_nr_hugepages=$(cat /proc/sys/vm/nr_hugepages)
+ if [ "$ARCH" == "$ARCH_ARM64" ]; then
+ echo 6 > /proc/sys/vm/nr_hugepages
+ fi
CATEGORY="hugevm" run_test ./va_high_addr_switch.sh
+ if [ "$ARCH" == "$ARCH_ARM64" ]; then
+ echo $prev_nr_hugepages > /proc/sys/vm/nr_hugepages
+ fi
fi # VADDR64
# vmalloc stability smoke test
--
2.30.2
next prev parent reply other threads:[~2023-03-23 10:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 10:52 [PATCH 0/5] selftests/mm: Implement support for arm64 on va Chaitanya S Prakash
2023-03-23 10:52 ` [PATCH 1/5] selftests/mm: Add support for arm64 platform on va switch Chaitanya S Prakash
2023-03-23 10:52 ` [PATCH 2/5] selftests/mm: Rename va_128TBswitch to va_high_addr_switch Chaitanya S Prakash
2023-03-23 10:52 ` [PATCH 3/5] selftests/mm: Add platform independent in code comments Chaitanya S Prakash
2023-03-23 10:52 ` Chaitanya S Prakash [this message]
2023-03-23 10:52 ` [PATCH 5/5] selftests/mm: Run hugetlb testcases of va switch Chaitanya S Prakash
2023-03-23 11:14 ` [PATCH 0/5] selftests/mm: Implement support for arm64 on va Kirill A. Shutemov
2023-03-23 11:59 ` Mark Rutland
2023-03-23 21:49 ` Andrew Morton
2023-03-24 10:15 ` Anshuman Khandual
2023-04-05 4:22 ` Chaitanya S Prakash
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=20230323105243.2807166-5-chaitanyas.prakash@arm.com \
--to=chaitanyas.prakash@arm.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@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