All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joey Gouly <joey.gouly@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: <linux-arm-kernel@lists.infradead.org>, <nd@arm.com>,
	<andre.przywara@arm.com>, <catalin.marinas@arm.com>,
	<vincenzo.frascino@arm.com>, <will@kernel.org>
Subject: Re: [PATCH v1 2/3] arm64: alternative: patch alternatives in the vDSO
Date: Thu, 25 Aug 2022 15:57:27 +0100	[thread overview]
Message-ID: <20220825145727.GA46645@e124191.cambridge.arm.com> (raw)
In-Reply-To: <Ywd25KlBOabxvWHs@FVFF77S0Q05N>

Hi Mark,

Thanks for the review!

On Thu, Aug 25, 2022 at 02:19:32PM +0100, Mark Rutland wrote:
> On Thu, Aug 25, 2022 at 11:20:24AM +0100, Joey Gouly wrote:
> > Make it possible to use alternatives in the vDSO, so that better
> > implementations can be used if possible.
> > 
> > Signed-off-by: Joey Gouly <joey.gouly@arm.com>
> > Cc: Catalin Marinas <catalin.marinas@arm.com>
> > Cc: Will Deacon <will@kernel.org>
> > Cc: Vincenzo Frascino <vincenzo.frascino@arm.com>
> > Cc: Mark Rutland <mark.rutland@arm.com>
> > ---
> >  arch/arm64/include/asm/vdso.h     |  3 +++
> >  arch/arm64/kernel/alternative.c   | 25 +++++++++++++++++++++++++
> >  arch/arm64/kernel/vdso.c          |  3 ---
> >  arch/arm64/kernel/vdso/vdso.lds.S |  7 +++++++
> >  4 files changed, 35 insertions(+), 3 deletions(-)
> > 
[..]
> > +void apply_alternatives_vdso(unsigned long *feature_mask)
> > +{
> > +	struct alt_region region;
> > +	const struct elf64_hdr *hdr;
> > +	const struct elf64_shdr *shdr;
> > +	const struct elf64_shdr *alt;
> > +
> > +	hdr = (struct elf64_hdr *)vdso_start;
> > +	shdr = (void *)hdr + hdr->e_shoff;
> > +	alt = find_section(hdr, shdr, ".altinstructions");
> > +	if (!alt)
> > +		return;
> > +
> > +	region = (struct alt_region){
> > +		.begin	= (void *)hdr + alt->sh_offset,
> > +		.end	= (void *)hdr + alt->sh_offset + alt->sh_size,
> > +	};
> > +
> > +	__apply_alternatives(&region, false, feature_mask);
> > +}
> > +
> >  /*
> >   * We might be patching the stop_machine state machine, so implement a
> >   * really simple polling protocol here.
> > @@ -216,6 +240,7 @@ static int __apply_alternatives_multi_stop(void *unused)
> >  
> >  		BUG_ON(all_alternatives_applied);
> >  		__apply_alternatives(&region, false, remaining_capabilities);
> > +		apply_alternatives_vdso(remaining_capabilities);
> 
> Since we didn't patch the vdso in apply_boot_alternatives(), using
> `remaining_capabilities` means that we could in theory miss alternatives for
> features which were detected on the boot CPU.
> 
> Since the VDSO cannot be concurrently executed within the kernel, we could
> hoist the call to apply_alternatives_vdso() out of
> __apply_alternatives_multi_stop(), and call it before the stop_machine in
> apply_alternatives_all().
> 
> That would keep __apply_alternatives_multi_stop() simple (and easier to make
> noinstr-safe), and we could use the same mask logic as
> apply_alternatives_module(), e.g.
> 
> void apply_alternatives_vdso(void)
> {
> 	DECLARE_BITMAP(all_capabilities, ARM64_NPATCHABLE);
> 	bitmap_fill(all_capabilities, ARM64_NPATCHABLE);
> 
> 	struct alt_region region;
> 	const struct elf64_hdr *hdr;
> 	const struct elf64_shdr *shdr;
> 	const struct elf64_shdr *alt;
> 
> 	hdr = (struct elf64_hdr *)vdso_start;
> 	shdr = (void *)hdr + hdr->e_shoff;
> 	alt = find_section(hdr, shdr, ".altinstructions");
> 	if (!alt)
> 	return;
> 
> 	region = (struct alt_region){
> 		.begin	= (void *)hdr + alt->sh_offset,
> 		.end	= (void *)hdr + alt->sh_offset + alt->sh_size,
> 	};
> 
> 	__apply_alternatives(&region, false, &all_capabilities[0]);
> }
> 
> ... does that sound ok to you?

Yep, this makes sense, will send a v2 with this and the fixes for the other patch.

Thanks,
Joey

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-08-25 14:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25 10:20 [PATCH v1 0/3] Use CNTVCTSS_EL0 in gettimeofday() Joey Gouly
2022-08-25 10:20 ` [PATCH v1 1/3] arm64: module: move find_section to header Joey Gouly
2022-08-25 13:19   ` Mark Rutland
2022-08-25 10:20 ` [PATCH v1 2/3] arm64: alternative: patch alternatives in the vDSO Joey Gouly
2022-08-25 13:19   ` Mark Rutland
2022-08-25 14:57     ` Joey Gouly [this message]
2022-08-25 10:20 ` [PATCH v1 3/3] arm64: vdso: use SYS_CNTVCTSS_EL0 for gettimeofday Joey Gouly
2022-08-25 13:24   ` Mark Rutland

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=20220825145727.GA46645@e124191.cambridge.arm.com \
    --to=joey.gouly@arm.com \
    --cc=andre.przywara@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=nd@arm.com \
    --cc=vincenzo.frascino@arm.com \
    --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 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.