public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kun Qin" <kun.q@outlook.com>
To: Laszlo Ersek <lersek@redhat.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"tigerliu@zhaoxin.com" <tigerliu@zhaoxin.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Sean <spbrogan@outlook.com>,
	"michael.kubacki@outlook.com" <michael.kubacki@outlook.com>
Subject: Re: [edk2-devel] Question about Smm code / StandaloneMmPkg
Date: Fri, 5 Mar 2021 02:22:55 +0000	[thread overview]
Message-ID: <MWHPR06MB3102AC5E95CD9B4288CC69E5F3969@MWHPR06MB3102.namprd06.prod.outlook.com> (raw)
In-Reply-To: <080ea8cb-30a5-2a98-832c-f918c97c9f5c@redhat.com>

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

Hi Tiger,

Our team has been sending patches to the community to cover Standalone MM driver to support x86 arch recently by believing that Standalone MM is the direction we are moving to in the long term.

From our experience so far, the Standalone MM core infrastructure is arch independent and capable of operations such as dispatching MM drivers and managing memory as is. What really is missing would be the StandaloneMmCpu and an IPL that can install MM foundation for x86 arch. But I am unaware of any public implementation for these 2 components at this moment. As I joined this Standalone MM journey relatively recently, maybe other community members will have more information in that regards.

Generally from our perspective, we are taking Standalone Mm model as an opportunity to provide better isolation between MM and non-MM environment, since this model is providing cleaner boundary inside MM without convoluted access to non-MM (mostly DXE) environment. If x86 SMM core code will ever be added to Standalone MM implemation, I would hope we do not lose advantage on that specific point.

Thanks,
Kun

From: Laszlo Ersek<mailto:lersek@redhat.com>
Sent: Thursday, March 4, 2021 12:55
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; tigerliu@zhaoxin.com<mailto:tigerliu@zhaoxin.com>; Kinney, Michael D<mailto:michael.d.kinney@intel.com>; Kun Qin<mailto:kun.q@outlook.com>
Subject: Re: [edk2-devel] Question about Smm code / StandaloneMmPkg

Adding Kun Qin; a comment below:

On 03/04/21 09:34, Tiger Liu(BJ-RD) wrote:
> Dear All:
> I have a few questions about Smm code and StandaloneMmPkg.
>
> Take X86 Arch cpu as example:
> 1. Smm infrastructure code is implemented in MdeModulePkg\Core\PiSmmCore
>    But it's a traditional smm mode, used launched in UEFI DXE Phase.
>
> A_Tour_Beyond_BIOS_Launching_Standalone_SMM_Drivers_in_PEI_using_the_EFI_Developer_Kit_II.pdf
> ----> This doc introduced a standalone smm mode.
>
> PI Spec introduces a MM concept, it's arch independent.
>
> So, I have below questions:
> 1. Will X86 SMM code implementation be migrated to MM concept code base?
> 2. StandaloneMmPkg is a MM reference implementation, is it arch independent?
> 3. The above doc mentioned launching SMM drivers in PEI,  is it also implemented in StandaloneMmPkg?

Please see (also) the following thread:

  [edk2-rfc] [RFC]
  Support Both MM Traditional and Standalone Drivers with One MM Core

  https://edk2.groups.io/g/rfc/message/430

Thanks
Laszlo


>
> Thanks
>
>
> 保密声明:
> 本邮件含有保密或专有信息,仅供指定收件人使用。严禁对本邮件或其内容做任何未经授权的查阅、使用、复制或转发。
> CONFIDENTIAL NOTE:
> This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or forwarding of this email or the content of this email is strictly prohibited.
>
>
> 
>
>


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

  reply	other threads:[~2021-03-05  2:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04  8:34 [edk2-devel] Question about Smm code / StandaloneMmPkg Tiger Liu(BJ-RD)
2021-03-04 20:55 ` Laszlo Ersek
2021-03-05  2:22   ` Kun Qin [this message]
2021-03-08  5:56     ` 答复: " Tiger Liu(BJ-RD)

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=MWHPR06MB3102AC5E95CD9B4288CC69E5F3969@MWHPR06MB3102.namprd06.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