All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@amd.com>
To: Alejandro Vallejo <alejandro.garciavallejo@amd.com>
Cc: xen-devel@lists.xenproject.org,
	Stefano Stabellini <sstabellini@kernel.org>,
	Julien Grall <julien@xen.org>,
	Bertrand Marquis <bertrand.marquis@arm.com>,
	Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
	Michal Orzel <michal.orzel@amd.com>
Subject: Re: [PATCH] arm/nospec: Make nospec helpers always_inline
Date: Tue, 6 Oct 2026 15:50:13 +0200	[thread overview]
Message-ID: <asT8lQktOeLhcva3@Mac.lan> (raw)
In-Reply-To: <20261006103142.139422-1-alejandro.garciavallejo@amd.com>

On Tue, Oct 06, 2026 at 12:31:40PM +0200, Alejandro Vallejo wrote:
> While today they don't implement fencing in a way that would block
> speculation, once/if they do they'll absolutely need to be inlined, even
> if -fno-inline or -fno-early-inlining are passed.

FWIW, it's my understanding that -fno-early-inlining is not really
relevant here; it disables the early inlining pass, but the late(r)
one(s) is/are still present, so inlining will happen, just later in
the compilation process.  -fno-inline is indeed relevant here.

Thanks, Roger.


      parent reply	other threads:[~2026-10-06 13:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06 10:31 [PATCH] arm/nospec: Make nospec helpers always_inline Alejandro Vallejo
2026-10-06 10:45 ` Orzel, Michal
2026-10-06 10:51   ` Andrew Cooper
2026-10-06 12:21     ` Alejandro Vallejo
2026-10-06 12:29   ` Alejandro Vallejo
2026-10-07 12:00     ` Orzel, Michal
2026-10-07 12:40       ` Alejandro Vallejo
2026-10-06 13:50 ` Roger Pau Monné [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=asT8lQktOeLhcva3@Mac.lan \
    --to=roger.pau@amd.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=alejandro.garciavallejo@amd.com \
    --cc=bertrand.marquis@arm.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.