[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <93510641-9032-4612-9424-c048145e883e@intel.com>
Date: Thu, 23 May 2024 08:36:19 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Alexandre Chartre <alexandre.chartre@...cle.com>, x86@...nel.org,
kvm@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, daniel.sneddon@...ux.intel.com,
pawan.kumar.gupta@...ux.intel.com, tglx@...utronix.de,
konrad.wilk@...cle.com, peterz@...radead.org, gregkh@...uxfoundation.org,
seanjc@...gle.com, andrew.cooper3@...rix.com, dave.hansen@...ux.intel.com,
nik.borisov@...e.com, kpsingh@...nel.org, longman@...hat.com, bp@...en8.de,
pbonzini@...hat.com
Subject: Re: [PATCH] x86/bhi: BHI mitigation can trigger warning in #DB
handler
On 5/23/24 07:52, Alexandre Chartre wrote:
>> Should we wrap up this gem and put it with the other entry selftests?
>
> It looks like tools/testing/selftests/x86/single_step_syscall.c tests
> sysenter with TF set but it doesn't check if the kernel issues any
> warning.
Does it actually trip the warning though? I'm a bit surprised that
nobody reported it if so.
Powered by blists - more mailing lists