mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vishal Annapurve <vannapurve@google.com>
To: dave.hansen@linux.intel.com, kirill.shutemov@linux.intel.com,
	 jgross@suse.com, ajay.kaher@broadcom.com, ak@linux.intel.com,
	 tony.luck@intel.com, thomas.lendacky@amd.com
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	hpa@zytor.com,  pbonzini@redhat.com, seanjc@google.com,
	kai.huang@intel.com,  chao.p.peng@linux.intel.com,
	isaku.yamahata@gmail.com,
	 sathyanarayanan.kuppuswamy@linux.intel.com,
	erdemaktas@google.com,  ackerleytng@google.com, jxgao@google.com,
	sagis@google.com,  afranji@google.com, kees@kernel.org,
	jikos@kernel.org, peterz@infradead.org,  x86@kernel.org,
	linux-kernel@vger.kernel.org, linux-coco@lists.linux.dev,
	 virtualization@lists.linux.dev,
	bcm-kernel-feedback-list@broadcom.com,
	 Vishal Annapurve <vannapurve@google.com>
Subject: [PATCH v7 3/3] x86/tdx: Emit warning if IRQs are enabled during HLT #VE handling
Date: Fri, 28 Feb 2025 01:44:16 +0000	[thread overview]
Message-ID: <20250228014416.3925664-4-vannapurve@google.com> (raw)
In-Reply-To: <20250228014416.3925664-1-vannapurve@google.com>

Direct HLT instruction execution causes #VEs for TDX VMs which is routed
to hypervisor via TDCALL. safe_halt() routines execute HLT in STI-shadow
so IRQs need to remain disabled until the TDCALL to ensure that pending
IRQs are correctly treated as wake events.

Emit warning and fail emulation if IRQs are enabled during HLT #VE handling
to avoid running into scenarios where IRQ wake events are lost resulting in
indefinite HLT execution times.

Reviewed-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Signed-off-by: Vishal Annapurve <vannapurve@google.com>
---
 arch/x86/coco/tdx/tdx.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/arch/x86/coco/tdx/tdx.c b/arch/x86/coco/tdx/tdx.c
index 6aad910d119d..a97ddc6a52c3 100644
--- a/arch/x86/coco/tdx/tdx.c
+++ b/arch/x86/coco/tdx/tdx.c
@@ -393,6 +393,14 @@ static int handle_halt(struct ve_info *ve)
 {
 	const bool irq_disabled = irqs_disabled();
 
+	/*
+	 * HLT with IRQs enabled is unsafe, as an IRQ that is intended to be a
+	 * wake event may be consumed before requesting HLT emulation, leaving
+	 * the vCPU blocking indefinitely.
+	 */
+	if (WARN_ONCE(!irq_disabled, "HLT emulation with IRQs enabled"))
+		return -EIO;
+
 	if (__halt(irq_disabled))
 		return -EIO;
 
-- 
2.48.1.711.g2feabab25a-goog


  parent reply	other threads:[~2025-02-28  1:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28  1:44 [PATCH v7 0/3] x86/tdx: Fix HLT logic execution for TDX VMs Vishal Annapurve
2025-02-28  1:44 ` [PATCH v7 1/3] x86/paravirt: Move halt paravirt calls under CONFIG_PARAVIRT Vishal Annapurve
2025-03-26  8:02   ` [tip: x86/tdx] " tip-bot2 for Kirill A. Shutemov
2025-02-28  1:44 ` [PATCH v7 2/3] x86/tdx: Fix arch_safe_halt() execution for TDX VMs Vishal Annapurve
2025-03-26  8:02   ` [tip: x86/tdx] " tip-bot2 for Vishal Annapurve
2025-02-28  1:44 ` Vishal Annapurve [this message]
2025-03-26  8:02   ` [tip: x86/tdx] x86/tdx: Emit warning if IRQs are enabled during HLT #VE handling tip-bot2 for Vishal Annapurve
2025-03-22  1:08 ` [PATCH v7 0/3] x86/tdx: Fix HLT logic execution for TDX VMs Vishal Annapurve
2025-03-24 18:53 ` Ryan Afranji

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=20250228014416.3925664-4-vannapurve@google.com \
    --to=vannapurve@google.com \
    --cc=ackerleytng@google.com \
    --cc=afranji@google.com \
    --cc=ajay.kaher@broadcom.com \
    --cc=ak@linux.intel.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bp@alien8.de \
    --cc=chao.p.peng@linux.intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=erdemaktas@google.com \
    --cc=hpa@zytor.com \
    --cc=isaku.yamahata@gmail.com \
    --cc=jgross@suse.com \
    --cc=jikos@kernel.org \
    --cc=jxgao@google.com \
    --cc=kai.huang@intel.com \
    --cc=kees@kernel.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sagis@google.com \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.com \
    --cc=seanjc@google.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=tony.luck@intel.com \
    --cc=virtualization@lists.linux.dev \
    --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®