From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"greg@kroah.com" <greg@kroah.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"David.Laight@ACULAB.COM" <David.Laight@ACULAB.COM>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: [RESEND PATCH v2] devres: Really align data field to unsigned long long
Date: Tue, 10 Jul 2018 06:42:55 +0000 [thread overview]
Message-ID: <f73763e1375693777cd6d95a2133a36618e9412d.camel@synopsys.com> (raw)
In-Reply-To: <e98bd4ab-ea20-0b42-bda9-eae8a6030c8f@synopsys.com>
Hi Vineet,
On Mon, 2018-07-09 at 11:27 -0700, Vineet Gupta wrote:
> On 07/09/2018 03:23 AM, Alexey Brodkin wrote:
> > Hi David,
> >
> > On Mon, 2018-07-09 at 10:18 +0000, David Laight wrote:
> > > From: Alexey Brodkin
> > > > Sent: 09 July 2018 11:00
> > >
> > > ...
> > > > That's a good idea indeed but it doesn't solve the problem with
> > > > struct devres_node. Consider the following snippet:
> > > > -------------------------------->8-------------------------------
> > > > struct mystruct {
> > > > atomic64_t myvar;
> > > > }
> > > >
> > > > struct mystruct *p;
> > > > p = devm_kzalloc(dev, sizeof(*p), GFP_KERNEL);
> > > > -------------------------------->8-------------------------------
> > > >
> > > > Here myvar address will match address of "data" member of struct devres_node.
> > > > So if "data" is has offset of 12 bytes from the beginning of a page then
> > > > myvar won't be 64-bit aligned regardless of myvar's attribute, right?
> > >
> > > ...
> > > > > > - unsigned long long data[]; /* guarantee ull alignment */
> > >
> > > Ahh, that line should be:
> > > u8 data[] __aligned(8); /* Guarantee 64bit alignment */
> >
> > And that pretty much what I suggested in my initial patch :)
> >
> > For the record x86 has exactly the same atomic64_t as you suggested,
> > see https://elixir.bootlin.com/linux/latest/source/arch/x86/include/asm/atomic64_32.h#L13:
> > ---------------------->8------------------
> > typedef struct {
> > u64 __aligned(8) counter;
> > } atomic64_t;
> > ---------------------->8------------------
>
> And so does the ARC version since when the atomic64_t support was added by commit
> ce6365270ecd
>
> Also, you should consider using the pre-canned type aligned_u64.
>
> typedef struct {
> aligned_u64 counter;
> ^^^^^^^^^^^
> } atomic64_t;
As Peter mentioned earlier atomic is signed, see:
http://lists.infradead.org/pipermail/linux-snps-arc/2018-July/004030.html
So looks like we need this fix for ARC instead:
--------------------------------->8----------------------------
diff --git a/arch/arc/include/asm/atomic.h b/arch/arc/include/asm/atomic.h
index 11859287c52a..ef94b7371de6 100644
--- a/arch/arc/include/asm/atomic.h
+++ b/arch/arc/include/asm/atomic.h
@@ -367,7 +367,7 @@ ATOMIC_OPS(xor, ^=, CTOP_INST_AXOR_DI_R2_R2_R3)
*/
typedef struct {
- aligned_u64 counter;
+ long long __aligned(8) counter;
} atomic64_t;
#define ATOMIC64_INIT(a) { (a) }
--------------------------------->8----------------------------
-Alexey
prev parent reply other threads:[~2018-07-10 6:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 4:44 Alexey Brodkin
2018-07-09 5:48 ` Greg KH
2018-07-09 6:46 ` Alexey Brodkin
2018-07-09 7:06 ` greg
2018-07-09 7:17 ` Alexey Brodkin
2018-07-09 7:33 ` greg
2018-07-09 7:07 ` Geert Uytterhoeven
2018-07-09 7:22 ` Alexey Brodkin
2018-07-09 7:52 ` Geert Uytterhoeven
2018-07-09 8:37 ` Alexey Brodkin
2018-07-09 9:03 ` Geert Uytterhoeven
2018-07-09 9:16 ` David Laight
2018-07-09 9:23 ` Geert Uytterhoeven
2018-07-09 9:54 ` David Laight
2018-07-09 9:59 ` Alexey Brodkin
2018-07-09 10:18 ` David Laight
2018-07-09 10:23 ` Alexey Brodkin
2018-07-09 18:27 ` Vineet Gupta
2018-07-10 6:42 ` Alexey Brodkin [this message]
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=f73763e1375693777cd6d95a2133a36618e9412d.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=David.Laight@ACULAB.COM \
--cc=Vineet.Gupta1@synopsys.com \
--cc=greg@kroah.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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®