From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Will Deacon <Will.Deacon@arm.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
arcml <linux-snps-arc@lists.infradead.org>,
lkml <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: single copy atomicity for double load/stores on 32-bit systems
Date: Mon, 3 Jun 2019 11:43:20 -0700 [thread overview]
Message-ID: <77b30ed2-3211-222b-1342-051a6cde4f77@synopsys.com> (raw)
In-Reply-To: <20190531082112.GH2623@hirez.programming.kicks-ass.net>
On 5/31/19 1:21 AM, Peter Zijlstra wrote:
> And I'll stand by my earlier conviction that any architecture that has a
> native u64 (be it a 64bit arch or a 32bit with double-width
> instructions) but has an ABI that allows u32 alignment on them is daft.
Why ? For 64-bit data on 32-bit systems, hardware doesn't claim to provide any
single-copy atomicity for such data and software doesn't expect either.
next prev parent reply other threads:[~2019-06-03 18:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 18:22 Vineet Gupta
2019-05-30 18:53 ` Paul E. McKenney
2019-05-30 19:16 ` Vineet Gupta
2019-05-31 8:23 ` Peter Zijlstra
2019-05-31 8:25 ` Peter Zijlstra
2019-05-31 8:21 ` Peter Zijlstra
2019-06-03 18:08 ` Vineet Gupta
2019-06-03 20:13 ` Paul E. McKenney
2019-06-03 21:59 ` Vineet Gupta
2019-06-04 7:41 ` Geert Uytterhoeven
2019-06-06 9:43 ` Paul E. McKenney
2019-06-06 9:53 ` Geert Uytterhoeven
2019-06-06 16:34 ` David Laight
2019-06-06 21:17 ` Paul E. McKenney
2019-06-03 18:43 ` Vineet Gupta [this message]
2019-07-01 20:05 ` Vineet Gupta
2019-07-02 10:46 ` Will Deacon
2019-05-31 9:41 ` David Laight
2019-05-31 11:44 ` Paul E. McKenney
2019-06-03 18:44 ` Vineet Gupta
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=77b30ed2-3211-222b-1342-051a6cde4f77@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Will.Deacon@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
/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
all inboxes | Powered by JetHome®