linux-kernel - Re: [GIT PULL] RISC-V Updates for the 4.19 Merge Window

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 19 Aug 2018 08:10:37 -0700
From:   Guenter Roeck <linux@...ck-us.net>
To:     Karsten Merker <merker@...ian.org>
Cc:     Palmer Dabbelt <palmer@...ive.com>,
        linux-riscv@...ts.infradead.org,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] RISC-V Updates for the 4.19 Merge Window

On 08/19/2018 12:26 AM, Karsten Merker wrote:
[ ... ]
>> However, the she system boots fine with the same qemu command line if I use qemu
>> built from https://github.com/riscv/riscv-qemu.git, branch qemu-for-upstream.
> 
> Hello,
> 
> AFAICS the qemu patch that adds support for handling separate bbl
> and kernel images, i.e.
> 
>    https://github.com/riscv/riscv-qemu/commit/6338416ecf4717197c635b5abf9c17465d2d0da0
> 
> hasn't yet made it into upstream qemu, so using the "-bios"
> option for bbl generally doesn't work with (upstream) qemu 3.0.
> 

You are correct. With qemu 3.0+commit b79cd8dec5 ("RISC-V: Support separate firmware
and kernel payload") and this pull request plus "riscv: Drop setup_initrd" on top
of mainline, my test passes:

Build reference: riscv-for-linus-4.19-mw0-8897-gd028021652dd

Building virt:defconfig:initrd ... running .... passed
Building virt:defconfig:virtio-blk:rootfs ... running .... passed

... giving this an official

Tested-by: Guenter Roeck <linux@...ck-us.net>

Guenter