public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yoshinoya" <yoshinoyatoko@163.com>
To: devel@edk2.groups.io, lersek@redhat.com
Subject: Re: [edk2-devel] Use dynamic pcd in smm mode
Date: Thu, 9 Nov 2023 14:03:01 +0800 (CST)	[thread overview]
Message-ID: <602275c3.324b.18bb2ad452a.Coremail.yoshinoyatoko@163.com> (raw)
In-Reply-To: <42cdccba-beb2-9e99-20b7-973f0629f6f4@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]

Hi, Laszlo:
Got it.


Thanks a lot!


I study the udk code, and find there are no smm pcd drivers, so can't use dynamic pcd in smm code.

















At 2023-11-07 20:45:16, "Laszlo Ersek" <lersek@redhat.com> wrote:
>On 11/7/23 12:31, Yoshinoya wrote:
>> Hi, All:
>> Could dynamic PCD be used in smm driver code?
>> 
>> It seems pcd has pei/dxe drivers, but not have smm related infrastructur
>> drivers.
>
>Dynamic PCDs (or more generally, DXE protocols) can be used in the entry
>point functions of DXE_SMM_DRIVER modules, to my understanding. Dynamic
>PCDs can't be used in any SMM services (callbacks, protocol member
>functions, SMI handlers, etc) that those modules provide (i.e., dynamic
>PCDs can't be used after the entry point function has returned).
>
>I'm not sure about MM_STANDALONE modules. The PI spec probably explains
>the environment in which the entry points of those modules are invoked.
>
>Laszlo
>
>
>
>
>


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#110950): https://edk2.groups.io/g/devel/message/110950
Mute This Topic: https://groups.io/mt/102440663/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 2248 bytes --]

  reply	other threads:[~2023-11-09  6:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25  6:01 [edk2-devel] question about cxl device enumeration in pci bus driver Yoshinoya
2023-10-25 10:13 ` Ni, Ray
2023-10-26  2:36   ` Yoshinoya
2023-10-26  8:33     ` Gerd Hoffmann
2023-10-26  9:49       ` Laszlo Ersek
2023-10-26 13:35         ` Jonathan Cameron via groups.io
2023-10-27  1:26           ` Yoshinoya
     [not found]           ` <1791D2898E0C74CA.20272@groups.io>
2023-10-27  1:29             ` Yoshinoya
2023-10-27  5:49               ` Ni, Ray
2023-11-06 11:20               ` Yoshinoya
2023-11-07 21:54                 ` Brian J. Johnson
2023-11-17  1:41                   ` Yoshinoya
2023-11-07 11:31 ` [edk2-devel] Use dynamic pcd in smm mode Yoshinoya
2023-11-07 12:45   ` Laszlo Ersek
2023-11-09  6:03     ` Yoshinoya [this message]
2023-11-17  2:15   ` [edk2-devel] question about PrmPkg Yoshinoya
2023-11-17  8:42     ` Laszlo Ersek
2023-11-17 16:04       ` Michael Kubacki
2023-11-20  2:09         ` Yoshinoya
2023-11-20 13:58           ` Michael Kubacki
2024-02-27 10:06           ` [edk2-devel] Question about SMM code privilege switch Yoshinoya
2024-03-04  1:20             ` Yoshinoya
2024-05-23  2:07               ` [edk2-devel] What PTSS abbreviation means Yoshinoya
2024-02-05  9:49     ` [edk2-devel] sctpackage failed to be compile with new udk codebase Yoshinoya

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=602275c3.324b.18bb2ad452a.Coremail.yoshinoyatoko@163.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