All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	 linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	 Nam Cao <namcao@linutronix.de>
Subject: Re: [PATCH 0/3] riscv: alternative: Statically compute alternative section boundaries and patch compat vDSO
Date: Thu, 6 Aug 2026 19:24:51 -0600 (MDT)	[thread overview]
Message-ID: <ba779b46-156b-61ae-ea35-6f575f6428a9@kernel.org> (raw)
In-Reply-To: <20260630-riscv-vdso32-alternative-v1-0-a32fd89b7b1c@linutronix.de>

[-- Attachment #1: Type: text/plain, Size: 588 bytes --]

On Tue, 30 Jun 2026, Thomas Weißschuh wrote:

> Currently the alternative sections are extracted from the vDSO
> binaries at runtime. This has runtime overhead and also doesn't
> work for the compat vDSO.
> 
> Extract the offsets of the alternative section during the build with the
> existing symbol extraction machinery and use those.
> 
> Also add support for the compat vDSO.
> 
> Link: https://lore.kernel.org/lkml/cover.1781876501.git.namcao@linutronix.de/
> Signed-off-by: Thomas Weißschuh (Schneider Electric) <thomas.weissschuh@linutronix.de>

Thanks, queued for v7.3.


- Paul

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

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

WARNING: multiple messages have this Message-ID (diff)
From: Paul Walmsley <pjw@kernel.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	 linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	 Nam Cao <namcao@linutronix.de>
Subject: Re: [PATCH 0/3] riscv: alternative: Statically compute alternative section boundaries and patch compat vDSO
Date: Thu, 6 Aug 2026 19:24:51 -0600 (MDT)	[thread overview]
Message-ID: <ba779b46-156b-61ae-ea35-6f575f6428a9@kernel.org> (raw)
In-Reply-To: <20260630-riscv-vdso32-alternative-v1-0-a32fd89b7b1c@linutronix.de>

[-- Attachment #1: Type: text/plain, Size: 588 bytes --]

On Tue, 30 Jun 2026, Thomas Weißschuh wrote:

> Currently the alternative sections are extracted from the vDSO
> binaries at runtime. This has runtime overhead and also doesn't
> work for the compat vDSO.
> 
> Extract the offsets of the alternative section during the build with the
> existing symbol extraction machinery and use those.
> 
> Also add support for the compat vDSO.
> 
> Link: https://lore.kernel.org/lkml/cover.1781876501.git.namcao@linutronix.de/
> Signed-off-by: Thomas Weißschuh (Schneider Electric) <thomas.weissschuh@linutronix.de>

Thanks, queued for v7.3.


- Paul

  parent reply	other threads:[~2026-08-07  1:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30  7:41 [PATCH 0/3] riscv: alternative: Statically compute alternative section boundaries and patch compat vDSO Thomas Weißschuh
2026-06-30  7:41 ` Thomas Weißschuh
2026-06-30  7:41 ` [PATCH 1/3] riscv: vdso: Add symbols for the alternative section boundaries Thomas Weißschuh
2026-06-30  7:41   ` Thomas Weißschuh
2026-06-30  7:41 ` [PATCH 2/3] riscv: alternative: Use the statically extracted vDSO section offsets Thomas Weißschuh
2026-06-30  7:41   ` Thomas Weißschuh
2026-06-30  7:41 ` [PATCH 3/3] riscv: alternative: Also patch the compat vDSO Thomas Weißschuh
2026-06-30  7:41   ` Thomas Weißschuh
2026-07-02  8:12 ` [PATCH 0/3] riscv: alternative: Statically compute alternative section boundaries and patch " Nam Cao
2026-07-02  8:12   ` Nam Cao
2026-08-07  1:24 ` Paul Walmsley [this message]
2026-08-07  1:24   ` Paul Walmsley

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=ba779b46-156b-61ae-ea35-6f575f6428a9@kernel.org \
    --to=pjw@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=namcao@linutronix.de \
    --cc=palmer@dabbelt.com \
    --cc=thomas.weissschuh@linutronix.de \
    /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.