[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <a034a57e-d9f1-4c56-87f0-e9126246849d@app.fastmail.com>
Date: Sun, 09 Nov 2025 18:35:23 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "Xie Yuanbin" <qq570070308@...il.com>,
"Peter Zijlstra" <peterz@...radead.org>,
"David Hildenbrand" <david@...hat.com>,
"Thomas Gleixner" <tglx@...utronix.de>,
"Segher Boessenkool" <segher@...nel.crashing.org>, riel@...riel.com,
"Russell King" <linux@...linux.org.uk>,
"Mathieu Desnoyers" <mathieu.desnoyers@...icios.com>,
"Paul E. McKenney" <paulmck@...nel.org>, pjw@...nel.org,
"Palmer Dabbelt" <palmer@...belt.com>,
"Albert Ou" <aou@...s.berkeley.edu>, "Alexandre Ghiti" <alex@...ti.fr>,
"Heiko Carstens" <hca@...ux.ibm.com>, gor@...ux.ibm.com,
"Alexander Gordeev" <agordeev@...ux.ibm.com>,
"Christian Borntraeger" <borntraeger@...ux.ibm.com>,
"Sven Schnelle" <svens@...ux.ibm.com>,
"David S . Miller" <davem@...emloft.net>,
"Andreas Larsson" <andreas@...sler.com>,
"Andy Lutomirski" <luto@...nel.org>, "Ingo Molnar" <mingo@...hat.com>,
"Borislav Petkov" <bp@...en8.de>,
"Dave Hansen" <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>,
"Arnaldo Carvalho de Melo" <acme@...nel.org>,
"Namhyung Kim" <namhyung@...nel.org>,
"Mark Rutland" <mark.rutland@....com>,
"Alexander Shishkin" <alexander.shishkin@...ux.intel.com>,
"Jiri Olsa" <jolsa@...nel.org>, "Ian Rogers" <irogers@...gle.com>,
"Adrian Hunter" <adrian.hunter@...el.com>,
"James Clark" <james.clark@...aro.org>,
"Anna-Maria Gleixner" <anna-maria@...utronix.de>,
"Frederic Weisbecker" <frederic@...nel.org>,
"Juri Lelli" <juri.lelli@...hat.com>,
"Vincent Guittot" <vincent.guittot@...aro.org>,
"Dietmar Eggemann" <dietmar.eggemann@....com>,
"Steven Rostedt" <rostedt@...dmis.org>,
"Benjamin Segall" <bsegall@...gle.com>, "Mel Gorman" <mgorman@...e.de>,
"Valentin Schneider" <vschneid@...hat.com>,
"Nathan Chancellor" <nathan@...nel.org>,
"Nick Desaulniers" <nick.desaulniers+lkml@...il.com>,
"Bill Wendling" <morbo@...gle.com>,
"Justin Stitt" <justinstitt@...gle.com>,
"Thomas Huth" <thuth@...hat.com>,
"Christian Brauner" <brauner@...nel.org>,
"Jeff Layton" <jlayton@...nel.org>,
"Andrey Albershteyn" <aalbersh@...hat.com>,
"Andrew Morton" <akpm@...ux-foundation.org>, david@...nel.org,
"Lorenzo Stoakes" <lorenzo.stoakes@...cle.com>, max.kellermann@...os.com,
"Ryan Roberts" <ryan.roberts@....com>, nysal@...ux.ibm.com,
"Uladzislau Rezki (Sony)" <urezki@...il.com>
Cc: x86@...nel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
linux-s390@...r.kernel.org, sparclinux@...r.kernel.org,
linux-perf-users@...r.kernel.org, llvm@...ts.linux.dev,
"Will Deacon" <will@...nel.org>
Subject: Re: [PATCH v2 3/4] Provide the always inline version of some functions
On Sun, Nov 9, 2025, at 18:04, Xie Yuanbin wrote:
> On Sun, 9 Nov 2025 12:31:52 +0100, Peter Zijlstra wrote:
> Adding the always-inline version of these functions can provide better
> guidance for compiler optimization, but it does indeed lead to more
> complex code.
> The best solution may be to prompt the compiler to always inline at a
> specific calling point through some keyword.
> I noticed that there are also people discussing this issue on stackerflow
> , but it seems that the current compiler does not have such a feature.
> Link: https://stackoverflow.com/questions/14571593
You can mark the caller as __attribute__((flatten)) to force all
functions to be inlined into that one if possible. I don't know
if that would be helpful or desired here though.
Arnd
Powered by blists - more mailing lists