From: "H. Peter Anvin" <hpa@zytor.com>
To: "Sławomir Rosek" <srosek@google.com>,
"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, "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
Subject: Re: [PATCH v1 0/2] selftests/x86: Skip int80 if not supported
Date: Fri, 23 Jan 2026 17:18:20 -0800 [thread overview]
Message-ID: <e5fa1ad5-afa0-4ba2-a60a-d43a2c6e86e5@zytor.com> (raw)
In-Reply-To: <CAF3aWvHbSgDYxgFHF05FkEGQncMUXsuwMPDBCcoXUGoQgESuEg@mail.gmail.com>
On 2026-01-12 03:23, Sławomir Rosek wrote:
> On Wed, Dec 17, 2025 at 2:59 PM Slawomir Rosek <srosek@google.com> wrote:
>>
>> 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
>
> Hi all,
>
> Just a gentle reminder, it would be really great if someone could take
> a look. Thanks in advance.
I think grepping the configuration and cmdline files is definitely not the way
to go.
For a solution that works on existing kernels, trapping SIGSEGV and calling
int $0x80 is probably the best way to probe.
-hpa
prev parent reply other threads:[~2026-01-24 1:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 13:59 [PATCH v1 0/2] selftests/x86: Skip int80 if not supported Slawomir Rosek
2025-12-17 13:59 ` [PATCH v1 1/2] selftests/x86/ldt_gdt: " 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 [this message]
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=e5fa1ad5-afa0-4ba2-a60a-d43a2c6e86e5@zytor.com \
--to=hpa@zytor.com \
--cc=adelva@google.com \
--cc=bettyzhou@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.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=srosek@google.com \
--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