All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Vallejo" <alejandro.garciavallejo@amd.com>
To: "Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Orzel, Michal" <michal.orzel@amd.com>,
	<xen-devel@lists.xenproject.org>
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
	"Julien Grall" <julien@xen.org>,
	"Bertrand Marquis" <bertrand.marquis@arm.com>,
	"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>
Subject: Re: [PATCH] arm/nospec: Make nospec helpers always_inline
Date: Tue, 06 Oct 2026 14:21:28 +0200	[thread overview]
Message-ID: <DLXR22SBHLW3.2SACLO55074LM@amd.com> (raw)
In-Reply-To: <d66c1a89-b448-45d1-b17f-ef63a34acc8b@citrix.com>

On Tue Oct 6, 2026 at 12:51 PM CEST, Andrew Cooper wrote:
> On 06/10/2026 11:45 am, Orzel, Michal wrote:
> >
> > On 06-Oct-26 12:31, 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.
> >>
> >> Signed-off-by: Alejandro Vallejo <alejandro.garciavallejo@amd.com>
> > Reviewed-by: Michal Orzel <michal.orzel@amd.com>
> >
> > but this should be done for Arm, RISCV and PPC at once in which case you can
> > keep my tag for v2 # for Arm.
>
> I previously had a patch series which made this all common, for these
> kinds of reasons.
>
> I think I'd prefer to kick that over the line, than to keep on taking
> micro-bugfixes like this.

for reference:
    https://lore.kernel.org/all/20240304161041.3465897-1-andrew.cooper3@citrix.com/

I wouldn't mind that, I can R-by it if you resend it. I'll still send a
v2 of this on the grounds that it's a strict improvement over existing
matters and might land faster.

Cheers,
Alejandro

>
> ~Andrew



  reply	other threads:[~2026-10-06 12:22 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 [this message]
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é

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=DLXR22SBHLW3.2SACLO55074LM@amd.com \
    --to=alejandro.garciavallejo@amd.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=andrew.cooper3@citrix.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.