Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: shuah@kernel.org, tglx@linutronix.de,
	dave.hansen@linux.intel.com, bp@alien8.de,
	chang.seok.bae@intel.com
Subject: [PATCH v3 0/3] selftests/x86: AMX-related test improvements
Date: Thu, 30 Mar 2023 16:35:17 -0700	[thread overview]
Message-ID: <20230330233520.21937-1-chang.seok.bae@intel.com> (raw)
In-Reply-To: <20220711170330.27138-1-chang.seok.bae@intel.com>

Dear maintainers,

Let me follow up on the last posting [5] with these two small changes:
* Clean up unused code in the AMX test.
* Fix the subsystem name in the patch1 subject.

Here is a summary of the included test code changes:

* With the STRICT_SIGALTSTACK_SIZE option [1,2], the kernel's altstack
  check becomes stringent. The x86 sigaltstack test is ignorant about
  this. Adjust the test. This check was established [3] to ensure
  every AMX task's altstack is sufficient (regardless of that option)
  [4].

* The AMX test wrongly fails on non-AMX machines. Fix the code to skip
  the test instead.

* It also has some unused code. Remove them where at this.

The series is available in this repository:
  git://github.com/intel/amx-linux.git selftest

Thanks,
Chang

[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/x86/Kconfig#n2467
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/admin-guide/kernel-parameters.txt#n6038
[3] 3aac3ebea08f ("x86/signal: Implement sigaltstack size validation")
[4] 4b7ca609a33d ("x86/signal: Use fpu::__state_user_size for sigalt stack validation")
[5] https://lore.kernel.org/lkml/20220711170330.27138-1-chang.seok.bae@intel.com/


Chang S. Bae (3):
  selftests/x86/sigaltstack: Adjust the test to the kernel's altstack
    check
  selftests/x86/amx: Fix the test to avoid failure when AMX is
    unavailable
  selftests/x86/amx: Remove unneeded code

 tools/testing/selftests/x86/amx.c         | 51 +++++------------------
 tools/testing/selftests/x86/sigaltstack.c | 12 +++++-
 2 files changed, 21 insertions(+), 42 deletions(-)


base-commit: 197b6b60ae7bc51dd0814953c562833143b292aa
-- 
2.17.1


  parent reply	other threads:[~2023-03-30 23:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 17:03 [PATCH v2 0/2] selftests/x86: AMX-related test improvements Chang S. Bae
2022-07-11 17:03 ` [PATCH v2 1/2] selftests/x86/signal: Adjust the test to the kernel's altstack check Chang S. Bae
2022-07-11 17:03 ` [PATCH v2 2/2] selftests/x86/amx: Fix the test to avoid failure when AMX is unavailable Chang S. Bae
2023-03-30 23:35 ` Chang S. Bae [this message]
2023-03-30 23:35   ` [PATCH v3 1/3] selftests/x86/sigaltstack: Adjust the test to the kernel's altstack check Chang S. Bae
2023-03-30 23:35   ` [PATCH v3 2/3] selftests/x86/amx: Fix the test to avoid failure when AMX is unavailable Chang S. Bae
2023-03-30 23:35   ` [PATCH v3 3/3] selftests/x86/amx: Remove unneeded code Chang S. Bae

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=20230330233520.21937-1-chang.seok.bae@intel.com \
    --to=chang.seok.bae@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.de \
    /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