From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
"Dong, Eric" <eric.dong@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Ni, Ruiyu" <ruiyu.ni@intel.com>
Subject: Re: [Patch] UefiCpuPkg/S3Resume2Pei: disable paging before creating new page table.
Date: Wed, 10 Oct 2018 13:14:22 +0000 [thread overview]
Message-ID: <74D8A39837DF1E4DA445A8C0B3885C503ADDC8E0@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <5af8d5f4-1cc2-747f-16b0-71f5bc9aee9e@redhat.com>
Good idea, Laszlo.
If we know something will fail, we had better make it fail as early as possible, and as obvious as possible.
I think we can do sth in INF:
1) Change # VALID_ARCHITECTURES = IA32
2) Change:
[Sources.IA32]
S3Resume.c
and remove [Sources.X64]
If we decide to enable X64 S3Resume, we can go back and add such support.
Thank you
Yao Jiewen
> -----Original Message-----
> From: Laszlo Ersek [mailto:lersek@redhat.com]
> Sent: Wednesday, October 10, 2018 9:04 PM
> To: Yao, Jiewen <jiewen.yao@intel.com>; Dong, Eric <eric.dong@intel.com>;
> edk2-devel@lists.01.org
> Cc: Ni, Ruiyu <ruiyu.ni@intel.com>
> Subject: Re: [edk2] [Patch] UefiCpuPkg/S3Resume2Pei: disable paging
> before creating new page table.
>
> On 10/10/18 09:58, Yao, Jiewen wrote:
> > Hey
> > I do not think we need add if (sizeof (UINTN) == sizeof (UINT32))
> >
> > This piece of code assume PEI is 32 bit.
> > The following code AsmEnablePaging64() does not work for X64.
>
> I don't feel strongly about this particular question. Any decent
> compiler will optimize away the UINTN size check, and IIRC Ray suggested
> under v1 to explicitly restrict the new code to 32-bit. (Although, we
> both confirmed that this PEIM only supported 32-bit PEI with SMM.)
>
> Now, if the code is *clearly* restricted to 32-bit already -- do we
> *declare* that fact somewhere? in the code or in the INF file? --, then
> I agree we might not need the UINTN size check.
>
> ... Maybe we should split this driver into [Sources.IA32] and
> [Sources.X64] more extensively that we currently do, and make the
> X64+SMM case fail more *obviously* than it currently does.
>
> I'll leave it up to you guys to decide if the UINTN size check should be
> preserved in this patch. Once you have an agreement, I'd like to
> regression-test the resultant version of the patch.
>
> FWIW, this version (v4) does look good to me. Should Jiewen think the
> UINTN size check is acceptable after all, I'd be ready to give my R-b
> (and to regression-test the patch as well).
>
> Thanks!
> Laszlo
>
> >
> > Thank you
> > Yao Jiewen
> >
> >> -----Original Message-----
> >> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> >> Eric Dong
> >> Sent: Wednesday, October 10, 2018 3:44 PM
> >> To: edk2-devel@lists.01.org
> >> Cc: Ni, Ruiyu <ruiyu.ni@intel.com>; Laszlo Ersek <lersek@redhat.com>
> >> Subject: [edk2] [Patch] UefiCpuPkg/S3Resume2Pei: disable paging before
> >> creating new page table.
> >>
> >> V4:
> >> Only disable paging when it is enabled.
> >>
> >> V3 changes:
> >> No need to change inf file.
> >>
> >> V2 changes:
> >> Only disable paging in 32 bit mode, no matter it is enable or not.
> >>
> >> V1 changes:
> >> PEI Stack Guard needs to enable paging. This might cause #GP if code
> >> trying to write CR3 register with PML4 page table while the processor
> >> is enabled with PAE paging.
> >>
> >> Simply disabling paging before updating CR3 can solve this conflict.
> >>
> >> It's an regression caused by change:
> >> 0a0d5296e448fc350de1594c49b9c0deff7fad60
> >>
> >> BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=1232
> >>
> >> Change-Id: I99bfdba5daa48a95a4c4ef97eeca1af086558957
> >> Cc: Ruiyu Ni <ruiyu.ni@intel.com>
> >> Cc: Laszlo Ersek <lersek@redhat.com>
> >> Cc: Jian J Wang <jian.j.wang@intel.com>
> >> Contributed-under: TianoCore Contribution Agreement 1.1
> >> Signed-off-by:Eric Dong <eric.dong@intel.com>
> >> Signed-off-by: Eric Dong <eric.dong@intel.com>
> >> ---
> >> UefiCpuPkg/Universal/Acpi/S3Resume2Pei/S3Resume.c | 12
> ++++++++++++
> >> 1 file changed, 12 insertions(+)
> >>
> >> diff --git a/UefiCpuPkg/Universal/Acpi/S3Resume2Pei/S3Resume.c
> >> b/UefiCpuPkg/Universal/Acpi/S3Resume2Pei/S3Resume.c
> >> index f164c1713b..c059c42db5 100644
> >> --- a/UefiCpuPkg/Universal/Acpi/S3Resume2Pei/S3Resume.c
> >> +++ b/UefiCpuPkg/Universal/Acpi/S3Resume2Pei/S3Resume.c
> >> @@ -964,6 +964,7 @@ S3RestoreConfig2 (
> >> VOID *GuidHob;
> >> BOOLEAN
> >> Build4GPageTableOnly;
> >> BOOLEAN
> >> InterruptStatus;
> >> + IA32_CR0 CR0Reg;
> >>
> >> TempAcpiS3Context = 0;
> >> TempEfiBootScriptExecutorVariable = 0;
> >> @@ -1105,6 +1106,17 @@ S3RestoreConfig2 (
> >> //
> >> SetInterruptState (InterruptStatus);
> >>
> >> + if (sizeof (UINTN) == sizeof (UINT32)) {
> >> + CR0Reg.UintN = AsmReadCr0 ();
> >> + if (CR0Reg.Bits.PG != 0) {
> >> + //
> >> + // We're in 32-bit mode, with paging enabled. We can't set
> CR3
> >> to
> >> + // the 64-bit page tables without first disabling paging.
> >> + //
> >> + CR0Reg.Bits.PG = 0;
> >> + AsmWriteCr0 (CR0Reg.UintN);
> >> + }
> >> + }
> >> AsmWriteCr3 ((UINTN)SmmS3ResumeState->SmmS3Cr3);
> >>
> >> //
> >> --
> >> 2.15.0.windows.1
> >>
> >> _______________________________________________
> >> edk2-devel mailing list
> >> edk2-devel@lists.01.org
> >> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-10-10 13:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 7:43 [Patch] UefiCpuPkg/S3Resume2Pei: disable paging before creating new page table Eric Dong
2018-10-10 7:58 ` Yao, Jiewen
2018-10-10 13:03 ` Laszlo Ersek
2018-10-10 13:14 ` Yao, Jiewen [this message]
2018-10-10 13:19 ` Laszlo Ersek
2018-10-10 13:30 ` Yao, Jiewen
2018-10-10 14:00 ` Laszlo Ersek
-- strict thread matches above, loose matches on Subject: below --
2018-10-09 1:51 Eric Dong
2018-10-09 1:59 ` Wang, Jian J
2018-10-09 2:03 ` Wang, Jian J
2018-10-09 2:27 ` Dong, Eric
2018-10-09 2:05 ` Dong, Eric
2018-10-09 2:15 ` Ni, Ruiyu
2018-10-09 8:09 ` Laszlo Ersek
2018-10-09 8:26 ` Ni, Ruiyu
2018-10-09 8:54 ` Laszlo Ersek
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=74D8A39837DF1E4DA445A8C0B3885C503ADDC8E0@shsmsx102.ccr.corp.intel.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