From: "Wu, Hao A" <hao.a.wu@intel.com>
To: "Chu, Maggie" <maggie.chu@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Wang, Jian J" <jian.j.wang@intel.com>,
"Ni, Ray" <ray.ni@intel.com>, "Zeng, Star" <star.zeng@intel.com>,
"Dong, Eric" <eric.dong@intel.com>
Subject: Re: [PATCH] MdeModulePkg/NvmExpressPei: Fix Opal S3 unlock issue
Date: Mon, 28 Oct 2019 05:42:59 +0000 [thread overview]
Message-ID: <B80AF82E9BFB8E4FBD8C89DA810C6A093C953C26@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20191028050802.856-1-maggie.chu@intel.com>
> -----Original Message-----
> From: Chu, Maggie
> Sent: Monday, October 28, 2019 1:08 PM
> To: devel@edk2.groups.io
> Cc: Wu, Hao A; Wang, Jian J; Ni, Ray; Zeng, Star; Dong, Eric
> Subject: [PATCH] MdeModulePkg/NvmExpressPei: Fix Opal S3 unlock issue
>
> https://bugzilla.tianocore.org/show_bug.cgi?id=2312
>
> This patch is for fixing unexpected system hang during S3 unlock process.
> FatPei driver maintained and updated internal BlockIo devices list
> when there is new BlockIo PPI has installed, and it relied on BlockIo PPI service
> to get data from devices. Because BlockIo Ppi leverage NvmExpressPei Ppi to
> transit
> Nvm command to device, we should make sure NvmePassThruPpi installed
> before BlockIo PPI.
The change is good to me,
Reviewed-by: Hao A Wu <hao.a.wu@intel.com>
If no other comment, I will adjust the length of some commit log message lines
when pushing this patch, since the PatchCheck.py script is complaining:
The commit message format is not valid:
* Line 7 of commit message is too long.
* Line 8 of commit message is too long.
* Line 9 of commit message is too long.
Best Regards,
Hao Wu
>
> Signed-off-by: Maggie Chu <maggie.chu@intel.com>
> Cc: Hao A Wu <hao.a.wu@intel.com>
> Cc: Jian J Wang <jian.j.wang@intel.com>
> Cc: Ray Ni <ray.ni@intel.com>
> Cc: Star Zeng <star.zeng@intel.com>
> Cc: Eric Dong <eric.dong@intel.com>
> ---
> MdeModulePkg/Bus/Pci/NvmExpressPei/NvmExpressPei.c | 43 ++++++++++++-
> ---------
> 1 file changed, 23 insertions(+), 20 deletions(-)
>
> diff --git a/MdeModulePkg/Bus/Pci/NvmExpressPei/NvmExpressPei.c
> b/MdeModulePkg/Bus/Pci/NvmExpressPei/NvmExpressPei.c
> index 987eed420e..a8cb7f3a67 100644
> --- a/MdeModulePkg/Bus/Pci/NvmExpressPei/NvmExpressPei.c
> +++ b/MdeModulePkg/Bus/Pci/NvmExpressPei/NvmExpressPei.c
> @@ -376,6 +376,29 @@ NvmExpressPeimEntry (
> continue;
>
> }
>
>
>
> + //
>
> + // Nvm Express Pass Thru PPI
>
> + //
>
> + Private->PassThruMode.Attributes =
> EFI_NVM_EXPRESS_PASS_THRU_ATTRIBUTES_PHYSICAL |
>
> +
> EFI_NVM_EXPRESS_PASS_THRU_ATTRIBUTES_LOGICAL |
>
> +
> EFI_NVM_EXPRESS_PASS_THRU_ATTRIBUTES_CMD_SET_NVM;
>
> + Private->PassThruMode.IoAlign = sizeof (UINTN);
>
> + Private->PassThruMode.NvmeVersion =
> EDKII_PEI_NVM_EXPRESS_PASS_THRU_PPI_REVISION;
>
> + Private->NvmePassThruPpi.Mode = &Private->PassThruMode;
>
> + Private->NvmePassThruPpi.GetDevicePath =
> NvmePassThruGetDevicePath;
>
> + Private->NvmePassThruPpi.GetNextNameSpace =
> NvmePassThruGetNextNameSpace;
>
> + Private->NvmePassThruPpi.PassThru = NvmePassThru;
>
> + CopyMem (
>
> + &Private->NvmePassThruPpiList,
>
> + &mNvmePassThruPpiListTemplate,
>
> + sizeof (EFI_PEI_PPI_DESCRIPTOR)
>
> + );
>
> + Private->NvmePassThruPpiList.Ppi = &Private->NvmePassThruPpi;
>
> + PeiServicesInstallPpi (&Private->NvmePassThruPpiList);
>
> +
>
> + //
>
> + // Block Io PPI
>
> + //
>
> Private->BlkIoPpi.GetNumberOfBlockDevices =
> NvmeBlockIoPeimGetDeviceNo;
>
> Private->BlkIoPpi.GetBlockDeviceMediaInfo =
> NvmeBlockIoPeimGetMediaInfo;
>
> Private->BlkIoPpi.ReadBlocks = NvmeBlockIoPeimReadBlocks;
>
> @@ -398,26 +421,6 @@ NvmExpressPeimEntry (
> Private->BlkIo2PpiList.Ppi = &Private->BlkIo2Ppi;
>
> PeiServicesInstallPpi (&Private->BlkIoPpiList);
>
>
>
> - //
>
> - // Nvm Express Pass Thru PPI
>
> - //
>
> - Private->PassThruMode.Attributes =
> EFI_NVM_EXPRESS_PASS_THRU_ATTRIBUTES_PHYSICAL |
>
> -
> EFI_NVM_EXPRESS_PASS_THRU_ATTRIBUTES_LOGICAL |
>
> -
> EFI_NVM_EXPRESS_PASS_THRU_ATTRIBUTES_CMD_SET_NVM;
>
> - Private->PassThruMode.IoAlign = sizeof (UINTN);
>
> - Private->PassThruMode.NvmeVersion =
> EDKII_PEI_NVM_EXPRESS_PASS_THRU_PPI_REVISION;
>
> - Private->NvmePassThruPpi.Mode = &Private->PassThruMode;
>
> - Private->NvmePassThruPpi.GetDevicePath =
> NvmePassThruGetDevicePath;
>
> - Private->NvmePassThruPpi.GetNextNameSpace =
> NvmePassThruGetNextNameSpace;
>
> - Private->NvmePassThruPpi.PassThru = NvmePassThru;
>
> - CopyMem (
>
> - &Private->NvmePassThruPpiList,
>
> - &mNvmePassThruPpiListTemplate,
>
> - sizeof (EFI_PEI_PPI_DESCRIPTOR)
>
> - );
>
> - Private->NvmePassThruPpiList.Ppi = &Private->NvmePassThruPpi;
>
> - PeiServicesInstallPpi (&Private->NvmePassThruPpiList);
>
> -
>
> //
>
> // Check if the NVME controller supports the Security Receive/Send
> commands
>
> //
>
> --
> 2.16.2.windows.1
next prev parent reply other threads:[~2019-10-28 5:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 5:08 [PATCH] MdeModulePkg/NvmExpressPei: Fix Opal S3 unlock issue Maggie Chu
2019-10-28 5:42 ` Wu, Hao A [this message]
2019-10-30 0:22 ` [edk2-devel] " Wu, Hao A
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=B80AF82E9BFB8E4FBD8C89DA810C6A093C953C26@SHSMSX104.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