[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0d9e4840da85ae419b5f583c9dacee1588a509ba.camel@intel.com>
Date: Thu, 13 Nov 2025 00:41:37 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "seanjc@...gle.com" <seanjc@...gle.com>
CC: "bp@...en8.de" <bp@...en8.de>, "x86@...nel.org" <x86@...nel.org>,
"thorsten.blum@...ux.dev" <thorsten.blum@...ux.dev>, "hpa@...or.com"
<hpa@...or.com>, "mingo@...hat.com" <mingo@...hat.com>, "tglx@...utronix.de"
<tglx@...utronix.de>, "dave.hansen@...ux.intel.com"
<dave.hansen@...ux.intel.com>, "pbonzini@...hat.com" <pbonzini@...hat.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>, "linux-coco@...ts.linux.dev"
<linux-coco@...ts.linux.dev>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "kas@...nel.org" <kas@...nel.org>
Subject: Re: [PATCH RESEND] KVM: TDX: Use struct_size and simplify
tdx_get_capabilities
On Wed, 2025-11-12 at 12:24 -0800, Sean Christopherson wrote:
> Your CI caught me just in time; I applied this locally last week, but haven't
> fully pushed it to kvm-x86 yet. :-)
The TDX CI tracks some upstream branches. Is there one in kvm_x86 tree that
would be useful? It's not foolproof enough to warrant sending out automated
mails. But we monitor it and might notice TDX specific issues. Ideally we would
not be chasing generic bugs in like scratch code not headed upstream or
something.
Powered by blists - more mailing lists