On Fri, Sep 27, 2019 at 1:58 PM Andy Lutomirski <luto@xxxxxxxxxx> wrote: > > On Tue, Sep 3, 2019 at 3:27 PM Palmer Dabbelt <palmer@xxxxxxxxxx> wrote: > > > > On Wed, 28 Aug 2019 10:52:05 PDT (-0700), luto@xxxxxxxxxxxxxx wrote: > > > > > > > > >> On Aug 25, 2019, at 2:59 PM, Kees Cook <keescook@xxxxxxxxxxxx> wrote: > > >> > > >>> On Thu, Aug 22, 2019 at 01:55:22PM -0700, David Abdurachmanov wrote: > > >>> This patch was extensively tested on Fedora/RISCV (applied by default on > > >>> top of 5.2-rc7 kernel for <2 months). The patch was also tested with 5.3-rc > > >>> on QEMU and SiFive Unleashed board. > > >> > > >> Oops, I see the mention of QEMU here. Where's the best place to find > > >> instructions on creating a qemu riscv image/environment? > > > > > > I don’t suppose one of you riscv folks would like to contribute riscv support to virtme? virtme-run —arch=riscv would be quite nice, and the total patch should be just a couple lines. Unfortunately, it helps a lot to understand the subtleties of booting the architecture to write those couple lines :) > > FYI, it works now: $ virtme-configkernel --arch=riscv --defconfig GEN Makefile [...] Configured. Build with 'make ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu- -j4' $ make ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu- -j4 [...] $ virtme-run --kdir=. --arch=riscv64 --mods=auto --root [path to a riscv filesystem] This is with virtme master and a qemu-system-riscv64 from qemu git on my path. It does *not* work with Fedora 30's qemu. So now you can all jump on the virtme bandwagon and have an easy way to test riscv kernels. :) Although, if you want to run kernel selftests, you may find the process of actually running them to be more fun if you use --rodir or --rwdir to map the kernel selftests directory into the guest.
