From: Ingo Molnar <mingo@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
Shuah Khan <shuah@kernel.org>,
"Chang S. Bae" <chang.seok.bae@intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Binbin Wu <binbin.wu@linux.intel.com>,
angquan yu <angquan21@gmail.com>,
kernel@collabora.com, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] selftests: x86: skip the tests if prerequisites aren't fulfilled
Date: Fri, 29 Mar 2024 08:36:09 +0100 [thread overview]
Message-ID: <ZgZvaUbZIr0qpxK5@gmail.com> (raw)
In-Reply-To: <1d6418a3-67eb-4a39-891a-7d653a26f1fc@linuxfoundation.org>
* Shuah Khan <skhan@linuxfoundation.org> wrote:
> On 3/27/24 05:17, Muhammad Usama Anjum wrote:
> > Skip instead of failing when prerequisite conditions aren't fulfilled,
> > such as invalid xstate values etc. This patch would make the tests show
> > as skip when run by:
> > make -C tools/testing/selftests/ TARGETS=x86 run_tests
> >
> > ...
> > # timeout set to 45
> > # selftests: x86: amx_64
> > # # xstate cpuid: invalid tile data size/offset: 0/0
> > ok 42 selftests: x86: amx_64 # SKIP
> > # timeout set to 45
> > # selftests: x86: lam_64
> > # # Unsupported LAM feature!
> > ok 43 selftests: x86: lam_64 # SKIP
> > ...
> >
> > In amx test, Move away from check_cpuid_xsave() and start using
> > arch_prctl() to find out if amx support is present or not. In the
> > kernels where amx isn't present, arch_prctl returns -EINVAL. Hence it is
> > backward compatible.
> >
> > Reviewed-by: Chang S. Bae <chang.seok.bae@intel.com>
> > Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> > Reviewed-by: Binbin Wu <binbin.wu@linux.intel.com>
> > Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
> > ---
> > Changes since v2:
> > - Update the changelog
> >
>
> Thank you - applied to linux-kselftest next for 6.10-rc1
Please don't, I've applied the patch to tip:x86/cpu with a tidied up
changelog.
Thanks,
Ingo
next prev parent reply other threads:[~2024-03-29 7:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 11:17 [PATCH v3] selftests: x86: skip the tests if prerequisites aren't fulfilled Muhammad Usama Anjum
2024-03-28 18:42 ` Shuah Khan
2024-03-29 7:36 ` Ingo Molnar [this message]
2024-03-29 15:01 ` Shuah Khan
2024-03-30 11:08 ` Ingo Molnar
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=ZgZvaUbZIr0qpxK5@gmail.com \
--to=mingo@kernel.org \
--cc=angquan21@gmail.com \
--cc=binbin.wu@linux.intel.com \
--cc=chang.seok.bae@intel.com \
--cc=kernel@collabora.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=usama.anjum@collabora.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