public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Oliver Smith-Denny" <osde@linux.microsoft.com>
To: devel@edk2.groups.io, ray.ni@intel.com
Cc: "Wu, Hao A" <hao.a.wu@intel.com>,
	"Wang, Jian J" <jian.j.wang@intel.com>,
	"Gao, Liming" <gaoliming@byosoft.com.cn>,
	Michael Kubacki <mikuback@linux.microsoft.com>,
	Sean Brogan <sean.brogan@microsoft.com>
Subject: Re: [edk2-devel] [PATCH v1 1/2] Add the volatile keyword to NvmExpressDxe's Passthru CQs and SQs.
Date: Thu, 20 Apr 2023 08:48:20 -0700	[thread overview]
Message-ID: <a9c32721-b580-6ad4-dcfd-68f7520c3f70@linux.microsoft.com> (raw)
In-Reply-To: <MN6PR11MB8244770AC8A27004206B17498C639@MN6PR11MB8244.namprd11.prod.outlook.com>

Hi Ray,

This is not a pure copy from HW to SW memory, we are also
polling the CQ to see if a transaction has completed:

   //
   // Wait for completion queue to get filled in.
   //
   Status = EFI_TIMEOUT;
   while (EFI_ERROR (gBS->CheckEvent (TimerEvent))) {
     if (Cq->Pt != Private->Pt[QueueId]) {
       Status = EFI_SUCCESS;
       break;
     }
   }


What we have seen happen is that without the volatile
keyword, the compiler can move the Cq->Pt read outside
of the loop and only do register compares inside the loop,
i.e. we end up going the full timeout even if the CQ reports
it is finished.

Here is the issue that was filed on the project Mu side:
https://github.com/microsoft/mu_basecore/issues/324.

Thanks,
Oliver

On 4/19/2023 5:48 PM, Ni, Ray wrote:
> If it's to copy from hw to sw memory, why do we need volatile?
> 
> Thanks,
> Ray
> 
>> -----Original Message-----
>> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Oliver
>> Smith-Denny
>> Sent: Thursday, April 20, 2023 7:41 AM
>> To: devel@edk2.groups.io
>> Cc: Wu, Hao A <hao.a.wu@intel.com>; Ni, Ray <ray.ni@intel.com>; Wang,
>> Jian J <jian.j.wang@intel.com>; Gao, Liming <gaoliming@byosoft.com.cn>;
>> Michael Kubacki <mikuback@linux.microsoft.com>; Sean Brogan
>> <sean.brogan@microsoft.com>
>> Subject: [edk2-devel][PATCH v1 1/2] Add the volatile keyword to
>> NvmExpressDxe's Passthru CQs and SQs.
>>
>> This updates the relevant functions that expect a non-volatile
>>
>> structure to be passed to them to take casts of the CQ and SQ,
>>
>> now that they are volatile.
>>
>>
>>
>> Cc: Hao A Wu <hao.a.wu@intel.com>
>>
>> Cc: Ray Ni <ray.ni@intel.com>
>>
>> Cc: Jian J Wang <jian.j.wang@intel.com>
>>
>> Cc: Liming Gao <gaoliming@byosoft.com.cn>
>>
>> Cc: Michael Kubacki <mikuback@linux.microsoft.com>
>>
>> Cc: Sean Brogan <sean.brogan@microsoft.com>
>>
>> Signed-off-by: Oliver Smith-Denny <osde@linux.microsoft.com>
>>
>> ---
>>
>>   MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpressPassthru.c | 10
>> +++++-----
>>
>>   1 file changed, 5 insertions(+), 5 deletions(-)
>>
>>
>>
>> diff --git a/MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpressPassthru.c
>> b/MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpressPassthru.c
>>
>> index f37baa626a16..1a7e39500ac0 100644
>>
>> --- a/MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpressPassthru.c
>>
>> +++ b/MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpressPassthru.c
>>
>> @@ -459,8 +459,8 @@ NvmExpressPassThru (
>>
>>     EFI_STATUS                     Status;
>>
>>     EFI_STATUS                     PreviousStatus;
>>
>>     EFI_PCI_IO_PROTOCOL            *PciIo;
>>
>> -  NVME_SQ                        *Sq;
>>
>> -  NVME_CQ                        *Cq;
>>
>> +  volatile NVME_SQ               *Sq;
>>
>> +  volatile NVME_CQ               *Cq;
>>
>>     UINT16                         QueueId;
>>
>>     UINT16                         QueueSize;
>>
>>     UINT32                         Bytes;
>>
>> @@ -581,7 +581,7 @@ NvmExpressPassThru (
>>
>>       return EFI_INVALID_PARAMETER;
>>
>>     }
>>
>>
>>
>> -  ZeroMem (Sq, sizeof (NVME_SQ));
>>
>> +  ZeroMem ((VOID *)Sq, sizeof (NVME_SQ));
>>
>>     Sq->Opc  = (UINT8)Packet->NvmeCmd->Cdw0.Opcode;
>>
>>     Sq->Fuse = (UINT8)Packet->NvmeCmd->Cdw0.FusedOperation;
>>
>>     Sq->Cid  = Private->Cid[QueueId]++;
>>
>> @@ -815,14 +815,14 @@ NvmExpressPassThru (
>>
>>         // Dump every completion entry status for debugging.
>>
>>         //
>>
>>         DEBUG_CODE_BEGIN ();
>>
>> -      NvmeDumpStatus (Cq);
>>
>> +      NvmeDumpStatus ((NVME_CQ *)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));
>>
>> +    CopyMem (Packet->NvmeCompletion, (VOID *)Cq, sizeof
>> (EFI_NVM_EXPRESS_COMPLETION));
>>
>>     } else {
>>
>>       //
>>
>>       // Timeout occurs for an NVMe command. Reset the controller to abort
>> the
>>
>> --
>>
>> 2.39.2
>>
>>
>>
>>
>>
>> -=-=-=-=-=-=
>> Groups.io Links: You receive all messages sent to this group.
>> View/Reply Online (#103263):
>> https://edk2.groups.io/g/devel/message/103263
>> Mute This Topic: https://groups.io/mt/98378948/1712937
>> Group Owner: devel+owner@edk2.groups.io
>> Unsubscribe: https://edk2.groups.io/g/devel/unsub [ray.ni@intel.com]
>> -=-=-=-=-=-=
>>
> 
> 
> 
> 
> 

  reply	other threads:[~2023-04-20 15:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 23:41 [edk2-devel][PATCH v1 0/2] MdeModulePkg: Add Volatile Keyword to NvmExpress Passthru CQs and SQs Oliver Smith-Denny
2023-04-19 23:41 ` [edk2-devel][PATCH v1 1/2] Add the volatile keyword to NvmExpressDxe's " Oliver Smith-Denny
2023-04-20  0:48   ` Ni, Ray
2023-04-20 15:48     ` Oliver Smith-Denny [this message]
2023-04-26  6:32       ` [edk2-devel] [PATCH " Wu, Hao A
2023-04-26 21:06         ` Oliver Smith-Denny
2023-04-27  1:27           ` Wu, Hao A
2023-04-19 23:41 ` [edk2-devel][PATCH v1 2/2] Add volatile keyword to NvmExpressPei's " Oliver Smith-Denny

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=a9c32721-b580-6ad4-dcfd-68f7520c3f70@linux.microsoft.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