From: "Min Xu" <min.m.xu@intel.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Aktas, Erdem" <erdemaktas@google.com>,
James Bottomley <jejb@linux.ibm.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
Gerd Hoffmann <kraxel@redhat.com>,
"Xu, Min M" <min.m.xu@intel.com>
Subject: Re: [PATCH 1/1] OvmfPkg: Reserve the Ovmf work area as RT_DATA
Date: Tue, 23 Aug 2022 01:38:33 +0000 [thread overview]
Message-ID: <PH0PR11MB50645D6E7F22A69F8E1635A6C5709@PH0PR11MB5064.namprd11.prod.outlook.com> (raw)
In-Reply-To: <982ab701-e912-db72-51e8-090c3ba5b63d@amd.com>
On August 22, 2022 9:19 PM, Tom Lendacky wrote:
> On 8/21/22 21:23, Min Xu wrote:
> > From: Min M Xu <min.m.xu@intel.com>
> >
> > BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=3974
> >
> > Ovmf work-area (PcdOvmfWorkArea) was designed to store the
> > Confidential Computing guest information, including the CC guest type.
> > This information will be probed by CcProbeLib so that the CC guest
> > type can be determined in run-time. But the Ovmf work-area was
> > reserved as BT_Data so that it cannot be accessed after
> > ExitBootService. Please see the detailed analysis in BZ#3974.
> >
> > RH also reports a similar bug. Please see:
> > https://bugzilla.redhat.com/show_bug.cgi?id=2114858
> >
> > This patch reserves the work-area as RT_Data to fix this bug.
>
> The work area was never meant to be kept around. When first introduced,
> Laszlo had said it could be used early, but that global structures should be
> represented by PCDs. So the code is correct. It seems that the CcProbeLib
> should be setting some PCDs during the start of DXE or similar for use during
> run time services.
>
Hi, Tom
The dynamic PCD is not thread-safe. Will IoLib be used in multi-thread scenario?
Thanks
Min
prev parent reply other threads:[~2022-08-23 1:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 2:23 [PATCH 1/1] OvmfPkg: Reserve the Ovmf work area as RT_DATA Min Xu
2022-08-22 8:51 ` Gerd Hoffmann
2022-08-23 1:34 ` Min Xu
2022-08-23 7:37 ` Gerd Hoffmann
2022-08-23 8:40 ` Min Xu
2022-08-23 13:07 ` Lendacky, Thomas
2022-08-25 5:47 ` [edk2-devel] " Min Xu
2022-08-25 7:42 ` Gerd Hoffmann
2022-08-25 7:56 ` Min Xu
2022-08-25 8:15 ` Gerd Hoffmann
2022-08-22 13:18 ` Lendacky, Thomas
2022-08-23 1:38 ` 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=PH0PR11MB50645D6E7F22A69F8E1635A6C5709@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