From: Josh Poimboeuf <jpoimboe@kernel.org>
To: Alexandre Chartre <alexandre.chartre@oracle.com>
Cc: x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, daniel.sneddon@linux.intel.com,
pawan.kumar.gupta@linux.intel.com, tglx@linutronix.de,
konrad.wilk@oracle.com, peterz@infradead.org, seanjc@google.com,
andrew.cooper3@citrix.com, dave.hansen@linux.intel.com,
nik.borisov@suse.com, kpsingh@kernel.org, longman@redhat.com,
bp@alien8.de, pbonzini@redhat.com
Subject: Re: [PATCH v2] x86/bhi: BHI mitigation can trigger warning in #DB handler
Date: Tue, 2 Jul 2024 23:24:55 -0700 [thread overview]
Message-ID: <20240703062455.ncak7idh2e3fv6sq@treble> (raw)
In-Reply-To: <20240524070459.3674025-1-alexandre.chartre@oracle.com>
On Fri, May 24, 2024 at 09:04:59AM +0200, Alexandre Chartre wrote:
> When BHI mitigation is enabled, if sysenter is invoked with the TF flag
> set then entry_SYSENTER_compat uses CLEAR_BRANCH_HISTORY and calls the
> clear_bhb_loop() before the TF flag is cleared. This causes the #DB
> handler (exc_debug_kernel) to issue a warning because single-step is
> used outside the entry_SYSENTER_compat function.
Reviewed-by: Josh Poimboeuf <jpoimboe@kernel.org>
--
Josh
next prev parent reply other threads:[~2024-07-03 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 7:04 Alexandre Chartre
2024-05-24 15:42 ` Pawan Gupta
2024-05-24 17:17 ` Andrew Cooper
2024-07-03 6:24 ` Josh Poimboeuf [this message]
2024-07-03 11:52 ` [tip: x86/urgent] x86/bhi: Avoid warning in #DB handler due to BHI mitigation tip-bot2 for Alexandre Chartre
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=20240703062455.ncak7idh2e3fv6sq@treble \
--to=jpoimboe@kernel.org \
--cc=alexandre.chartre@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=daniel.sneddon@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=konrad.wilk@oracle.com \
--cc=kpsingh@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=nik.borisov@suse.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®