From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Binbin Wu <binbin.wu@linux.intel.com>,
Ira Weiny <ira.weiny@intel.com>, "H. Peter Anvin" <hpa@zytor.com>,
Sagi Shahar <sagis@google.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v2] KVM: TDX: Force split irqchip for TDX at irqchip creation time
Date: Tue, 16 Sep 2025 13:22:16 +0800 [thread overview]
Message-ID: <2e0b5ee6-deae-4eba-89dc-4abfd63b1578@intel.com> (raw)
In-Reply-To: <175798193779.623026.2646711972824495792.b4-ty@google.com>
On 9/16/2025 8:25 AM, Sean Christopherson wrote:
> On Tue, 26 Aug 2025 18:17:26 -0700, Sagi Shahar wrote:
>> TDX module protects the EOI-bitmap which prevents the use of in-kernel
>> I/O APIC. See more details in the original patch [1]
>>
>> The current implementation already enforces the use of split irqchip for
>> TDX but it does so at the vCPU creation time which is generally to late
>> to fallback to split irqchip.
>>
>> [...]
>
> Applied to kvm-x86 misc, thanks!
The latest one of this patch is v4:
https://lore.kernel.org/all/20250904062007.622530-1-sagis@google.com/
> [1/1] KVM: TDX: Force split irqchip for TDX at irqchip creation time
> https://github.com/kvm-x86/linux/commit/2569c8c5767b
What got queued, added a superfluous new line in tdx_vm_init()
> --
> https://github.com/kvm-x86/linux/tree/next
>
next prev parent reply other threads:[~2025-09-16 5:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 1:17 [PATCH v2] KVM: TDX: Force split irqchip for TDX at irqchip creation time Sagi Shahar
2025-08-27 1:41 ` Binbin Wu
2025-08-27 6:22 ` Xiaoyao Li
2025-09-16 0:25 ` Sean Christopherson
2025-09-16 5:22 ` Xiaoyao Li [this message]
2025-09-16 19:59 ` Sean Christopherson
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=2e0b5ee6-deae-4eba-89dc-4abfd63b1578@intel.com \
--to=xiaoyao.li@intel.com \
--cc=binbin.wu@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=ira.weiny@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sagis@google.com \
--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