mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sohil Mehta <sohil.mehta@intel.com>
To: Binbin Wu <binbin.wu@linux.intel.com>
Cc: <kvm@vger.kernel.org>, <x86@kernel.org>,
	Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H . Peter Anvin" <hpa@zytor.com>, Shuah Khan <shuah@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"Chang S . Bae" <chang.seok.bae@intel.com>,
	Kai Huang <kai.huang@intel.com>,
	Fuad Tabba <fuad.tabba@linux.dev>, Chao Gao <chao.gao@intel.com>,
	Yosry Ahmed <yosry@kernel.org>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>,
	David Matlack <dmatlack@google.com>,
	Bala-Vignesh-Reddy <reddybalavignesh9979@gmail.com>,
	Kishen Maloor <kishen.maloor@intel.com>,
	Rick Edgecombe <rick.p.edgecombe@intel.com>,
	<linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v4 7/7] selftests/x86: Add a userspace test for LASS enforcement
Date: Mon, 14 Sep 2026 20:22:30 -0700	[thread overview]
Message-ID: <c77b9400-f896-4582-98af-fd3399a39443@intel.com> (raw)
In-Reply-To: <e6f853c7-ec9f-4e1a-bf7a-3b97ff84d3aa@linux.intel.com>


> 
>> +int main(void)
>> +{
>> +	ksft_print_header();
>> +
>> +	if (!is_lass_active())
>> +		ksft_exit_skip("LASS is not enabled\n");
>> +
>> +	ksft_set_plan(TOTAL_TESTS);
>> +
>> +	sethandler(SIGSEGV, fault_handler, 0);
>> +	/* Only to report a #SS; LASS shouldn't cause one here. */
>> +	sethandler(SIGBUS, fault_handler, 0);
> 
> So the purpose is that if there is an unexpected #SS, fails the test instead of
> killing it, right?
> 

Sorry, I missed this question earlier. Yes, the goal is to catch the
SIGBUS and report a failure.

I think it isn't worth keeping in the first place. My initial plan was
to trigger an LASS violation #SS. But, it turned out to be much harder
to trigger. I'll probably remove it because it creates a distraction.

>> +
>> +	ksft_print_msg("Accessing the kernel address 0x%lx from userspace\n",
>> +		       (unsigned long)KERNEL_ADDR);
>> +	test_kernel_read();
>> +	test_kernel_write();
>> +	test_kernel_fetch();
>> +
>> +	clearhandler(SIGBUS);
>> +	clearhandler(SIGSEGV);
>> +
>> +	ksft_finished();
>> +}
> 


  reply	other threads:[~2026-09-15  3:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06  1:15 [PATCH v4 0/7] KVM: x86: Add LASS virtualization support Sohil Mehta
2026-08-06  1:15 ` [PATCH v4 1/7] KVM: x86: Add an emulator flag to differentiate branch targets from fetches Sohil Mehta
2026-08-06  1:15 ` [PATCH v4 2/7] KVM: x86: Use linear_read_system() to read the TSS I/O bitmap Sohil Mehta
2026-08-19  3:19   ` Binbin Wu
2026-08-19  5:03     ` Sohil Mehta
2026-08-19  5:21       ` H. Peter Anvin
2026-08-19  5:26       ` Binbin Wu
2026-08-06  1:15 ` [PATCH v4 3/7] KVM: x86: Add LASS violation checks during instruction emulation Sohil Mehta
2026-08-19  5:58   ` Binbin Wu
2026-08-06  1:15 ` [PATCH v4 4/7] KVM: VMX: Implement LASS violation check Sohil Mehta
2026-08-19  8:49   ` Binbin Wu
2026-09-14 17:43   ` Chang S. Bae
2026-09-15  5:10     ` Sohil Mehta
2026-09-15 14:04       ` Sean Christopherson
2026-09-16  0:12         ` Sohil Mehta
2026-09-16 18:38           ` Sean Christopherson
2026-09-16 21:49             ` Sohil Mehta
2026-08-06  1:15 ` [PATCH v4 5/7] KVM: x86: Virtualize LASS and advertise support to userspace Sohil Mehta
2026-08-19  9:01   ` Binbin Wu
2026-08-06  1:15 ` [PATCH v4 6/7] KVM: selftests: Add coverage for LASS CPUID and CR4 handling Sohil Mehta
2026-08-20  6:01   ` Binbin Wu
2026-08-06  1:15 ` [PATCH v4 7/7] selftests/x86: Add a userspace test for LASS enforcement Sohil Mehta
2026-08-20  6:36   ` Binbin Wu
2026-09-15  3:22     ` Sohil Mehta [this message]
2026-09-14 18:21   ` Chang S. Bae
2026-09-15  3:16     ` Sohil Mehta
2026-08-26  3:50 ` [PATCH v4 0/7] KVM: x86: Add LASS virtualization support Kishen Maloor
2026-08-27  3:18 ` Chen, Farrah

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=c77b9400-f896-4582-98af-fd3399a39443@intel.com \
    --to=sohil.mehta@intel.com \
    --cc=binbin.wu@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=chang.seok.bae@intel.com \
    --cc=chao.gao@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dmatlack@google.com \
    --cc=fuad.tabba@linux.dev \
    --cc=hpa@zytor.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kai.huang@intel.com \
    --cc=kishen.maloor@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=reddybalavignesh9979@gmail.com \
    --cc=rick.p.edgecombe@intel.com \
    --cc=seanjc@google.com \
    --cc=shuah@kernel.org \
    --cc=tglx@kernel.org \
    --cc=x86@kernel.org \
    --cc=yosry@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

all inboxes | Powered by JetHome®