From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
"sathyanarayanan.kuppuswamy@linux.intel.com"
<sathyanarayanan.kuppuswamy@linux.intel.com>,
"kas@kernel.org" <kas@kernel.org>,
"Aktas, Erdem" <erdemaktas@google.com>,
"djbw@kernel.org" <djbw@kernel.org>,
"moe@flashbots.net" <moe@flashbots.net>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"Miao, Jun" <jun.miao@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH v3 0/2] virt: tdx-guest: Fix and speed up the wait for a Quote
Date: Mon, 2 Nov 2026 19:55:36 +0000 [thread overview]
Message-ID: <3b582cdcfe37f1d01ee71611ab2611f845261089.camel@intel.com> (raw)
In-Reply-To: <20261024-tdx-guest-quote-poll-v3-0-6a83bb767314@flashbots.net>
On Sat, 2026-10-24 at 19:17 +0000, Moe Mahhouk via B4 Relay wrote:
>
> The GHCI SetupEventNotifyInterrupt mechanism would avoid polling
> altogether, but it relies on the VMM implementing that service. This
> series keeps the existing polling model, which works with any VMM.
Long term though, isn't this a better option? This patch is essentially a
performance optimization.
Polling is always going to be weird. And when the attestation speed changes
(possible in the many upcoming attestation plans) this tuning could again be
suboptimal. I think we should fix it properly... This seems like "this hack
worked for me for now".
prev parent reply other threads:[~2026-11-02 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-24 19:17 Moe Mahhouk via B4 Relay
2026-10-24 19:17 ` [PATCH v3 1/2] virt: tdx-guest: Fix timeout detection in wait_for_quote_completion() Moe Mahhouk via B4 Relay
2026-10-27 13:50 ` Xiaoyao Li
2026-10-24 19:17 ` [PATCH v3 2/2] virt: tdx-guest: Poll Quote status with exponential backoff Moe Mahhouk via B4 Relay
2026-10-27 14:08 ` Xiaoyao Li
2026-11-02 19:55 ` Edgecombe, Rick P [this message]
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=3b582cdcfe37f1d01ee71611ab2611f845261089.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=djbw@kernel.org \
--cc=erdemaktas@google.com \
--cc=jun.miao@intel.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=moe@flashbots.net \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=thomas.lendacky@amd.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
all inboxes | Powered by JetHome®