Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Slawomir Rosek <srosek@google.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	 Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org,  "H . Peter Anvin" <hpa@zytor.com>,
	Shuah Khan <shuah@kernel.org>
Cc: Betty Zhou <bettyzhou@google.com>, Wake Liu <wakel@google.com>,
	 Kazuhiro Inaba <kinaba@google.com>, Jeff Xu <jeffxu@google.com>,
	 Alistair Delva <adelva@google.com>,
	linux-kernel@vger.kernel.org,  linux-kselftest@vger.kernel.org,
	Slawomir Rosek <srosek@google.com>
Subject: [PATCH v1 0/2] selftests/x86: Skip int80 if not supported
Date: Wed, 17 Dec 2025 13:59:30 +0000	[thread overview]
Message-ID: <20251217135932.3153847-1-srosek@google.com> (raw)

The IA32 Emulation support can be either removed from the kernel,
disabled by default or disabled at runtime. Some of x86 selftests
are crashing for all of above thus is_32bit_syscall_supported()
helper is added to skip int80 syscalls if they are not supported.

Slawomir Rosek (2):
  selftests/x86/ldt_gdt: Skip int80 if not supported
  selftests/x86/ptrace_syscall: Skip int80 if not supported

 tools/testing/selftests/x86/ldt_gdt.c        | 21 +++++++++++++++++++-
 tools/testing/selftests/x86/ptrace_syscall.c | 20 +++++++++++++++++--
 2 files changed, 38 insertions(+), 3 deletions(-)

-- 
2.52.0.305.g3fc767764a-goog


             reply	other threads:[~2025-12-17 13:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-17 13:59 Slawomir Rosek [this message]
2025-12-17 13:59 ` [PATCH v1 1/2] selftests/x86/ldt_gdt: Skip int80 if not supported Slawomir Rosek
2026-01-23 16:54   ` Borislav Petkov
2026-01-23 17:07     ` Dave Hansen
2026-01-24  1:01     ` H. Peter Anvin
2026-02-13 17:26       ` Sławomir Rosek
2025-12-17 13:59 ` [PATCH v1 2/2] selftests/x86/ptrace_syscall: " Slawomir Rosek
2026-01-12 11:23 ` [PATCH v1 0/2] selftests/x86: " Sławomir Rosek
2026-01-24  1:18   ` H. Peter Anvin

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=20251217135932.3153847-1-srosek@google.com \
    --to=srosek@google.com \
    --cc=adelva@google.com \
    --cc=bettyzhou@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jeffxu@google.com \
    --cc=kinaba@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wakel@google.com \
    --cc=x86@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