From: Ingo Molnar <mingo@kernel.org>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: Brian Gerst <brgerst@gmail.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
"H . Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>, Ard Biesheuvel <ardb@kernel.org>,
Linus Torvalds <torvalds@linuxfoundation.org>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v3 00/11] Add a percpu subsection for cache hot data
Date: Tue, 4 Mar 2025 10:55:45 +0100 [thread overview]
Message-ID: <Z8bOIXeWYycUEmp4@gmail.com> (raw)
In-Reply-To: <CAFULd4YFm-2Sc6NOzyWt4-TPDkwY-=5h-Gb99M+tFf-Mczk0Ng@mail.gmail.com>
* Uros Bizjak <ubizjak@gmail.com> wrote:
> On Tue, Mar 4, 2025 at 10:48 AM Ingo Molnar <mingo@kernel.org> wrote:
> >
> >
> > * Brian Gerst <brgerst@gmail.com> wrote:
> >
> > > On Tue, Mar 4, 2025 at 3:47 AM Ingo Molnar <mingo@kernel.org> wrote:
> > > >
> > > >
> > > > * Brian Gerst <brgerst@gmail.com> wrote:
> > > >
> > > > > >
> > > > > > - PERCPU_SECTION(INTERNODE_CACHE_BYTES)
> > > > > > + PERCPU_SECTION(L1_CACHE_BYTES)
> > > > > > ASSERT(__per_cpu_hot_end - __per_cpu_hot_start <= 64, "percpu cache hot section too large")
> > > > > >
> > > > > > RUNTIME_CONST_VARIABLES
> > > > > >
> > > > >
> > > > > That is probably the right call. The initial percpu section is just
> > > > > used by the boot cpu early and as a template for the dynamically
> > > > > allocated percpu memory, which should account for the proper
> > > > > alignment for NUMA.
> > > >
> > > > Okay.
> > > >
> > > > Randconfig testing found another corner case with the attached config:
> > > >
> > > > KSYMS .tmp_vmlinux0.kallsyms.S
> > > > AS .tmp_vmlinux0.kallsyms.o
> > > > LD .tmp_vmlinux1
> > > > ld: percpu cache hot section too large
> > > > make[2]: *** [scripts/Makefile.vmlinux:77: vmlinux] Error 1
> > > >
> > > > (I haven't figured out the root cause yet.)
> > >
> > > CONFIG_MPENTIUM4 sets X86_L1_CACHE_SHIFT to 7 (128 bytes).
> >
> > Hm, to resolve this I'd go for the easy out of explicitly using '64' as
> > the size limit - like we did it in the C space.
>
> Why not simply:
>
> ASSERT(__per_cpu_hot_end - __per_cpu_hot_start <= L1_CACHE_BYTES, "...")
>
> ?
I don't think it's a great idea to randomly allow a larger section
depending on the .config ... The *actual* intended limit is 64, not 128
and not 4096, so I'd suggest we write it out as before.
Thanks,
Ingo
next prev parent reply other threads:[~2025-03-04 9:55 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 16:52 [PATCH v3 00/11] Add a percpu subsection for cache hot data Brian Gerst
2025-03-03 16:52 ` [PATCH v3 01/11] percpu: Introduce percpu hot section Brian Gerst
2025-03-04 8:27 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-04 10:36 ` tip-bot2 for Brian Gerst
2025-03-04 19:34 ` tip-bot2 for Brian Gerst
2025-03-04 19:43 ` tip-bot2 for Brian Gerst
2025-03-03 16:52 ` [PATCH v3 02/11] x86/percpu: Move pcpu_hot to " Brian Gerst
2025-03-04 8:27 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-04 10:36 ` tip-bot2 for Brian Gerst
2025-03-04 19:34 ` tip-bot2 for Brian Gerst
2025-03-04 19:43 ` tip-bot2 for Brian Gerst
2025-03-03 16:52 ` [PATCH v3 03/11] x86/preempt: Move preempt count " Brian Gerst
2025-03-04 8:27 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-04 10:36 ` tip-bot2 for Brian Gerst
2025-03-04 19:34 ` tip-bot2 for Brian Gerst
2025-03-04 19:43 ` tip-bot2 for Brian Gerst
2025-03-03 16:52 ` [PATCH v3 04/11] x86/smp: Move cpu number " Brian Gerst
2025-03-04 8:27 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-04 10:36 ` tip-bot2 for Brian Gerst
2025-03-04 19:34 ` tip-bot2 for Brian Gerst
2025-03-04 19:43 ` tip-bot2 for Brian Gerst
2025-03-03 16:52 ` [PATCH v3 05/11] x86/retbleed: Move call depth " Brian Gerst
2025-03-04 8:27 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-04 10:36 ` tip-bot2 for Brian Gerst
2025-03-04 19:34 ` tip-bot2 for Brian Gerst
2025-03-04 19:43 ` tip-bot2 for Brian Gerst
2025-03-03 16:52 ` [PATCH v3 06/11] x86/softirq: Move softirq_pending " Brian Gerst
2025-03-04 8:27 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-04 10:36 ` tip-bot2 for Brian Gerst
2025-03-04 19:34 ` tip-bot2 for Brian Gerst
2025-03-04 19:43 ` tip-bot2 for Brian Gerst
2025-03-03 16:52 ` [PATCH v3 07/11] x86/irq: Move irq stacks " Brian Gerst
2025-03-04 8:27 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-04 10:36 ` tip-bot2 for Brian Gerst
2025-03-04 19:34 ` tip-bot2 for Brian Gerst
2025-03-04 19:43 ` tip-bot2 for Brian Gerst
2025-03-03 16:52 ` [PATCH v3 08/11] x86/percpu: Move top_of_stack " Brian Gerst
2025-03-04 8:27 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-04 10:36 ` tip-bot2 for Brian Gerst
2025-03-04 19:33 ` tip-bot2 for Brian Gerst
2025-03-04 19:43 ` tip-bot2 for Brian Gerst
2025-03-03 16:52 ` [PATCH v3 09/11] x86/percpu: Move current_task " Brian Gerst
2025-03-04 8:27 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-04 10:36 ` tip-bot2 for Brian Gerst
2025-03-04 19:33 ` tip-bot2 for Brian Gerst
2025-03-04 19:43 ` tip-bot2 for Brian Gerst
2025-03-03 16:52 ` [PATCH v3 10/11] x86/stackprotector: Move __stack_chk_guard " Brian Gerst
2025-03-04 8:27 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-04 10:36 ` tip-bot2 for Brian Gerst
2025-03-04 19:33 ` tip-bot2 for Brian Gerst
2025-03-04 19:43 ` tip-bot2 for Brian Gerst
2025-03-03 16:52 ` [PATCH v3 11/11] x86/smp: Move this_cpu_off " Brian Gerst
2025-03-04 8:27 ` [tip: x86/core] " tip-bot2 for Brian Gerst
2025-03-04 10:36 ` tip-bot2 for Brian Gerst
2025-03-04 19:33 ` tip-bot2 for Brian Gerst
2025-03-04 19:43 ` tip-bot2 for Brian Gerst
2025-03-03 19:53 ` [PATCH v3 00/11] Add a percpu subsection for cache hot data Uros Bizjak
2025-03-03 20:38 ` Ingo Molnar
2025-03-03 20:55 ` Brian Gerst
2025-03-04 8:47 ` Ingo Molnar
2025-03-04 9:26 ` Brian Gerst
2025-03-04 9:47 ` Ingo Molnar
2025-03-04 9:52 ` Uros Bizjak
2025-03-04 9:55 ` Ingo Molnar [this message]
2025-03-04 15:00 ` Brian Gerst
2025-03-04 16:01 ` Uros Bizjak
2025-03-04 16:42 ` Brian Gerst
2025-03-04 16:48 ` Uros Bizjak
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=Z8bOIXeWYycUEmp4@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linuxfoundation.org \
--cc=ubizjak@gmail.com \
--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