From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
Waiman Long <longman@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Petr Mladek <pmladek@suse.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, arcml <linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH 0/2] locking/qspinlock: Break qspinlock_types.h header loop
Date: Thu, 6 Aug 2020 03:37:31 +0000 [thread overview]
Message-ID: <04d25afe-d258-86ba-b2d1-cee8b60ee227@synopsys.com> (raw)
In-Reply-To: <20200730075040.GA21623@gondor.apana.org.au>
On 7/30/20 12:50 AM, Herbert Xu wrote:
> On Thu, Jul 30, 2020 at 10:47:16AM +0300, Andy Shevchenko wrote:
>> We may ask Synopsys folks to look at this as well.
>> Vineet, any ideas if we may unify ATOMIC64_INIT() across the architectures?
> I don't think there is any technical difficulty. The custom
> atomic64_t simply adds an alignment requirement so the initialisor
> remains the same.
Exactly so.
FWIW the alignment requirement is because ARC ABI allows 64-bit data to be 32-bit
aligned provided hardware deals fine with 4 byte aligned for the non-atomic
double-load/store LDD/STD instructions. The 64-bit alignement however is required
for atomic double load/store LLOCKD/SCONDD instructions hence the definition of
ARC atomic64_t
-Vineet
next prev parent reply other threads:[~2020-08-06 3:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 11:03 linux-next: build failure after merge of the printk tree Stephen Rothwell
2020-07-29 11:47 ` Herbert Xu
2020-07-29 12:28 ` [PATCH 0/2] locking/qspinlock: Break qspinlock_types.h header loop Herbert Xu
2020-07-29 12:31 ` [PATCH 1/2] locking/atomic: Move ATOMIC_INIT into linux/types.h Herbert Xu
2020-07-29 12:33 ` [PATCH 2/2] locking/qspinlock: Do not include atomic.h from qspinlock_types.h Herbert Xu
2020-07-29 12:47 ` [PATCH 0/2] locking/qspinlock: Break qspinlock_types.h header loop peterz
2020-07-29 12:51 ` Herbert Xu
2020-07-29 13:00 ` peterz
2020-07-29 13:28 ` Sergey Senozhatsky
2020-07-29 14:28 ` peterz
2020-07-29 16:41 ` Sergey Senozhatsky
2020-07-29 13:35 ` Waiman Long
2020-07-29 15:04 ` Andy Shevchenko
2020-07-30 0:59 ` Herbert Xu
2020-07-30 7:47 ` Andy Shevchenko
2020-07-30 7:50 ` Herbert Xu
2020-07-30 7:55 ` Andy Shevchenko
2020-08-06 3:37 ` Vineet Gupta [this message]
2020-07-29 17:50 ` Sergey Senozhatsky
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=04d25afe-d258-86ba-b2d1-cee8b60ee227@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=andy.shevchenko@gmail.com \
--cc=bp@alien8.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).