public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Zhangjin Wu <falcon@tinylab.org>
To: Palmer Dabbelt <palmer@rivosinc.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Guo Ren <guoren@kernel.org>, Albert Ou <aou@eecs.berkeley.edu>
Cc: Eric Biederman <ebiederm@xmission.com>,
	Kees Cook <keescook@chromium.org>,
	Conor Dooley <conor.dooley@microchip.com>,
	linux-riscv@lists.infradead.org, Zhangjin Wu <falcon@tinylab.org>
Subject: [RFC PATCH 0/1] riscv: Allow disable vdso support
Date: Fri, 19 May 2023 01:47:39 +0800	[thread overview]
Message-ID: <cover.1684430522.git.falcon@tinylab.org> (raw)

This is part of my tinylinux work for RISC-V, see related patchsets:

* RISC-V: Enable dead code elimination, v3 [1]
* tools/nolibc: riscv: Fix up compile error for rv32, v1 [2]
* Add dead syscalls elimination support, RFC [3]

This patch allows to remove the whole vdso support out of the kernel
binary and shrink 4KB for compat vdso and shrink another 8KB for vdso.

Unfortunately, just found there is a big vdso framework change from the
just sent-out RFC patchset from Guoren:

    * riscv: s64ilp32: Running 32-bit Linux kernel on 64-bit supervisor mode [4]

That patchset unifies vdso32 & compat_vdso into vdso/Makefile, so, it is
possible to rebase our work on that patchset or simply let VDSO64 and
VDSO32 configurable in that patchset.

Best Regards,
Zhangjin Wu
---

[1]: https://lore.kernel.org/linux-riscv/20230517084134.37892-1-falcon@tinylab.org/T/#t
[2]: https://lore.kernel.org/linux-riscv/cover.1684425792.git.falcon@tinylab.org/T/#t
[3]: https://lore.kernel.org/linux-riscv/cover.1676594211.git.falcon@tinylab.org/
[4]: https://lore.kernel.org/linux-riscv/mhng-24855381-7da8-4c77-bcaf-a3a53c8cb38b@palmer-ri-x1c9/T/#t

Zhangjin Wu (1):
  riscv: add Kconfig.vdso

 arch/riscv/Kconfig                |  6 +-----
 arch/riscv/Kconfig.vdso           | 28 ++++++++++++++++++++++++++++
 arch/riscv/Makefile               |  8 +++++---
 arch/riscv/include/asm/elf.h      |  6 ++++--
 arch/riscv/include/asm/mmu.h      |  2 ++
 arch/riscv/include/asm/vdso.h     |  8 ++++----
 arch/riscv/kernel/Makefile        |  4 ++--
 arch/riscv/kernel/alternative.c   |  2 +-
 arch/riscv/kernel/compat_signal.c |  2 ++
 arch/riscv/kernel/entry.S         |  2 +-
 arch/riscv/kernel/signal.c        |  4 ++--
 arch/riscv/kernel/sys_riscv.c     |  2 +-
 arch/riscv/kernel/vdso.c          | 10 +++++-----
 13 files changed, 58 insertions(+), 26 deletions(-)
 create mode 100644 arch/riscv/Kconfig.vdso

-- 
2.25.1


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

             reply	other threads:[~2023-05-18 17:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 17:47 Zhangjin Wu [this message]
2023-05-18 17:48 ` [RFC PATCH 1/1] riscv: add Kconfig.vdso Zhangjin Wu
2023-09-25 15:08   ` Palmer Dabbelt
2023-10-03  6:39   ` Zhangjin Wu

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=cover.1684430522.git.falcon@tinylab.org \
    --to=falcon@tinylab.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor.dooley@microchip.com \
    --cc=ebiederm@xmission.com \
    --cc=guoren@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@rivosinc.com \
    --cc=paul.walmsley@sifive.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