mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kiryl Shutsemau <kas@kernel.org>
To: moe@flashbots.net
Cc: Rick Edgecombe <rick.p.edgecombe@intel.com>,
	 Dave Hansen <dave.hansen@linux.intel.com>,
	Erdem Aktas <erdemaktas@google.com>,
	 Tom Lendacky <thomas.lendacky@amd.com>,
	Dan Williams <djbw@kernel.org>, Jun Miao <jun.miao@intel.com>,
	 Kuppuswamy Sathyanarayanan
	<sathyanarayanan.kuppuswamy@linux.intel.com>,
	x86@kernel.org, linux-coco@lists.linux.dev, kvm@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] virt: tdx-guest: Fix and speed up the wait for a Quote
Date: Fri, 23 Oct 2026 11:17:10 +0100	[thread overview]
Message-ID: <atsz9rdU4CCjhSD2@thinkstation> (raw)
In-Reply-To: <20261022-tdx-guest-quote-poll-v2-0-7543c6eb2d36@flashbots.net>

On Thu, Oct 22, 2026 at 04:31:40PM +0000, Moe Mahhouk via B4 Relay wrote:
> Getting a TDX Quote takes at least one second, because
> wait_for_quote_completion() sleeps a full second before each status
> check, while a local Quote Generation Service answers in a few
> milliseconds. Patch 2 polls with an exponential backoff instead.
> 
> In v1, Kiryl noticed that the same loop gets a real timeout wrong.
> Patch 1 fixes that on its own, so that it can be backported; patch 2
> then replaces the loop.

For the series:

Reviewed-by: Kiryl Shutsemau (Meta) <kas@kernel.org>

-- 
  Kiryl Shutsemau / Kirill A. Shutemov

      parent reply	other threads:[~2026-10-23 10:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-22 16:31 Moe Mahhouk via B4 Relay
2026-10-22 16:31 ` [PATCH v2 1/2] virt: tdx-guest: Fix timeout detection in wait_for_quote_completion() Moe Mahhouk via B4 Relay
2026-10-23 20:43   ` Kuppuswamy Sathyanarayanan
2026-10-22 16:31 ` [PATCH v2 2/2] virt: tdx-guest: Poll Quote status with exponential backoff Moe Mahhouk via B4 Relay
2026-10-23 20:58   ` Kuppuswamy Sathyanarayanan
2026-10-23 10:17 ` Kiryl Shutsemau [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=atsz9rdU4CCjhSD2@thinkstation \
    --to=kas@kernel.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=djbw@kernel.org \
    --cc=erdemaktas@google.com \
    --cc=jun.miao@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moe@flashbots.net \
    --cc=rick.p.edgecombe@intel.com \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.com \
    --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®