From: Dave Hansen <dave.hansen@intel.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Vishal Annapurve <vannapurve@google.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
pbonzini@redhat.com, seanjc@google.com, erdemaktas@google.com,
ackerleytng@google.com, jxgao@google.com, sagis@google.com,
oupton@google.com, pgonda@google.com, kirill@shutemov.name,
dave.hansen@linux.intel.com, linux-coco@lists.linux.dev,
chao.p.peng@linux.intel.com, isaku.yamahata@gmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH V3 1/2] x86/tdx: Route safe halt execution via tdx_safe_halt()
Date: Tue, 11 Feb 2025 15:46:23 -0800 [thread overview]
Message-ID: <c07fa2b7-d453-4a9d-b1fc-e3e96514a8d3@intel.com> (raw)
In-Reply-To: <wra363f7ye6mwv2papahmpgmybi45yqyzeohunbqju3zsf22td@zcutpjluiury>
On 2/11/25 00:32, Kirill A. Shutemov wrote:
>> If CONFIG_PARAVIRT_XXL is disabled, "sti;hlt" sequences can still get
>> executed from TDX VMs via paths like:
>> acpi_safe_halt() =>
>> raw_safe_halt() =>
>> arch_safe_halt() =>
>> native_safe_halt()
>> There is a long term plan to fix these paths by carving out
>> irq.safe_halt() outside paravirt framework.
> I don't think it is acceptable to keep !PARAVIRT_XXL (read no-Xen) config
> broken.
Oh, I thought it took PARAVIRT_XXL=y to even trigger this issue. Was I
just confused?
next prev parent reply other threads:[~2025-02-11 23:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 22:27 [PATCH V3 1/2] x86/tdx: Route safe halt execution via tdx_safe_halt() Vishal Annapurve
2025-02-06 22:27 ` [PATCH V3 2/2] x86/tdx: Emit warning if IRQs are enabled during HLT #VE handling Vishal Annapurve
2025-02-07 15:22 ` Sean Christopherson
2025-02-10 18:08 ` Vishal Annapurve
2025-02-11 8:32 ` [PATCH V3 1/2] x86/tdx: Route safe halt execution via tdx_safe_halt() Kirill A. Shutemov
2025-02-11 23:37 ` Vishal Annapurve
2025-02-11 23:46 ` Dave Hansen [this message]
2025-02-12 0:22 ` Vishal Annapurve
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=c07fa2b7-d453-4a9d-b1fc-e3e96514a8d3@intel.com \
--to=dave.hansen@intel.com \
--cc=ackerleytng@google.com \
--cc=chao.p.peng@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=erdemaktas@google.com \
--cc=isaku.yamahata@gmail.com \
--cc=jxgao@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=oupton@google.com \
--cc=pbonzini@redhat.com \
--cc=pgonda@google.com \
--cc=sagis@google.com \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=vannapurve@google.com \
--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