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 0/1] [Test Report] get qutoe time via tdvmcall
Date: Wed, 11 Feb 2026 16:58:00 +0800 [thread overview]
Message-ID: <20260211085801.4036464-1-jun.miao@intel.com> (raw)
[Background]
Currently, many mobile device vendors (such as OPPO and Xiaomi) use TDVM for security management.
Each mobile terminal must perform remote attestation before it can access the TDVM confidential container.
As a result, there are a large number of remote attestation get-quote requests, especially in cases
where vsock is not configured or misconfigured and cannot be used.
[Limitation]
Currently, the polling interval is set to 1 second, which allows at most one quote to be retrieved per second.
For workloads with frequent remote attestations, polling once per second severely limits performance.
Test like this:
[root@INTELTDX ~]# ./test_tdx_attest-thread
Start tdx_att_get_quote concurrent loop, duration: 1 s, threads: 1
Summary (tdx_att_get_quote)
Threads: 1
Mode: concurrent
Duration: requested 1 s, actual 1.036 s
Total: 1
Success: 1
Failure: 0
Avg total per 1s: 0.97
Avg success per 1s: 0.97
Avg total per 1s per thread: 0.97
Avg success per 1s per thread: 0.97
Min elapsed_time: 1025.95 ms
Max elapsed_time: 1025.95 ms
[Optimization Rationale]
But the actual trace the get quote time on GNR platform:
test_tdx_attest-598 [001] ..... 371.214611: tdx_report_new: [debug start wait]===: I am in function wait_for_quote_completion LINE=155===
test_tdx_attest-598 [001] ..... 371.220287: tdx_report_new: [debug end wait]===: I am in function wait_for_quote_completion LINE=162===
Cost time: 371.220287 - 371.215611 = 0.004676 = 4.6ms
The following test results were obtained on the GNR platform:
| msleep_interruptible(time) | 1ms | 5ms | 1s |
| ------------------------------ | -------- | -------- | ---------- |
| Duration | 1.004 s | 1.005 s | 1.036 s |
| Total(Get Quote) | 167 | 142 | 1 |
| Success: | 167 | 142 | 1 |
| Failure: | 0 | 0 | 0 |
| Avg total / 1s | 166.35 | 141.31 | 0.97 |
| Avg success / 1s | 166.35 | 141.31 | 0.97 |
| Avg total / 1s / thread | 166.35 | 141.31 | 0.97 |
| Avg success / 1s / thread | 166.35 | 141.31 | 0.97 |
| Min elapsed_time | 2.99 ms | 6.85 ms | 1025.95 ms |
| Max elapsed_time | 10.76 ms | 10.93 ms | 1025.95 ms |
Jun Miao (1):
virt: tdx-guest: Optimize the get-quote polling interval time
drivers/virt/coco/tdx-guest/tdx-guest.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--
2.32.0
next 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 Jun Miao [this message]
2026-02-11 8:58 ` [PATCH 1/1] virt: tdx-guest: Optimize the get-quote polling interval time Jun Miao
2026-02-20 18:45 ` 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-1-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