Yeah, there is some good resource on the web.
ACPI spec defined APEI for error handling.
https://www.uefi.org/sites/default/files/resources/ACPI_6_2.pdf
Below ppt introduced basic info on memory technology such as spare or mirror.
ftp://ftp.hp.com/pub/c-products/servers/options/c00256943.pdf
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,
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)
Good suggestion Laszlo.
Current static paging will force:
1) only valid smm comm buffer is present. The OS memory is not present.
2) non smram is NX (no matter static or dynamic paging)
3) code region in Smm is RO (if pe image is page aligned)
4) data region in Smm is NX (if pe image is page
On 11/06/18 03:59, Ruiyu Ni wrote:
> From: Jiewen Yao
>
> Today's implementation blocks SMM read-out no matter static paging
> is enabled or not. But certain platform may need to read non-SMM
> content from SMM code. These platforms don't have a way to disable
> the read-out blocking.
>
> The
From: Jiewen Yao
Today's implementation blocks SMM read-out no matter static paging
is enabled or not. But certain platform may need to read non-SMM
content from SMM code. These platforms don't have a way to disable
the read-out blocking.
The patch updates the policy to only block SMM read-out
6 matches
Mail list logo
