linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: "Alexandre Ghiti" <alexghiti@rivosinc.com>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Paul Walmsley" <paul.walmsley@sifive.com>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	"Conor Dooley" <conor@kernel.org>,
	"Björn Töpel" <bjorn@kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org,
	"Björn Töpel" <bjorn@rivosinc.com>,
	nathan@kernel.org, llvm@lists.linux.dev, ndesaulniers@google.com
Subject: Re: [PATCH v7 1/1] riscv: Allow to downgrade paging mode from the command line
Date: Mon, 27 Feb 2023 13:56:55 +0100	[thread overview]
Message-ID: <CAMj1kXGCkqpHY7rHZv0EFKhPNk6jpbh1OfG_Jm3vSW8c5Y+9_A@mail.gmail.com> (raw)
In-Reply-To: <Y/yilORflGv3vXjX@wendy>

On Mon, 27 Feb 2023 at 13:32, Conor Dooley <conor.dooley@microchip.com> wrote:
>
> Hey Alex, clang/llvm folk,
>
> On Fri, Feb 24, 2023 at 11:02:18AM +0100, Alexandre Ghiti wrote:
> > Add 2 early command line parameters that allow to downgrade satp mode
> > (using the same naming as x86):
> > - "no5lvl": use a 4-level page table (down from sv57 to sv48)
> > - "no4lvl": use a 3-level page table (down from sv57/sv48 to sv39)
> >
> > Note that going through the device tree to get the kernel command line
> > works with ACPI too since the efi stub creates a device tree anyway with
> > the command line.
> >
> > In KASAN kernels, we can't use the libfdt that early in the boot process
> > since we are not ready to execute instrumented functions. So instead of
> > using the "generic" libfdt, we compile our own versions of those functions
> > that are not instrumented and that are prefixed so that they do not
> > conflict with the generic ones. We also need the non-instrumented versions
> > of the string functions and the prefixed versions of memcpy/memmove.
> >
> > This is largely inspired by commit aacd149b6238 ("arm64: head: avoid
> > relocating the kernel twice for KASLR") from which I removed compilation
> > flags that were not relevant to RISC-V at the moment (LTO, SCS, pie).
> >
> > Signed-off-by: Alexandre Ghiti <alexghiti@rivosinc.com>
> > Tested-by: Björn Töpel <bjorn@rivosinc.com>
> > Reviewed-by: Björn Töpel <bjorn@rivosinc.com>
> > ---
> >  .../admin-guide/kernel-parameters.txt         |  5 +-
> >  arch/riscv/kernel/Makefile                    |  2 +
> >  arch/riscv/kernel/pi/Makefile                 | 37 +++++++++++
> >  arch/riscv/kernel/pi/cmdline_early.c          | 62 +++++++++++++++++++
>
> +      4 ld.lld: warning: vmlinux.a(arch/riscv/kernel/pi/string.pi.o):(.init.sdata) is being placed in '.init.sdata'
>
> I'm getting 4 new linker warnings with LLVM=1 clang-15 allmodconfig
> builds - but I don't really understand this issue.
> Is this spurious, and a just consequence of...
>
> > diff --git a/arch/riscv/kernel/pi/Makefile b/arch/riscv/kernel/pi/Makefile
> > new file mode 100644
> > index 000000000000..4002ed94b6d3
> > --- /dev/null
> > +++ b/arch/riscv/kernel/pi/Makefile
> > @@ -0,0 +1,37 @@
> > +# SPDX-License-Identifier: GPL-2.0
> > +# This file was copied from arm64/kernel/pi/Makefile.
> > +
> > +KBUILD_CFLAGS        := $(subst $(CC_FLAGS_FTRACE),,$(KBUILD_CFLAGS)) \
> > +                -Os -DDISABLE_BRANCH_PROFILING $(DISABLE_STACKLEAK_PLUGIN) \
> > +                $(call cc-option,-mbranch-protection=none) \
> > +                -I$(srctree)/scripts/dtc/libfdt -fno-stack-protector \
> > +                -D__DISABLE_EXPORTS -ffreestanding \
> > +                -fno-asynchronous-unwind-tables -fno-unwind-tables \
> > +                $(call cc-option,-fno-addrsig)
> > +
> > +CFLAGS_cmdline_early.o += -D__NO_FORTIFY
> > +CFLAGS_lib-fdt_ro.o += -D__NO_FORTIFY
> > +
> > +GCOV_PROFILE := n
> > +KASAN_SANITIZE       := n
> > +KCSAN_SANITIZE       := n
> > +UBSAN_SANITIZE       := n
> > +KCOV_INSTRUMENT      := n
> > +
> > +$(obj)/%.pi.o: OBJCOPYFLAGS := --prefix-symbols=__pi_ \
> > +                            --remove-section=.note.gnu.property \
> > +                            --prefix-alloc-sections=.init
>
> ...this?
>

Yes. if the input object has a .sdata section, the output .pi.o object
will have a .init.sdata section, and if the common linker script does
not place it explicitly, you will get a warning. Note that we switched
to --orphan-handling=error on other arches, as the linker sometimes
does unexpected things with sections it doesn't know about.

I'd imagine this needs to be combined with .init.data

  reply	other threads:[~2023-02-27 12:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24 10:02 [PATCH v7 0/1] riscv: Allow to downgrade paging mode from the command line Alexandre Ghiti
2023-02-24 10:02 ` [PATCH v7 1/1] " Alexandre Ghiti
2023-02-27 12:31   ` Conor Dooley
2023-02-27 12:56     ` Ard Biesheuvel [this message]
2023-02-27 13:27       ` Alexandre Ghiti
2023-02-27 13:42         ` Conor Dooley

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=CAMj1kXGCkqpHY7rHZv0EFKhPNk6jpbh1OfG_Jm3vSW8c5Y+9_A@mail.gmail.com \
    --to=ardb@kernel.org \
    --cc=alexghiti@rivosinc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=bjorn@kernel.org \
    --cc=bjorn@rivosinc.com \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=palmer@dabbelt.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;
as well as URLs for NNTP newsgroup(s).