From: Nam Cao <namcao@linutronix.de>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
"Thomas Weißschuh (Schneider Electric)"
<thomas.weissschuh@linutronix.de>
Subject: Re: [PATCH 0/3] riscv: alternative: Statically compute alternative section boundaries and patch compat vDSO
Date: Thu, 02 Jul 2026 10:12:56 +0200 [thread overview]
Message-ID: <87fr21vmgn.fsf@yellow.woof> (raw)
In-Reply-To: <20260630-riscv-vdso32-alternative-v1-0-a32fd89b7b1c@linutronix.de>
Thomas Weißschuh <thomas.weissschuh@linutronix.de> writes:
> 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.
Reviewed-by: Nam Cao <namcao@linutronix.de>
WARNING: multiple messages have this Message-ID (diff)
From: Nam Cao <namcao@linutronix.de>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
"Thomas Weißschuh (Schneider Electric)"
<thomas.weissschuh@linutronix.de>
Subject: Re: [PATCH 0/3] riscv: alternative: Statically compute alternative section boundaries and patch compat vDSO
Date: Thu, 02 Jul 2026 10:12:56 +0200 [thread overview]
Message-ID: <87fr21vmgn.fsf@yellow.woof> (raw)
In-Reply-To: <20260630-riscv-vdso32-alternative-v1-0-a32fd89b7b1c@linutronix.de>
Thomas Weißschuh <thomas.weissschuh@linutronix.de> writes:
> 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.
Reviewed-by: Nam Cao <namcao@linutronix.de>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-07-02 8:12 UTC|newest]
Thread overview: 10+ 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 ` Nam Cao [this message]
2026-07-02 8:12 ` [PATCH 0/3] riscv: alternative: Statically compute alternative section boundaries and patch " Nam Cao
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=87fr21vmgn.fsf@yellow.woof \
--to=namcao@linutronix.de \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--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.