From: "Wasim Khan" <wasim.khan@nxp.com>
To: "michael.d.kinney@intel.com" <michael.d.kinney@intel.com>,
"liming.gao@intel.com" <liming.gao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: [edk2-discuss] Need memory barriers in IoLib for AARCH64
Date: Fri, 10 Jul 2020 12:49:33 +0000 [thread overview]
Message-ID: <VE1PR04MB6702D23929E36D9B99D8AC0590650@VE1PR04MB6702.eurprd04.prod.outlook.com> (raw)
Hello,
MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic.inf:
IoLib library uses IoLibArm.c for AARCH64/ARM architecture and IoLib.c for other architectures.
While IoLib.c already has memory barriers in MmioWrite functions, there barriers are missing in IoLibArm.c
Is there any reason for **not** adding these memory barriers in IoLibArm.c to guarantee that all MMIO operations
are serialized ?
I am facing some issues and I need to add memory barriers in IoLibArm.c for AARCH64 also .
Regards,
Wasim
next reply other threads:[~2020-07-10 12:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 12:49 Wasim Khan [this message]
2020-07-12 5:17 ` [edk2-discuss] Need memory barriers in IoLib for AARCH64 Wasim Khan
2020-07-12 16:54 ` [edk2-devel] " Andrew Fish
2020-07-13 15:31 ` Laszlo Ersek
2020-07-13 15:57 ` Andrew Fish
2020-07-17 6:43 ` Wasim Khan
2020-07-18 20:08 ` Andrew Fish
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=VE1PR04MB6702D23929E36D9B99D8AC0590650@VE1PR04MB6702.eurprd04.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