From: "Min Xu" <min.m.xu@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [edk2-devel] Regression: 100x I/O performance slowdown in SEC phase caused by TDX
Date: Wed, 13 Apr 2022 03:33:15 +0000 [thread overview]
Message-ID: <PH0PR11MB5064754E144DB4E90E23A7C6C5EC9@PH0PR11MB5064.namprd11.prod.outlook.com> (raw)
In-Reply-To: <e69f65c5800014337d4a06bee96211e4b55bed43.camel@HansenPartnership.com>
On April 13, 2022 5:22 AM, James Bottom wrote:
>
> I'm using a SEC phase which has a TPM driver to experiment with sorting out
> measured boot, which is how I noticed (usually SEC doesn't do MMIO) .
> What I'm seeing is after commit b6b2de884864 ("MdePkg: Support mmio for
> Tdx guest in BaseIoLibIntrinsic") we get a massive slowdown of about 100x in
> TPM performance. The reason seems to be this addition to the
> mmioreadX/mmiowriteX code:
>
> MemoryFence ();
> - *(volatile UINT16 *)Address = Value;
> +
> + if (IsTdxGuest ()) {
> + TdMmioWrite16 (Address, Value);
> + } else {
> + *(volatile UINT16 *)Address = Value;
> + }
> +
> MemoryFence ();
>
>
> The problem is that IsTdxGuest () has this structure:
>
> BOOLEAN
> EFIAPI
> IsTdxGuest (
> VOID
> )
> {
> if (mTdxProbed) {
> return mTdxEnabled;
> }
>
> mTdxEnabled = TdIsEnabled ();
> mTdxProbed = TRUE;
>
> return mTdxEnabled;
> }
>
> Which is trying to cache the result of the probe in the efi data segment.
> However, that doesn't work in SEC, because the data segment is read only
> (so the write seems to succeed but a read will always return the original
> value), leading to us calling TdIsEnabled() check for every mmio we do,
> which is causing the slowdown because it's very expensive.
>
The analysis is right. I hadn't thought the basic IO would be heavily called in SEC phase. I will fix it as soon as possible.
My thought is that a TdProbeLib will be introduced in MdePkg. In MdePkg this lib is of null instance. It just simply return TD_PROBE_NON which means it is not Td guest. This lib will be added in MdePkg/MdeLibs.dsc.inc (like RegisterFilterLibNull).
In OvmfPkg TdProbeLib will be implemented. It checks the OvmfWorkArea to determine the guest type.
Thanks
Min
prev parent reply other threads:[~2022-04-13 3:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 21:22 Regression: 100x I/O performance slowdown in SEC phase caused by TDX James Bottomley
2022-04-13 3:33 ` Min Xu [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-list 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=PH0PR11MB5064754E144DB4E90E23A7C6C5EC9@PH0PR11MB5064.namprd11.prod.outlook.com \
--to=devel@edk2.groups.io \
/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