mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sohil Mehta <sohil.mehta@intel.com>
To: "Xin Li (Intel)" <xin@zytor.com>, <linux-kernel@vger.kernel.org>,
	<linux-kselftest@vger.kernel.org>
Cc: <tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
	<dave.hansen@linux.intel.com>, <x86@kernel.org>, <hpa@zytor.com>,
	<shuah@kernel.org>, <andrew.cooper3@citrix.com>
Subject: Re: [PATCH v4 0/2] x86/fred: Prevent single-step upon ERETU completion
Date: Thu, 5 Jun 2025 14:51:43 -0700	[thread overview]
Message-ID: <06e68373-a92b-472e-8fd9-ba548119770c@intel.com> (raw)
In-Reply-To: <8264e653-6570-4c2a-a9a7-c4104da26f76@intel.com>

On 6/5/2025 12:32 PM, Sohil Mehta wrote:
> On 6/5/2025 11:10 AM, Xin Li (Intel) wrote:
> 
>>
>> Xin Li (Intel) (2):
>>   x86/fred/signal: Prevent single-step upon ERETU completion
>>   selftests/x86: Add a test to detect infinite sigtrap handler loop
>>
> 
> I tested the patches on a machine that supports FRED. The results are as
> expected:
> 

Seeing a split lock warning when running the test:
x86/split lock detection: #DB: sigtrap_loop_64/4614 took a bus_lock trap
at address: 0x4011ae

Wanted to get this out sooner for awareness. Will figure out more
details and send out an update.

> FRED on  — no Fix   => FAIL
> FRED off — no Fix   => PASS
> FRED on  — with Fix => PASS
> FRED off — with Fix => PASS
> 
> Tested-by: Sohil Mehta <sohil.mehta@intel.com>
> 
> Though, I haven't tested the 32-bit version of the selftest.
> 
>>  arch/x86/include/asm/sighandling.h         | 22 +++++
>>  arch/x86/kernel/signal_32.c                |  4 +
>>  arch/x86/kernel/signal_64.c                |  4 +
>>  tools/testing/selftests/x86/Makefile       |  2 +-
>>  tools/testing/selftests/x86/sigtrap_loop.c | 97 ++++++++++++++++++++++
>>  5 files changed, 128 insertions(+), 1 deletion(-)
>>  create mode 100644 tools/testing/selftests/x86/sigtrap_loop.c
>>


  reply	other threads:[~2025-06-05 21:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 18:10 Xin Li (Intel)
2025-06-05 18:10 ` [PATCH v4 1/2] x86/fred/signal: " Xin Li (Intel)
2025-06-05 18:46   ` H. Peter Anvin
2025-06-05 18:10 ` [PATCH v4 2/2] selftests/x86: Add a test to detect infinite sigtrap handler loop Xin Li (Intel)
2025-06-05 19:32 ` [PATCH v4 0/2] x86/fred: Prevent single-step upon ERETU completion Sohil Mehta
2025-06-05 21:51   ` Sohil Mehta [this message]
2025-06-12 18:12     ` Xin Li

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=06e68373-a92b-472e-8fd9-ba548119770c@intel.com \
    --to=sohil.mehta@intel.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.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=x86@kernel.org \
    --cc=xin@zytor.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

all inboxes | Powered by JetHome®