From: Thomas Monjalon <thomas@monjalon.net>
To: Phil Yang <Phil.Yang@arm.com>,
Diogo Behrens <diogo.behrens@huawei.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: dev@dpdk.org, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH] librte_eal: fix mcslock hang on weak memory
Date: Tue, 06 Oct 2020 23:49:45 +0200 [thread overview]
Message-ID: <1947647.zX4bR4m4Ni@thomas> (raw)
In-Reply-To: <DBAPR08MB58148C46395B8592D9AC2B8F98510@DBAPR08MB5814.eurprd08.prod.outlook.com>
31/08/2020 20:45, Honnappa Nagarahalli:
>
> Hi Diogo,
>
> Thanks for your explanation.
>
> As documented in https://developer.arm.com/documentation/ddi0487/fc B2.9.5 Load-Exclusive and Store-Exclusive instruction usage restrictions:
> " Between the Load-Exclusive and the Store-Exclusive, there are no explicit memory accesses, preloads,
> direct or indirect System register writes, address translation instructions, cache or TLB maintenance
> instructions, exception generating instructions, exception returns, or indirect branches."
> [Honnappa] This is a requirement on the software, not on the micro-architecture.
> We are having few discussions internally, will get back soon.
>
> So it is not allowed to insert (1) & (4) between (2, 3). The cmpxchg operation is atomic.
Please what is the conclusion?
next prev parent reply other threads:[~2020-10-06 21:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 9:20 [dpdk-dev] [PATCH] librte_eal: fix mcslock hang on weak memory Diogo Behrens
2020-08-26 10:17 ` Phil Yang
2020-08-27 8:56 ` Diogo Behrens
2020-08-28 9:19 ` Phil Yang
2020-08-31 18:45 ` Honnappa Nagarahalli
2020-10-06 21:49 ` Thomas Monjalon [this message]
2020-10-07 9:55 ` Diogo Behrens
2020-10-20 11:56 ` Thomas Monjalon
2020-10-20 21:49 ` Honnappa Nagarahalli
2020-11-22 18:07 ` Thomas Monjalon
2020-11-23 15:06 ` Honnappa Nagarahalli
2020-11-23 15:44 ` Stephen Hemminger
2020-11-23 18:16 ` Honnappa Nagarahalli
2020-11-23 18:29 ` Honnappa Nagarahalli
2020-11-23 19:36 ` Stephen Hemminger
2020-11-25 4:50 ` Honnappa Nagarahalli
2020-11-25 8:41 ` Diogo Behrens
2020-11-25 14:16 ` Thomas Monjalon
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-all 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=1947647.zX4bR4m4Ni@thomas \
--to=thomas@monjalon.net \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Phil.Yang@arm.com \
--cc=dev@dpdk.org \
--cc=diogo.behrens@huawei.com \
--cc=nd@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.