Messages in this thread | | | Date | Tue, 27 Feb 2024 12:51:04 -0600 | Subject | Re: [PATCH 0/4] riscv: 64-bit NOMMU fixes and enhancements | From | Samuel Holland <> |
| |
Hi Conor,
On 2024-02-27 6:13 AM, Conor Dooley wrote: > On Mon, Feb 26, 2024 at 04:34:45PM -0800, Samuel Holland wrote: >> This series aims to improve support for NOMMU, specifically by making it >> easier to test NOMMU kernels in QEMU and on various widely-available >> hardware (errata permitting). After all, everything supports Svbare... >> >> After applying this series, a NOMMU kernel based on defconfig (changing >> only the three options below*) boots to userspace on QEMU when passed as >> -kernel. >> >> # CONFIG_RISCV_M_MODE is not set >> # CONFIG_MMU is not set >> CONFIG_NONPORTABLE=y >> >> *if you are using LLD, you must also disable BPF_SYSCALL and KALLSYMS, >> because LLD bails on out-of-range references to undefined weak symbols. > > That's not new to these patches though, right? IIRC that's an existing > issue.
Yes, that's correct. I see that arch/riscv/configs/nommu_* have KALLSYMS disabled already; this may be the reason.
Regards, Samuel
| |