From: Laszlo Ersek <lersek@redhat.com>
To: Star Zeng <star.zeng@intel.com>, edk2-devel@lists.01.org
Cc: Jiewen Yao <jiewen.yao@intel.com>,
Eric Dong <eric.dong@intel.com>, Ruiyu Ni <ruiyu.ni@intel.com>
Subject: Re: [PATCH] UefiCpuPkg PiSmmCpuDxeSmm: Only DumpCpuContext in error case
Date: Thu, 7 Dec 2017 12:12:59 +0100 [thread overview]
Message-ID: <0849d664-f963-01e9-8f61-eac7786525e2@redhat.com> (raw)
In-Reply-To: <1512611363-14196-1-git-send-email-star.zeng@intel.com>
On 12/07/17 02:49, Star Zeng wrote:
> Only DumpCpuContext in error case, otherwise there will be too many
> debug messages from DumpCpuContext() when SmmProfile feature is enabled
> by setting PcdCpuSmmProfileEnable to TRUE. Those debug messages are not
> needed for SmmProfile feature as it will record those information to
> buffer for further dump.
>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Eric Dong <eric.dong@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Cc: Ruiyu Ni <ruiyu.ni@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Star Zeng <star.zeng@intel.com>
> ---
> UefiCpuPkg/PiSmmCpuDxeSmm/Ia32/PageTbl.c | 6 ++++--
> UefiCpuPkg/PiSmmCpuDxeSmm/X64/PageTbl.c | 6 ++++--
> 2 files changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/UefiCpuPkg/PiSmmCpuDxeSmm/Ia32/PageTbl.c b/UefiCpuPkg/PiSmmCpuDxeSmm/Ia32/PageTbl.c
> index 0396f2daaaed..6e1ffe7c6287 100644
> --- a/UefiCpuPkg/PiSmmCpuDxeSmm/Ia32/PageTbl.c
> +++ b/UefiCpuPkg/PiSmmCpuDxeSmm/Ia32/PageTbl.c
> @@ -134,12 +134,12 @@ SmiPFHandler (
> }
>
> //
> - // If a page fault occurs in SMM range
> + // If a page fault occurs in non-SMRAM range.
> //
> if ((PFAddress < mCpuHotPlugData.SmrrBase) ||
> (PFAddress >= mCpuHotPlugData.SmrrBase + mCpuHotPlugData.SmrrSize)) {
> - DumpCpuContext (InterruptType, SystemContext);
> if ((SystemContext.SystemContextIa32->ExceptionData & IA32_PF_EC_ID) != 0) {
> + DumpCpuContext (InterruptType, SystemContext);
> DEBUG ((DEBUG_ERROR, "Code executed on IP(0x%x) out of SMM range after SMM is locked!\n", PFAddress));
> DEBUG_CODE (
> DumpModuleInfoByIp (*(UINTN *)(UINTN)SystemContext.SystemContextIa32->Esp);
> @@ -147,6 +147,7 @@ SmiPFHandler (
> CpuDeadLoop ();
> }
> if (IsSmmCommBufferForbiddenAddress (PFAddress)) {
> + DumpCpuContext (InterruptType, SystemContext);
> DEBUG ((DEBUG_ERROR, "Access SMM communication forbidden address (0x%x)!\n", PFAddress));
> DEBUG_CODE (
> DumpModuleInfoByIp ((UINTN)SystemContext.SystemContextIa32->Eip);
> @@ -160,6 +161,7 @@ SmiPFHandler (
> //
> if ((PcdGet8 (PcdNullPointerDetectionPropertyMask) & BIT1) != 0 &&
> (PFAddress < EFI_PAGE_SIZE)) {
> + DumpCpuContext (InterruptType, SystemContext);
> DEBUG ((DEBUG_ERROR, "!!! NULL pointer access !!!\n"));
> DEBUG_CODE (
> DumpModuleInfoByIp ((UINTN)SystemContext.SystemContextIa32->Eip);
> diff --git a/UefiCpuPkg/PiSmmCpuDxeSmm/X64/PageTbl.c b/UefiCpuPkg/PiSmmCpuDxeSmm/X64/PageTbl.c
> index 79a26d7ec6a3..6478c6c3e355 100644
> --- a/UefiCpuPkg/PiSmmCpuDxeSmm/X64/PageTbl.c
> +++ b/UefiCpuPkg/PiSmmCpuDxeSmm/X64/PageTbl.c
> @@ -851,12 +851,12 @@ SmiPFHandler (
> }
>
> //
> - // If a page fault occurs in SMM range
> + // If a page fault occurs in non-SMRAM range.
> //
> if ((PFAddress < mCpuHotPlugData.SmrrBase) ||
> (PFAddress >= mCpuHotPlugData.SmrrBase + mCpuHotPlugData.SmrrSize)) {
> - DumpCpuContext (InterruptType, SystemContext);
> if ((SystemContext.SystemContextX64->ExceptionData & IA32_PF_EC_ID) != 0) {
> + DumpCpuContext (InterruptType, SystemContext);
> DEBUG ((DEBUG_ERROR, "Code executed on IP(0x%lx) out of SMM range after SMM is locked!\n", PFAddress));
> DEBUG_CODE (
> DumpModuleInfoByIp (*(UINTN *)(UINTN)SystemContext.SystemContextX64->Rsp);
> @@ -864,6 +864,7 @@ SmiPFHandler (
> CpuDeadLoop ();
> }
> if (IsSmmCommBufferForbiddenAddress (PFAddress)) {
> + DumpCpuContext (InterruptType, SystemContext);
> DEBUG ((DEBUG_ERROR, "Access SMM communication forbidden address (0x%lx)!\n", PFAddress));
> DEBUG_CODE (
> DumpModuleInfoByIp ((UINTN)SystemContext.SystemContextX64->Rip);
> @@ -877,6 +878,7 @@ SmiPFHandler (
> //
> if ((PcdGet8 (PcdNullPointerDetectionPropertyMask) & BIT1) != 0 &&
> (PFAddress < EFI_PAGE_SIZE)) {
> + DumpCpuContext (InterruptType, SystemContext);
> DEBUG ((DEBUG_ERROR, "!!! NULL pointer access !!!\n"));
> DEBUG_CODE (
> DumpModuleInfoByIp ((UINTN)SystemContext.SystemContextX64->Rip);
>
Looks reasonable to me.
Acked-by: Laszlo Ersek <lersek@redhat.com>
Thanks!
Laszlo
prev parent reply other threads:[~2017-12-07 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 1:49 [PATCH] UefiCpuPkg PiSmmCpuDxeSmm: Only DumpCpuContext in error case Star Zeng
2017-12-07 3:01 ` Dong, Eric
2017-12-07 3:03 ` Yao, Jiewen
2017-12-07 3:03 ` Zeng, Star
2017-12-07 11:12 ` Laszlo Ersek [this message]
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=0849d664-f963-01e9-8f61-eac7786525e2@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