From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Finn Thain <fthain@linux-m68k.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Boqun Feng <boqun.feng@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org,
Linux-Arch <linux-arch@vger.kernel.org>,
linux-m68k@vger.kernel.org, Lance Yang <lance.yang@linux.dev>
Subject: Re: [RFC v2 2/3] atomic: Specify alignment for atomic_t and atomic64_t
Date: Wed, 1 Oct 2025 09:08:17 +0200 [thread overview]
Message-ID: <CAMuHMdVwYvJSoAWDTJJYOTt8mgtfa+sB_uevYR3NXFUK2fVS5A@mail.gmail.com> (raw)
In-Reply-To: <7c2c4da1-57f6-23b6-dbff-6288ef3f2a4f@linux-m68k.org>
Hi Finn,
On Wed, 1 Oct 2025 at 03:46, Finn Thain <fthain@linux-m68k.org> wrote:
> On Tue, 30 Sep 2025, Geert Uytterhoeven wrote:
> > > To silence the misalignment WARN from CONFIG_DEBUG_ATOMIC, for 64-bit
> > > atomic operations, for my small m68k .config, it was also necesary to
> > > increase ARCH_SLAB_MINALIGN to 8. However, I'm not advocating a
> >
> > Probably ARCH_SLAB_MINALIGN should be 4 on m68k. Somehow I thought that
> > was already the case, but it is __alignof__(unsigned long long) = 2.
>
> I agree -- setting ARCH_SLAB_MINALIGN to 4 would be better style, and may
> avoid surprises in future. Right now that won't have any effect because
> that value gets increased to sizeof(void *) by calculate_alignment() and
Ah, so there it happens...
> gets increased to ARCH_KMALLOC_MINALIGN or ARCH_DMA_MINALIGN by
> __kmalloc_minalign().
Thanks for checking!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2025-10-01 7:08 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-14 0:45 [RFC v2 0/3] Align atomic storage Finn Thain
2025-09-14 0:45 ` [RFC v2 2/3] atomic: Specify alignment for atomic_t and atomic64_t Finn Thain
2025-09-15 7:13 ` Geert Uytterhoeven
2025-09-15 7:35 ` Arnd Bergmann
2025-09-15 8:06 ` Peter Zijlstra
2025-09-15 9:26 ` Finn Thain
2025-09-15 9:29 ` Arnd Bergmann
2025-09-22 7:06 ` Geert Uytterhoeven
2025-09-22 8:16 ` Finn Thain
2025-09-22 9:29 ` Geert Uytterhoeven
2025-09-22 15:21 ` Arnd Bergmann
2025-09-23 6:28 ` Finn Thain
2025-09-23 6:41 ` Arnd Bergmann
2025-09-23 8:05 ` Finn Thain
2025-09-23 19:11 ` Arnd Bergmann
2025-09-30 2:18 ` Finn Thain
2025-09-30 6:35 ` Arnd Bergmann
2025-10-01 1:03 ` Finn Thain
2025-10-01 6:44 ` Arnd Bergmann
2025-10-06 9:25 ` Finn Thain
2025-10-06 9:25 ` Finn Thain
2025-10-06 10:07 ` Arnd Bergmann
2025-10-06 10:22 ` Peter Zijlstra
2025-10-06 11:09 ` Arnd Bergmann
2025-10-06 9:37 ` Peter Zijlstra
2025-09-30 7:41 ` Geert Uytterhoeven
2025-10-01 1:46 ` Finn Thain
2025-10-01 7:08 ` Geert Uytterhoeven [this message]
2025-09-14 0:45 ` [RFC v2 1/3] documentation: Discourage alignment assumptions Finn Thain
2025-09-14 0:45 ` [RFC v2 3/3] atomic: Add alignment check to instrumented atomic operations Finn Thain
2025-09-15 8:00 ` Peter Zijlstra
2025-09-15 9:38 ` Finn Thain
2025-09-15 10:06 ` Peter Zijlstra
2025-09-15 10:37 ` Finn Thain
2025-09-15 11:20 ` Arnd Bergmann
2025-09-16 0:16 ` Finn Thain
2025-09-16 10:10 ` Geert Uytterhoeven
2025-09-17 1:23 ` Finn Thain
2025-09-16 12:37 ` Arnd Bergmann
2025-09-16 21:38 ` Brad Boyer
2025-09-17 16:54 ` Andreas Schwab
2025-09-17 2:14 ` Finn Thain
2025-09-22 15:49 ` Arnd Bergmann
2025-09-23 6:39 ` Finn Thain
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=CAMuHMdVwYvJSoAWDTJJYOTt8mgtfa+sB_uevYR3NXFUK2fVS5A@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=fthain@linux-m68k.org \
--cc=lance.yang@linux.dev \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peterz@infradead.org \
--cc=will@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).