From: Chunyu Hu <chuhu@redhat.com>
To: Luiz Capitulino <luizcap@redhat.com>, akpm@linux-foundation.org
Cc: akpm@linux-foundation.org, david@kernel.org, shuah@kernel.org,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, lorenzo.stoakes@oracle.com,
Liam.Howlett@oracle.com, vbabka@suse.cz, rppt@kernel.org,
surenb@google.com, mhocko@suse.com
Subject: Re: [PATCH v2 4/5] selftests/mm: va_high_addr_switch return fail when either test failed
Date: Tue, 23 Dec 2025 10:46:18 +0800 [thread overview]
Message-ID: <aUoCepcpRjuMKoNW@gmail.com> (raw)
In-Reply-To: <469acbcf-22f2-4774-8cf3-7f68c7095c0a@redhat.com>
On Mon, Dec 22, 2025 at 02:36:18PM -0500, Luiz Capitulino wrote:
> On 2025-12-20 23:00, Chunyu Hu wrote:
> > When the first test failed, and the hugetlb test passed, the result would
> > be pass, but we expect a fail. Fix this issue by returning fail if either
> > is not KSFT_PASS.
> >
> > CC: Luiz Capitulino <luizcap@redhat.com>
> > Signed-off-by: Chunyu Hu <chuhu@redhat.com>
> > ---
> > tools/testing/selftests/mm/va_high_addr_switch.c | 10 +++++++---
> > 1 file changed, 7 insertions(+), 3 deletions(-)
> >
> > diff --git a/tools/testing/selftests/mm/va_high_addr_switch.c b/tools/testing/selftests/mm/va_high_addr_switch.c
> > index 02f290a69132..51401e081b20 100644
> > --- a/tools/testing/selftests/mm/va_high_addr_switch.c
> > +++ b/tools/testing/selftests/mm/va_high_addr_switch.c
> > @@ -322,7 +322,7 @@ static int supported_arch(void)
> > int main(int argc, char **argv)
> > {
> > - int ret;
> > + int ret, hugetlb_ret = KSFT_PASS;
> > if (!supported_arch())
> > return KSFT_SKIP;
> > @@ -331,6 +331,10 @@ int main(int argc, char **argv)
> > ret = run_test(testcases, sz_testcases);
> > if (argc == 2 && !strcmp(argv[1], "--run-hugetlb"))
> > - ret = run_test(hugetlb_testcases, sz_hugetlb_testcases);
>
> Maybe you could just have used:
>
> ret |= run_test(hugetlb_testcases, sz_hugetlb_testcases);
Good point. I thought the result code is not encoded by bit, but for
KSFT_PASS and KSFT_FAIL, and KSFT_SKIP, they are per bit.
85 #define KSFT_PASS 0
86 #define KSFT_FAIL 1
87 #define KSFT_XFAIL 2
88 #define KSFT_XPASS 3
89 #define KSFT_SKIP 4
@Andrew, do you think I need to send a v3 for using the simpified way?
if so, send the whole series or the single patch?
>
> But anyways, as this is just testing code:
>
> Reviewed-by: Luiz Capitulino <luizcap@redhat.com>
>
> > - return ret;
> > + hugetlb_ret = run_test(hugetlb_testcases, sz_hugetlb_testcases);
> > +
> > + if (ret == KSFT_PASS && hugetlb_ret == KSFT_PASS)
> > + return KSFT_PASS;
> > + else
> > + return KSFT_FAIL;
> > }
>
next prev parent reply other threads:[~2025-12-23 2:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-21 4:00 [PATCH v2 1/5] selftests/mm: fix va_high_addr_switch.sh return value Chunyu Hu
2025-12-21 4:00 ` [PATCH v2 2/5] selftests/mm: allocate 6 hugepages in va_high_addr_switch.sh Chunyu Hu
2025-12-21 4:00 ` [PATCH v2 3/5] selftests/mm: remove arm64 nr_hugepages setup for va_high_addr_switch test Chunyu Hu
2025-12-21 4:00 ` [PATCH v2 4/5] selftests/mm: va_high_addr_switch return fail when either test failed Chunyu Hu
2025-12-21 4:00 ` [PATCH v2 5/5] selftests/mm: fix comment for check_test_requirements Chunyu Hu
2025-12-22 19:37 ` Luiz Capitulino
2025-12-22 19:36 ` [PATCH v2 4/5] selftests/mm: va_high_addr_switch return fail when either test failed Luiz Capitulino
2025-12-23 2:46 ` Chunyu Hu [this message]
2025-12-23 2:56 ` Andrew Morton
2025-12-23 3:04 ` Chunyu Hu
2025-12-22 19:34 ` [PATCH v2 2/5] selftests/mm: allocate 6 hugepages in va_high_addr_switch.sh Luiz Capitulino
2025-12-21 18:57 ` [PATCH v2 1/5] selftests/mm: fix va_high_addr_switch.sh return value Andrew Morton
2025-12-22 4:32 ` Chunyu Hu
2025-12-23 1:15 ` SeongJae Park
2025-12-23 2:54 ` Chunyu Hu
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=aUoCepcpRjuMKoNW@gmail.com \
--to=chuhu@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=luizcap@redhat.com \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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).