public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, gao.cheng@intel.com
Cc: Liming Gao <gaoliming@byosoft.com.cn>, Ray Ni <ray.ni@intel.com>,
	Jiewen Yao <jiewen.yao@intel.com>
Subject: Re: [edk2-devel] [PATCH] MdeModulePkg/Variable: Merge variable header + data update into one step
Date: Tue, 14 Nov 2023 17:02:35 +0100	[thread overview]
Message-ID: <3008173d-d688-1555-56da-6b86485b1786@redhat.com> (raw)
In-Reply-To: <475e7d21da7f9a54d4841d1efe78c1e587c6b931.1699949356.git.gao.cheng@intel.com>

+Jiewen (I seem to remember Jiewen co-authored a whitepaper on edk2
variables; I could be wrong)

one more comment below:

On 11/14/23 09:23, Gao wrote:
> REF:https://bugzilla.tianocore.org/show_bug.cgi?id=4597
> 
> When creating a new variable, skip marking VAR_HEADER_VALID_ONLY so that
> variable header + data update can be merged into one flash write. This
> will greatly reduce the time taken for updating a variable and thus
> increase performance. Removing VAR_HEADER_VALID_ONLY marking doesn't
> have any function impact since it's not used by current code to detect
> variable header + data corruption.

That would have been my question; thanks for spelling it out in advance
(in the commit message).

I wouldn't like to start reviewing this right now, but if you don't get
a review in a week or so, feel free to ping me; I'll try to dig into it.

Laszlo

> 
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
> Cc: Ray Ni <ray.ni@intel.com>
> Signed-off-by: Gao Cheng <gao.cheng@intel.com>
> ---
>  .../Universal/Variable/RuntimeDxe/Variable.c  | 45 ++-----------------
>  1 file changed, 4 insertions(+), 41 deletions(-)
> 
> diff --git a/MdeModulePkg/Universal/Variable/RuntimeDxe/Variable.c b/MdeModulePkg/Universal/Variable/RuntimeDxe/Variable.c
> index 7a1331255b..3c360481f4 100644
> --- a/MdeModulePkg/Universal/Variable/RuntimeDxe/Variable.c
> +++ b/MdeModulePkg/Universal/Variable/RuntimeDxe/Variable.c
> @@ -2168,11 +2168,9 @@ UpdateVariable (
>  
>      if (!mVariableModuleGlobal->VariableGlobal.EmuNvMode) {
>        //
> -      // Four steps
> -      // 1. Write variable header
> -      // 2. Set variable state to header valid
> -      // 3. Write variable data
> -      // 4. Set variable state to valid
> +      // Two steps
> +      // 1. Write variable header and data
> +      // 2. Set variable state to valid
>        //
>        //
>        // Step 1:
> @@ -2183,7 +2181,7 @@ UpdateVariable (
>                   TRUE,
>                   Fvb,
>                   mVariableModuleGlobal->NonVolatileLastVariableOffset,
> -                 (UINT32)GetVariableHeaderSize (AuthFormat),
> +                 (UINT32)VarSize,
>                   (UINT8 *)NextVariable
>                   );
>  
> @@ -2194,41 +2192,6 @@ UpdateVariable (
>        //
>        // Step 2:
>        //
> -      NextVariable->State = VAR_HEADER_VALID_ONLY;
> -      Status              = UpdateVariableStore (
> -                              &mVariableModuleGlobal->VariableGlobal,
> -                              FALSE,
> -                              TRUE,
> -                              Fvb,
> -                              mVariableModuleGlobal->NonVolatileLastVariableOffset + OFFSET_OF (VARIABLE_HEADER, State),
> -                              sizeof (UINT8),
> -                              &NextVariable->State
> -                              );
> -
> -      if (EFI_ERROR (Status)) {
> -        goto Done;
> -      }
> -
> -      //
> -      // Step 3:
> -      //
> -      Status = UpdateVariableStore (
> -                 &mVariableModuleGlobal->VariableGlobal,
> -                 FALSE,
> -                 TRUE,
> -                 Fvb,
> -                 mVariableModuleGlobal->NonVolatileLastVariableOffset + GetVariableHeaderSize (AuthFormat),
> -                 (UINT32)(VarSize - GetVariableHeaderSize (AuthFormat)),
> -                 (UINT8 *)NextVariable + GetVariableHeaderSize (AuthFormat)
> -                 );
> -
> -      if (EFI_ERROR (Status)) {
> -        goto Done;
> -      }
> -
> -      //
> -      // Step 4:
> -      //
>        NextVariable->State = VAR_ADDED;
>        Status              = UpdateVariableStore (
>                                &mVariableModuleGlobal->VariableGlobal,



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#111204): https://edk2.groups.io/g/devel/message/111204
Mute This Topic: https://groups.io/mt/102579876/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2023-11-14 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14  8:23 [edk2-devel] [PATCH] MdeModulePkg/Variable: Merge variable header + data update into one step Gao
2023-11-14 16:02 ` Laszlo Ersek [this message]
2023-11-17  0:43 ` 回复: " gaoliming via groups.io

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=3008173d-d688-1555-56da-6b86485b1786@redhat.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