From: Jisheng Zhang <jszhang@kernel.org>
To: Xiao Wang <xiao.w.wang@intel.com>
Cc: paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: alternative: remove alternative boundary symbols in vdso
Date: Mon, 4 Sep 2023 22:35:23 +0800 [thread overview]
Message-ID: <ZPXrKz1jhqz5g3nF@xhacker> (raw)
In-Reply-To: <20230902022510.818602-1-xiao.w.wang@intel.com>
On Sat, Sep 02, 2023 at 10:25:10AM +0800, Xiao Wang wrote:
> Instruction patching for vdso is based on elf header parsing to get the
> beginning and ending of .alternative section, the __alt_start and __alt_end
> symbols defined in vdso linker script are not used, so this patch removes
> them.
The same patch has been in mailist since July:
https://lore.kernel.org/linux-riscv/20230726173024.3684-2-jszhang@kernel.org/
Thanks
>
> Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>
> ---
> arch/riscv/kernel/vdso/vdso.lds.S | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/arch/riscv/kernel/vdso/vdso.lds.S b/arch/riscv/kernel/vdso/vdso.lds.S
> index 82ce64900f3d..d43fd7c7dd11 100644
> --- a/arch/riscv/kernel/vdso/vdso.lds.S
> +++ b/arch/riscv/kernel/vdso/vdso.lds.S
> @@ -42,9 +42,7 @@ SECTIONS
>
> . = ALIGN(4);
> .alternative : {
> - __alt_start = .;
> *(.alternative)
> - __alt_end = .;
> }
>
> .data : {
> --
> 2.25.1
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-09-04 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-02 2:25 [PATCH] riscv: alternative: remove alternative boundary symbols in vdso Xiao Wang
2023-09-04 14:35 ` Jisheng Zhang [this message]
2023-09-05 9:49 ` Wang, Xiao W
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=ZPXrKz1jhqz5g3nF@xhacker \
--to=jszhang@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=xiao.w.wang@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox