From: Andrew Morton <akpm@linux-foundation.org>
To: Audra Mitchell <audra@redhat.com>
Cc: shuah@kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
raquini@redhat.com, Adam Sindelar <adam@wowsignal.io>
Subject: Re: [PATCH] selftests/mm: Update va_high_addr_switch.sh to check CPU for la57 flag
Date: Sun, 21 Jan 2024 14:31:53 -0800 [thread overview]
Message-ID: <20240121143153.5dcfe26dea53ba0e896dbf85@linux-foundation.org> (raw)
In-Reply-To: <20240119205801.62769-1-audra@redhat.com>
On Fri, 19 Jan 2024 15:58:01 -0500 Audra Mitchell <audra@redhat.com> wrote:
> In order for the page table level 5 to be in use, the CPU must have the
> setting enabled in addition to the CONFIG option. Check for the flag to be
> set to avoid false test failures on systems that do not have this cpu flag
> set.
>
Thanks.
I'll add
Cc: Adam Sindelar <adam@wowsignal.io>
Fixes: 4f2930c6718a ("selftests/vm: only run 128TBswitch with 5-level paging")
Cc: <stable@vger.kernel.org>
A more complete description of these "test failures" would be helpful
please.
> --- a/tools/testing/selftests/mm/va_high_addr_switch.sh
> +++ b/tools/testing/selftests/mm/va_high_addr_switch.sh
> @@ -29,9 +29,15 @@ check_supported_x86_64()
> # See man 1 gzip under '-f'.
> local pg_table_levels=$(gzip -dcfq "${config}" | grep PGTABLE_LEVELS | cut -d'=' -f 2)
>
> + local cpu_supports_pl5=$(awk '/^flags/ {if (/la57/) {print 0;}
> + else {print 1}; exit}' /proc/cpuinfo 2>/dev/null)
> +
> if [[ "${pg_table_levels}" -lt 5 ]]; then
> echo "$0: PGTABLE_LEVELS=${pg_table_levels}, must be >= 5 to run this test"
> exit $ksft_skip
> + elif [[ "${cpu_supports_pl5}" -ne 0 ]]; then
> + echo "$0: CPU does not have the necessary la57 flag to support page table level 5"
> + exit $ksft_skip
> fi
> }
>
> --
> 2.43.0
next prev parent reply other threads:[~2024-01-21 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 20:58 [PATCH] selftests/mm: Update va_high_addr_switch.sh to check CPU for la57 flag Audra Mitchell
2024-01-21 22:31 ` Andrew Morton [this message]
2024-01-24 13:39 ` Audra Mitchell
2024-01-26 1:43 ` Andrew Morton
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=20240121143153.5dcfe26dea53ba0e896dbf85@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adam@wowsignal.io \
--cc=audra@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=raquini@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).