From: "Ni, Ruiyu" <ruiyu.ni@Intel.com>
To: Hao Wu <hao.a.wu@intel.com>, edk2-devel@lists.01.org
Cc: Liangcheng Tang <liangcheng.tang@intel.com>,
Star Zeng <star.zeng@intel.com>
Subject: Re: [PATCH v1 2/3] MdeModulePkg/NvmExpressDxe: Always copy CQ entry to PassThru packet
Date: Tue, 23 Oct 2018 16:54:09 +0800 [thread overview]
Message-ID: <ef33269f-8dd0-3d8b-dfba-c140bb6b95ed@Intel.com> (raw)
In-Reply-To: <20181018064200.2068-3-hao.a.wu@intel.com>
On 10/18/2018 2:41 PM, Hao Wu wrote:
> REF:https://bugzilla.tianocore.org/show_bug.cgi?id=1259
>
> According to the the NVM Express spec Revision 1.1, for some commands,
> command-related information will be stored in the Dword 0 of the
> completion queue entry.
>
> One case is for the Get Features Command (Section 5.9.2 of the spec),
> Dword 0 of the completion queue entry may contain feature information.
>
> Hence, this commit will always copy the content of completion queue entry
> to the PassThru packet regardless of the execution result of the command.
>
> Cc: Liangcheng Tang <liangcheng.tang@intel.com>
> Cc: Ruiyu Ni <ruiyu.ni@intel.com>
> Cc: Star Zeng <star.zeng@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Hao Wu <hao.a.wu@intel.com>
> ---
> MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpressPassthru.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpressPassthru.c b/MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpressPassthru.c
> index bfcd349794..c52e960771 100644
> --- a/MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpressPassthru.c
> +++ b/MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpressPassthru.c
> @@ -781,17 +781,16 @@ NvmExpressPassThru (
> } else {
> Status = EFI_DEVICE_ERROR;
> //
> - // Copy the Respose Queue entry for this command to the callers response buffer
> - //
> - CopyMem(Packet->NvmeCompletion, Cq, sizeof(EFI_NVM_EXPRESS_COMPLETION));
> -
> - //
> // Dump every completion entry status for debugging.
> //
> DEBUG_CODE_BEGIN();
> NvmeDumpStatus(Cq);
> DEBUG_CODE_END();
> }
> + //
> + // Copy the Respose Queue entry for this command to the callers response buffer
> + //
> + CopyMem(Packet->NvmeCompletion, Cq, sizeof(EFI_NVM_EXPRESS_COMPLETION));
> } else {
> //
> // Timeout occurs for an NVMe command. Reset the controller to abort the
>
Reviewed-by: Ruiyu Ni <ruiyu.ni@intel.com>
--
Thanks,
Ray
next prev parent reply other threads:[~2018-10-23 8:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 6:41 [PATCH v1 0/3] NvmExpressDxe: Bug fixes within NvmExpressPassThru() Hao Wu
2018-10-18 6:41 ` [PATCH v1 1/3] MdeModulePkg/NvmExpressDxe: Refine data buffer & len check in PassThru Hao Wu
2018-10-23 8:53 ` Ni, Ruiyu
2018-10-18 6:41 ` [PATCH v1 2/3] MdeModulePkg/NvmExpressDxe: Always copy CQ entry to PassThru packet Hao Wu
2018-10-23 8:54 ` Ni, Ruiyu [this message]
2018-10-18 6:42 ` [PATCH v1 3/3] MdeModulePkg/NvmExpressDxe: Refine PassThru IO queue creation behavior Hao Wu
2018-10-23 8:53 ` Ni, Ruiyu
2018-10-24 0:59 ` 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=ef33269f-8dd0-3d8b-dfba-c140bb6b95ed@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