From: Jun Miao <jun.miao@intel.com>
To: kas@kernel.org, dave.hansen@linux.intel.com,
rick.p.edgecombe@intel.com,
sathyanarayanan.kuppuswamy@linux.intel.com
Cc: linux-coco@lists.linux.dev, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, jun.miao@intel.com
Subject: [PATCH 1/1] virt: tdx-guest: Optimize the get-quote polling interval time
Date: Wed, 11 Feb 2026 16:58:01 +0800 [thread overview]
Message-ID: <20260211085801.4036464-2-jun.miao@intel.com> (raw)
In-Reply-To: <20260211085801.4036464-1-jun.miao@intel.com>
The TD guest sends TDREPORT to the TD Quoting Enclave via a vsock or
a tdvmcall. In general, vsock is indeed much faster than tdvmcall,
and Quote requests usually take a few millisecond to complete rather
than seconds based on actual measurements.
The following get quote time via tdvmcall were obtained on the GNR:
| msleep_interruptible(time) | 1s | 5ms | 1ms |
| ------------------------------ | -------- | -------- | ---------- |
| Duration | 1.004 s | 1.005 s | 1.036 s |
| Total(Get Quote) | 167 | 142 | 167 |
| Success: | 167 | 142 | 167 |
| Failure: | 0 | 0 | 0 |
| Avg total / 1s | 0.97 | 141.31 | 166.35 |
| Avg success / 1s | 0.97 | 141.31 | 166.35 |
| Avg total / 1s / thread | 0.97 | 141.31 | 166.35 |
| Avg success / 1s / thread | 0.97 | 141.31 | 166.35 |
| Min elapsed_time | 1025.95ms| 6.85 ms | 2.99 ms |
| Max elapsed_time | 1025.95ms| 10.93 ms | 10.76 ms |
According to trace analysis, the typical execution tdvmcall get the
quote time is 4 ms. Therefore, 5 ms is a reasonable balance between
performance efficiency and CPU overhead.
And compared to the previous throughput of one request per second,
the current 5ms can get 142 requests per second delivers a
142× performance improvement, which is critical for high-frequency
use cases without vsock.
So, change the 1s (MSEC_PER_SEC) -> 5ms (MSEC_PER_SEC / 200)
Signed-off-by: Jun Miao <jun.miao@intel.com>
---
drivers/virt/coco/tdx-guest/tdx-guest.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/virt/coco/tdx-guest/tdx-guest.c b/drivers/virt/coco/tdx-guest/tdx-guest.c
index 4e239ec960c9..71d2d7304b1a 100644
--- a/drivers/virt/coco/tdx-guest/tdx-guest.c
+++ b/drivers/virt/coco/tdx-guest/tdx-guest.c
@@ -251,11 +251,11 @@ static int wait_for_quote_completion(struct tdx_quote_buf *quote_buf, u32 timeou
int i = 0;
/*
- * Quote requests usually take a few seconds to complete, so waking up
- * once per second to recheck the status is fine for this use case.
+ * Quote requests usually take a few milliseconds to complete, so waking up
+ * once per 5 milliseconds to recheck the status is fine for this use case.
*/
- while (quote_buf->status == GET_QUOTE_IN_FLIGHT && i++ < timeout) {
- if (msleep_interruptible(MSEC_PER_SEC))
+ while (quote_buf->status == GET_QUOTE_IN_FLIGHT && i++ < 200 * timeout) {
+ if (msleep_interruptible(MSEC_PER_SEC / 200))
return -EINTR;
}
--
2.32.0
next prev parent reply other threads:[~2026-02-11 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 8:58 [PATCH 0/1] [Test Report] get qutoe time via tdvmcall Jun Miao
2026-02-11 8:58 ` Jun Miao [this message]
2026-02-20 18:45 ` [PATCH 1/1] virt: tdx-guest: Optimize the get-quote polling interval time Kuppuswamy Sathyanarayanan
2026-02-22 2:17 ` Miao, Jun
2026-03-10 18:58 ` Kuppuswamy Sathyanarayanan
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=20260211085801.4036464-2-jun.miao@intel.com \
--to=jun.miao@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=rick.p.edgecombe@intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
/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