From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Roberto Sassu" <roberto.sassu@huaweicloud.com>,
"James Bottomley" <James.Bottomley@HansenPartnership.com>,
"Linux regressions mailing list" <regressions@lists.linux.dev>
Cc: <keyrings@vger.kernel.org>,
"linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>,
"LKML" <linux-kernel@vger.kernel.org>,
"Pengyu Ma" <mapengyu@gmail.com>
Subject: Re: [regression] significant delays when secureboot is enabled since 6.10
Date: Wed, 11 Sep 2024 18:14:35 +0300 [thread overview]
Message-ID: <D43JXBFOOB2O.3U6ZQ7DASR1ZW@kernel.org> (raw)
In-Reply-To: <f554031343039883068145f9f4777277e490dc05.camel@huaweicloud.com>
On Wed Sep 11, 2024 at 11:53 AM EEST, Roberto Sassu wrote:
> I made few measurements. I have a Fedora 38 VM with TPM passthrough.
I was thinking more like
sudo bpftrace -e 'k:tpm_transmit { @start[tid] = nsecs; } kr:tpm_transmit { @[kstack, ustack, comm] = sum(nsecs - @start[tid]); delete(@start[tid]); } END { clear(@start); }'
For example when running "tpm2_createprimary --hierarchy o -G rsa2048 -c owner.txt", I get:
Attaching 3 probes...
^C
@[
tpm_transmit_cmd+46
tpm2_flush_context+120
tpm2_commit_space+197
tpm_dev_transmit.constprop.0+137
tpm_dev_async_work+102
process_one_work+374
worker_thread+614
kthread+207
ret_from_fork+49
ret_from_fork_asm+26
, , kworker/4:2]: 2860677
@[
tpm_dev_transmit.constprop.0+111
tpm_dev_async_work+102
process_one_work+374
worker_thread+614
kthread+207
ret_from_fork+49
ret_from_fork_asm+26
, , kworker/16:1]: 3890693
@[
tpm_transmit_cmd+46
tpm2_load_context+195
tpm2_prepare_space+410
tpm_dev_transmit.constprop.0+54
tpm_dev_async_work+102
process_one_work+374
worker_thread+614
kthread+207
ret_from_fork+49
ret_from_fork_asm+26
, , kworker/4:2]: 9058524
@[
tpm_transmit_cmd+46
tpm2_save_context+179
tpm2_commit_space+314
tpm_dev_transmit.constprop.0+137
tpm_dev_async_work+102
process_one_work+374
worker_thread+614
kthread+207
ret_from_fork+49
ret_from_fork_asm+26
, , kworker/4:2]: 11426260
@[
tpm_transmit_cmd+46
tpm2_load_context+195
tpm2_prepare_space+318
tpm_dev_transmit.constprop.0+54
tpm_dev_async_work+102
process_one_work+374
worker_thread+614
kthread+207
ret_from_fork+49
ret_from_fork_asm+26
, , kworker/4:2]: 14182972
@[
tpm_transmit_cmd+46
tpm2_save_context+179
tpm2_commit_space+155
tpm_dev_transmit.constprop.0+137
tpm_dev_async_work+102
process_one_work+374
worker_thread+614
kthread+207
ret_from_fork+49
ret_from_fork_asm+26
, , kworker/4:2]: 22597059
@[
tpm_dev_transmit.constprop.0+111
tpm_dev_async_work+102
process_one_work+374
worker_thread+614
kthread+207
ret_from_fork+49
ret_from_fork_asm+26
, , kworker/4:2]: 1958500581
This results stacks to compare with "real" time spent total in each
stack (in nsecs). CPU time is relevant measure in the problem we're
dealing.
BR, Jarkko
next prev parent reply other threads:[~2024-09-11 15:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 9:01 [regression] significant delays when secureboot is enabled since 6.10 Linux regression tracking (Thorsten Leemhuis)
2024-09-10 9:05 ` Roberto Sassu
2024-09-10 12:39 ` Jarkko Sakkinen
2024-09-10 12:48 ` Jarkko Sakkinen
2024-09-10 12:57 ` James Bottomley
2024-09-10 13:28 ` Jarkko Sakkinen
2024-09-11 8:53 ` Roberto Sassu
2024-09-11 12:21 ` James Bottomley
2024-09-12 13:16 ` Jarkko Sakkinen
2024-09-12 13:26 ` James Bottomley
2024-09-12 13:36 ` Roberto Sassu
2024-09-12 14:13 ` James Bottomley
2024-09-12 14:52 ` Roberto Sassu
2024-09-12 14:26 ` Jarkko Sakkinen
2024-09-14 10:42 ` Jarkko Sakkinen
2024-09-14 10:51 ` Jarkko Sakkinen
2024-09-14 10:58 ` Jarkko Sakkinen
2024-09-11 15:14 ` Jarkko Sakkinen [this message]
2024-09-12 8:13 ` Roberto Sassu
2024-09-12 14:23 ` Jarkko Sakkinen
2024-09-13 20:50 ` Jarkko Sakkinen
2024-09-13 22:06 ` Jarkko Sakkinen
2024-09-15 9:43 ` Jarkko Sakkinen
2024-09-15 10:07 ` Jarkko Sakkinen
2024-09-15 13:59 ` James Bottomley
2024-09-15 14:50 ` Jarkko Sakkinen
2024-09-15 14:55 ` Jarkko Sakkinen
2024-09-15 15:00 ` James Bottomley
2024-09-15 16:22 ` Jarkko Sakkinen
2024-09-21 15:40 ` Jarkko Sakkinen
2024-09-22 14:11 ` Jarkko Sakkinen
2024-09-10 12:22 ` James Bottomley
2024-09-10 12:41 ` Linux regression tracking (Thorsten Leemhuis)
2024-09-10 22:40 ` Jarkko Sakkinen
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=D43JXBFOOB2O.3U6ZQ7DASR1ZW@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mapengyu@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=roberto.sassu@huaweicloud.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