From: "Gerd Hoffmann" <kraxel@redhat.com>
To: "Xu, Min M" <min.m.xu@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] CcProbeLib not working for runtime calls
Date: Thu, 18 Aug 2022 06:58:27 +0200 [thread overview]
Message-ID: <20220818045827.7gxm3lizix5e6xbt@sirius.home.kraxel.org> (raw)
In-Reply-To: <CO1PR11MB50581ACC3162ECB8AFFC6A9DC56D9@CO1PR11MB5058.namprd11.prod.outlook.com>
On Thu, Aug 18, 2022 at 01:47:37AM +0000, Xu, Min M wrote:
> On August 17, 2022 7:05 PM, Gerd Hoffmann wrote:
> > https://bugzilla.redhat.com/show_bug.cgi?id=2114858
> >
> > I think the call chain is:
> >
> > -> linux does efi runtime call
> > -> some debug message printed
> > -> OvmfPkg/Library/PlatformDebugLibIoPort/DebugLib.c
> > -> MdePkg/Library/BaseIoLibIntrinsic (IoWriteFifo8)
> > -> OvmfPkg/Library/CcProbeLib (CcProbe)
> > -> page fault when trying to access WorkArea
> >
>
> I think this bug shares the same root cause. https://bugzilla.tianocore.org/show_bug.cgi?id=3974
Yes, highly likely this is the same.
> And there is a fix awaiting for review. https://edk2.groups.io/g/devel/message/91132
Hmm. When the tdx/sev code actually works properly in runtime mode we
should be able to reserve the workarea, mark it as runtime memory
(SetMemorySpaceAttributes) and access it from runtime code, so we don't
need two different ways to figure what CC mode we are running in.
take care,
Gerd
next prev parent reply other threads:[~2022-08-18 4:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 11:04 CcProbeLib not working for runtime calls Gerd Hoffmann
2022-08-18 1:47 ` [edk2-devel] " Min Xu
2022-08-18 4:58 ` Gerd Hoffmann [this message]
2022-08-19 3:39 ` Min Xu
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=20220818045827.7gxm3lizix5e6xbt@sirius.home.kraxel.org \
--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