public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Eric Dong <eric.dong@intel.com>
Cc: edk2-devel@lists.01.org
Subject: Re: [Patch v3 0/3] Optimize load uCode performance
Date: Tue, 17 Jul 2018 18:38:08 +0200	[thread overview]
Message-ID: <4878637c-df4f-f099-32e8-370208c01a71@redhat.com> (raw)
In-Reply-To: <20180716030851.13752-1-eric.dong@intel.com>

Hi Eric,

On 07/16/18 05:08, Eric Dong wrote:
> Use below three rules to optimize load uCode performance:
> 1. Let BSP relocate uCode from flash to memory for better performance.
> 2. BSP caches the CPU ID and address of uCode so AP doesn’t need to look 
>    for the uCode again if the CPU ID is same as BSP’s.
> 3. Only apply uCode in one thread of a core when hyper threading is enabled.
> 
> v2 changes:
>   Fix potential issue if allocate memory failed.
> 
> V3 Changes:
>   Remove the ASSERT code which is not correct.

Based on the above, my understanding is that you didn't modify patches
#2 and #3, from v2 to v3. Is that correct?

If it's correct, then you should have picked up my Acked-by tags from
the v2 review, for the v3 posting:

http://mid.mail-archive.com/dcf4df85-1d35-65e9-2c9b-d5d47a0988aa@redhat.com

http://mid.mail-archive.com/dbc8439f-448e-306c-cdbd-1b2edc1f4aef@redhat.com

If you don't pick up my previous review tags for un-modified patches in
new postings of the patch series, then I have to re-review those patches
every single time. I described this workflow element here:

https://github.com/tianocore/tianocore.github.io/wiki/Laszlo's-unkempt-git-guide-for-edk2-contributors-and-maintainers#contrib-26

----------
    26. § More frequently though, you will get requests for changes for
        *some* of your patches, while *others* of your patches will be
        fine, and garner Reviewed-by, Acked-by, and Tested-by tags. What
        you need to do in this case is:

        * create the next version of your local branch
        * pick up the tags that you got on the list
        * implement the requested changes
        * mark the v2 changes on each patch outside of the commit
          message
        * push the next version to your personal repo again
        * post the next version to the list

        In the following steps, we'll go through each of these in more
        detail.
----------

Thanks
Laszlo

> Test:
> Use an sample platform which has 1 socket, 4 core, 8 threads, the 
> CpuMpPei driver cost time reduce from 108.4ms to 27.2ms
> 
> 
> Eric Dong (3):
>   UefiCpuPkg/MpInitLib: Use BSP uCode for APs if possible.
>   UefiCpuPkg/MpInitLib: Load uCode once for each core.
>   UefiCpuPkg/MpInitLib: Relocate uCode to memory to save time.
> 
>  UefiCpuPkg/Library/MpInitLib/Microcode.c | 43 +++++++++++++++++++++++++++++---
>  UefiCpuPkg/Library/MpInitLib/MpLib.c     | 38 +++++++++++++++++++++++++---
>  UefiCpuPkg/Library/MpInitLib/MpLib.h     | 11 ++++++--
>  3 files changed, 84 insertions(+), 8 deletions(-)
> 
> 
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
> 



  parent reply	other threads:[~2018-07-17 16:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16  3:08 [Patch v3 0/3] Optimize load uCode performance Eric Dong
2018-07-16  3:08 ` [Patch v3 1/3] UefiCpuPkg/MpInitLib: Relocate uCode to memory to save time Eric Dong
2018-07-17 10:02   ` Ni, Ruiyu
2018-07-16  3:08 ` [Patch v3 2/3] UefiCpuPkg/MpInitLib: Use BSP uCode for APs if possible Eric Dong
2018-07-17 10:00   ` Ni, Ruiyu
2018-07-16  3:08 ` [Patch v3 3/3] UefiCpuPkg/MpInitLib: Load uCode once for each core Eric Dong
2018-07-17 10:02   ` Ni, Ruiyu
2018-07-17 14:07     ` Laszlo Ersek
2018-07-18  0:11       ` Dong, Eric
2018-07-19  4:42         ` Ni, Ruiyu
2018-07-17 16:38 ` Laszlo Ersek [this message]
2018-07-17 19:08   ` [Patch v3 0/3] Optimize load uCode performance Laszlo Ersek
2018-07-18  0:18   ` Dong, Eric
  -- strict thread matches above, loose matches on Subject: below --
2018-07-13  0:47 Eric Dong

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=4878637c-df4f-f099-32e8-370208c01a71@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