public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Li, Yong" <yong.li@intel.com>
To: <devel@edk2.groups.io>, <sunilvl@ventanamicro.com>,
	<michael.d.kinney@intel.com>, <gaoliming@byosoft.com.cn>
Cc: Andrei Warkentin <andrei.warkentin@intel.com>,
	Evan Chai <evan.chai@intel.com>,
	Tuan Phan <tphan@ventanamicro.com>
Subject: Re: [edk2-devel] [PATCH v2 1/1] MdePkg/BaseLib: Add SpeculationBarrier implementation for RiscV64
Date: Mon, 5 Jun 2023 15:44:54 +0800	[thread overview]
Message-ID: <f48f9819-ff0c-e580-026c-4361d4c9fd05@intel.com> (raw)
In-Reply-To: <efce7c47-a3c1-ebef-0b2c-dca311c64ed4@intel.com>

Hi  Michael,

I updated the commit messages and the EDK II CI passes, 
The PR link is as below.
https://github.com/tianocore/edk2/pull/4480

Please help merge, thanks for the helping


On 2023/6/3 14:13, Li, Yong wrote:
> Hi Michael
> 
> This is the change to MdePkg/Library/BaseLib/RiscV64. 
> Since it is for RiscV specific, I somehow got the review from Sunil.
> Not sure need additional reviewer and or anything else from my side ?
> It is my first patch to edk2, please help proceed and look for the feedback. Thanks 
> 
> 
> On 2023/6/3 1:09, Sunil V L wrote:
>> On Thu, Jun 01, 2023 at 06:56:05PM +0800, Yong Li wrote:
>>> Implement the SpeculationBarrier with implementations consisting of
>>> fence instruction which provides finer-grain memory orderings.
>>> Perform Data Barrier in RiscV: fence rw,rw
>>> Perform Instruction Barrier in RiscV: fence.i; fence r,r
>>> More detail is in Appendix A: RVWMO Explanatory Material in
>>> https://github.com/riscv/riscv-isa-manual
>>>
>>> This API is first introduced in the below commits for IA32 and x64
>>> https://github.com/tianocore/edk2/commit/d9f1cac51bd354507e880e614d11a1dc160d38a3
>>> https://github.com/tianocore/edk2/commit/e83d841fdc2878959185c4c6cc38a7a1e88377a4
>>> and below the commit for ARM and AArch64 implementation
>>> https://github.com/tianocore/edk2/commit/c0959b4426b2da45cdb8146a5116bb4fd9b86534
>>>
>>> This commit is to add the RiscV64 implementation which will be used by
>>> variable service under Variable/RuntimeDxe
>>>
>>> Cc: Andrei Warkentin <andrei.warkentin@intel.com>
>>> Cc: Evan Chai <evan.chai@intel.com>
>>> Cc: Sunil V L <sunilvl@ventanamicro.com>
>>> Cc: Tuan Phan <tphan@ventanamicro.com>
>>> Signed-off-by: Yong Li <yong.li@intel.com>
>>> ---
>>
>> Reviewed-by: Sunil V L <sunilvl@ventanamicro.com>
>>
>> Thanks,
>> Sunil
>>
>>
>> 
>>
>>

  reply	other threads:[~2023-06-05  7:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1685616822.git.yong.li@intel.com>
2023-06-01 10:56 ` [PATCH v2 1/1] MdePkg/BaseLib: Add SpeculationBarrier implementation for RiscV64 Li, Yong
2023-06-02 17:09   ` Sunil V L
2023-06-03  6:13     ` [edk2-devel] " Li, Yong
2023-06-05  7:44       ` Li, Yong [this message]
2023-06-06 21:06         ` Michael D Kinney

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=f48f9819-ff0c-e580-026c-4361d4c9fd05@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