From: Vineet.Gupta1@synopsys.com (Vineet Gupta)
To: linux-snps-arc@lists.infradead.org
Subject: [RESEND PATCH v2] devres: Really align data field to unsigned long long
Date: Mon, 9 Jul 2018 11:27:31 -0700 [thread overview]
Message-ID: <e98bd4ab-ea20-0b42-bda9-eae8a6030c8f@synopsys.com> (raw)
In-Reply-To: <82d2b36fa913bca6d56c7bf32a653324970817b8.camel@synopsys.com>
On 07/09/2018 03:23 AM, Alexey Brodkin wrote:
> Hi David,
>
> On Mon, 2018-07-09@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;
next prev parent reply other threads:[~2018-07-09 18:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 4:44 [RESEND PATCH v2] devres: Really align data field to unsigned long long 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 [this message]
2018-07-10 6:42 ` Alexey Brodkin
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=e98bd4ab-ea20-0b42-bda9-eae8a6030c8f@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=linux-snps-arc@lists.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