From: Laszlo Ersek <lersek@redhat.com>
To: "Yao, Jiewen" <jiewen.yao@intel.com>
Cc: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Dong, Eric" <eric.dong@intel.com>
Subject: Re: [PATCH] UefiCpuPkg/SmmCpu: Block SMM read-out only when static paging is used
Date: Wed, 7 Nov 2018 14:36:40 +0100 [thread overview]
Message-ID: <ab1ad449-1a03-2901-93d7-bf01af24901e@redhat.com> (raw)
In-Reply-To: <74D8A39837DF1E4DA445A8C0B3885C503F3D8305@shsmsx102.ccr.corp.intel.com>
On 11/07/18 09:27, Yao, Jiewen wrote:
> If Static paging is not used, then the SMM uses dynamic paging.
>
> Here dynamic paging means the page fault request on-demand.
>
> 2 special examples here:
> 1) above 4G MMIO. By default, SMM only setup paging table for 4G memory. If MMIO above 4G, then SMM need use #PF handler to grant MMIO access.
> 2) server RAS. By default, SMM only setup paging table for SMM communication buffer. For server RAS, memory hotplug may request direct OS memory access. If so, we also rely on #PF handler to grant OS access.
>
> This patch fixed the second issue in the second case.
This is very interesting -- if you have a bit of time, can you please
describe in more detail what "For server RAS, memory hotplug may request
direct OS memory access" means? What agents take what steps?
(I don't mean to hold this patch -- I've given my A-b, so this is for my
own education only. Although, adding this very useful info to the commit
message, or at least to the associated BZ, would be extremely useful.)
Thanks!
Laszlo
next prev parent reply other threads:[~2018-11-07 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 2:59 [PATCH] UefiCpuPkg/SmmCpu: Block SMM read-out only when static paging is used Ruiyu Ni
2018-11-06 16:13 ` Laszlo Ersek
2018-11-06 22:44 ` Yao, Jiewen
2018-11-07 8:27 ` Yao, Jiewen
2018-11-07 13:36 ` Laszlo Ersek [this message]
2018-11-08 6:16 ` Yao, Jiewen
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=ab1ad449-1a03-2901-93d7-bf01af24901e@redhat.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