public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Chen, ArvinX" <arvinx.chen@intel.com>
To: Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: G Edhaya Chandran <Edhaya.Chandran@arm.com>,
	"Jin, Eric" <eric.jin@intel.com>,
	"gaoliming@byosoft.com.cn" <gaoliming@byosoft.com.cn>,
	"Chu, Maggie" <maggie.chu@intel.com>
Subject: 回覆: [edk2-devel] [PATCH 2/2] uefi-sct/SctPkg: Correct BBTestEraseBlocks behavior (EFI_BLOCK_IO_PROTOCOL)
Date: Tue, 17 Nov 2020 05:51:02 +0000	[thread overview]
Message-ID: <DM5PR11MB17378A3545211C3C08578AE1FBE20@DM5PR11MB1737.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DB7PR08MB326061759136436F8C78F63F90E80@DB7PR08MB3260.eurprd08.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 8769 bytes --]

HI Samer,

    Sorry for the slow reply, In EMMC's case, it allowed storage firmware erase to "1" to be a valid behavior (please reference the spec of emmc JESD84-B51/6.6.9), so once verification team use kind of this device, the test case will always failed. To avoid this problem, I think this change is required.

Thanks!!
Arvin

________________________________
寄件者: Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
寄件日期: 2020年11月12日 上午 04:56
收件者: devel@edk2.groups.io <devel@edk2.groups.io>; Chen, ArvinX <arvinx.chen@intel.com>
副本: G Edhaya Chandran <Edhaya.Chandran@arm.com>; Jin, Eric <eric.jin@intel.com>; Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>; gaoliming@byosoft.com.cn <gaoliming@byosoft.com.cn>
主旨: RE: [edk2-devel] [PATCH 2/2] uefi-sct/SctPkg: Correct BBTestEraseBlocks behavior (EFI_BLOCK_IO_PROTOCOL)

Hi Chen,

The UEFI Specification 2.8ErrataB (page 575) states that " It is the intention of the EraseBlocks() operation to be at least as performant as writing zeroes to each of the specified LBA locations while ensuring the equivalent security."

So while not explicitly saying that Erase should "erase to 0", it implies that at least is the intention. Do we know that erasing to "1" is a valid behavior?



> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Chen,
> ArvinX via groups.io
> Sent: Monday, November 2, 2020 5:00 AM
> To: devel@edk2.groups.io
> Cc: G Edhaya Chandran <Edhaya.Chandran@arm.com>; Eric Jin
> <eric.jin@intel.com>
> Subject: [edk2-devel] [PATCH 2/2] uefi-sct/SctPkg: Correct
> BBTestEraseBlocks behavior (EFI_BLOCK_IO_PROTOCOL)
>
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3022
>
>
>
> The storage device erase behavior may have two possibilities:
>
>  1.Write all data into "0"
>
>  2.Write all data into "1"
>
> but now tool behavior can only check case 1 (Write all data into "0"),
>
> so we need add the other case into SCT tool to correct the test behavior.
>
>
>
> Cc: G Edhaya Chandran <Edhaya.Chandran@arm.com>
>
> Cc: Eric Jin <eric.jin@intel.com>
>
> Signed-off-by: ArvinX Chen <arvinx.chen@intel.com>
>
> ---
>
>  .../BlackBoxTest/EraseBlockBBTestFunction.c   | 55 +++++++++++++++----
>
>  1 file changed, 43 insertions(+), 12 deletions(-)
>
>
>
> diff --git a/uefi-
> sct/SctPkg/TestCase/UEFI/EFI/Protocol/EraseBlock/BlackBoxTest/EraseBlock
> BBTestFunction.c b/uefi-
> sct/SctPkg/TestCase/UEFI/EFI/Protocol/EraseBlock/BlackBoxTest/EraseBlock
> BBTestFunction.c
>
> index cbf43e1d..dbbb70c6 100644
>
> --- a/uefi-
> sct/SctPkg/TestCase/UEFI/EFI/Protocol/EraseBlock/BlackBoxTest/EraseBlock
> BBTestFunction.c
>
> +++ b/uefi-
> sct/SctPkg/TestCase/UEFI/EFI/Protocol/EraseBlock/BlackBoxTest/EraseBlock
> BBTestFunction.c
>
> @@ -71,6 +71,7 @@ BBTestEraseBlocksFunctionTest (
>
>    UINT64                                Index;
>
>    UINTN                                 Index1;
>
>    UINTN                                 Remainder;
>
> +  UINT64                                EraseCounter;
>
>
>
>    EFI_ERASE_BLOCK_TOKEN                 Token;
>
>    EFI_BLOCK_IO2_TOKEN                   BlockIo2Token;
>
> @@ -223,26 +224,41 @@ BBTestEraseBlocksFunctionTest (
>
>          // Read the data with 0, the first/last block should not be erased
>
>          ReadStatus = BlockIo->ReadBlocks (BlockIo, MediaId, Lba, BufferSize,
> (VOID*)Buffer2);
>
>          if (ReadStatus == EFI_SUCCESS) {
>
> -          for (Index1 = 0; Index1 < BlockSize; Index1++) {
>
> -            if (Buffer2[Index1] != 0) {
>
> +          for (Index1 = 0, EraseCounter = 0; Index1 < BlockSize; Index1++) {
>
> +            if (Buffer2[Index1] != 0x00 && Buffer2[Index1] != 0xFF) {
>
>                IsZero1 = FALSE;
>
>                break;
>
> +            } else if (Buffer2[Index1] == 0x00) {
>
> +              EraseCounter++;
>
>              }
>
>            }
>
> +          if (EraseCounter!=0 && EraseCounter!=BlockSize) {
>
> +            IsZero1 = FALSE;
>
> +          }
>
>
>
> -          for (Index1 = BlockSize; Index1 < BufferSize - BlockSize; Index1++) {
>
> -            if (Buffer2[Index1] != 0) {
>
> +          for (Index1 = BlockSize, EraseCounter = 0; Index1 < BufferSize -
> BlockSize; Index1++) {
>
> +            if (Buffer2[Index1] != 0x00 && Buffer2[Index1] != 0xFF) {
>
>                IsZero2 = FALSE;
>
>                break;
>
> +            } else if (Buffer2[Index1] == 0x00) {
>
> +              EraseCounter++;
>
>              }
>
>            }
>
> +          if (EraseCounter!=0 && EraseCounter!=(BufferSize - (BlockSize*2))) {
>
> +            IsZero2 = FALSE;
>
> +          }
>
>
>
> -          for (Index1 = BufferSize - BlockSize; Index1 < BufferSize; Index1++) {
>
> -            if (Buffer2[Index1] != 0) {
>
> +          for (Index1 = BufferSize - BlockSize, EraseCounter = 0; Index1 <
> BufferSize; Index1++) {
>
> +            if (Buffer2[Index1] != 0x00 && Buffer2[Index1] != 0xFF) {
>
>                IsZero3 = FALSE;
>
>                break;
>
> +            } else if (Buffer2[Index1] == 0x00) {
>
> +              EraseCounter++;
>
>              }
>
>            }
>
> +          if (EraseCounter!=0 && EraseCounter!=BlockSize) {
>
> +            IsZero3 = FALSE;
>
> +          }
>
>
>
>            if ((EraseStatus == EFI_SUCCESS) && (IsZero1 == FALSE) && (IsZero2 ==
> TRUE) && ((IsZero3 == FALSE)))
>
>              AssertionType = EFI_TEST_ASSERTION_PASSED;
>
> @@ -492,26 +508,41 @@ BlockIo2:
>
>          // Read the data with 0, the first/last block should not be erased
>
>          ReadStatus = BlockIo2->ReadBlocksEx (BlockIo2, MediaId, Lba,
> &BlockIo2Token, BufferSize, (VOID*)Buffer2);
>
>          if (ReadStatus == EFI_SUCCESS) {
>
> -          for (Index1 = 0; Index1 < BlockSize; Index1++) {
>
> -            if (Buffer2[Index1] != 0) {
>
> +          for (Index1 = 0, EraseCounter = 0; Index1 < BlockSize; Index1++) {
>
> +            if (Buffer2[Index1] != 0x00 && Buffer2[Index1] != 0xFF) {
>
>                IsZero1 = FALSE;
>
>                break;
>
> +            } else if (Buffer2[Index1] == 0x00) {
>
> +              EraseCounter++;
>
>              }
>
>            }
>
> +          if (EraseCounter!=0 && EraseCounter!=BlockSize) {
>
> +            IsZero1 = FALSE;
>
> +          }
>
>
>
> -          for (Index1 = BlockSize; Index1 < BufferSize - BlockSize; Index1++) {
>
> -            if (Buffer2[Index1] != 0) {
>
> +          for (Index1 = BlockSize, EraseCounter = 0; Index1 < BufferSize -
> BlockSize; Index1++) {
>
> +            if (Buffer2[Index1] != 0x00 && Buffer2[Index1] != 0xFF) {
>
>                IsZero2 = FALSE;
>
>                break;
>
> +            } else if (Buffer2[Index1] == 0x00) {
>
> +              EraseCounter++;
>
>              }
>
>            }
>
> +          if (EraseCounter!=0 && EraseCounter!=(BufferSize - (BlockSize*2))) {
>
> +            IsZero2 = FALSE;
>
> +          }
>
>
>
> -          for (Index1 = BufferSize - BlockSize; Index1 < BufferSize; Index1++) {
>
> -            if (Buffer2[Index1] != 0) {
>
> +          for (Index1 = BufferSize - BlockSize, EraseCounter = 0; Index1 <
> BufferSize; Index1++) {
>
> +            if (Buffer2[Index1] != 0x00 && Buffer2[Index1] != 0xFF) {
>
>                IsZero3 = FALSE;
>
>                break;
>
> +            } else if (Buffer2[Index1] == 0x00) {
>
> +              EraseCounter++;
>
>              }
>
>            }
>
> +          if (EraseCounter!=0 && EraseCounter!=BlockSize) {
>
> +            IsZero3 = FALSE;
>
> +          }
>
>
>
>            if ((EraseStatus == EFI_SUCCESS) && (IsZero1 == FALSE) && (IsZero2 ==
> TRUE) && ((IsZero3 == FALSE)))
>
>              AssertionType = EFI_TEST_ASSERTION_PASSED;
>
> --
>
> 2.26.2.windows.1
>
>
>
>
>
> -=-=-=-=-=-=
> Groups.io Links: You receive all messages sent to this group.
> View/Reply Online (#66857): https://edk2.groups.io/g/devel/message/66857
> Mute This Topic: https://groups.io/mt/77977762/1945644
> Group Owner: devel+owner@edk2.groups.io
> Unsubscribe: https://edk2.groups.io/g/devel/unsub [samer.el-haj-
> mahmoud@arm.com]
> -=-=-=-=-=-=
>

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[-- Attachment #2: Type: text/html, Size: 18874 bytes --]

  reply	other threads:[~2020-11-17  5:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02  9:59 [PATCH 2/2] uefi-sct/SctPkg: Correct BBTestEraseBlocks behavior (EFI_BLOCK_IO_PROTOCOL) Chen, ArvinX
2020-11-11 20:56 ` [edk2-devel] " Samer El-Haj-Mahmoud
2020-11-17  5:51   ` Chen, ArvinX [this message]
2020-11-17 13:53     ` Samer El-Haj-Mahmoud
2020-11-24  5:47       ` 回覆: " Chen, ArvinX
2020-11-24  5:49         ` G Edhaya Chandran
2020-12-07  9:49   ` G Edhaya Chandran

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=DM5PR11MB17378A3545211C3C08578AE1FBE20@DM5PR11MB1737.namprd11.prod.outlook.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