Re: [GIT PULL] RISC-V Updates for the 4.19 Merge Window
On Tue, 21 Aug 2018 12:45:50 PDT (-0700), mer...@debian.org wrote: On Tue, Aug 21, 2018 at 11:31:48AM -0700, Palmer Dabbelt wrote: On Sat, 18 Aug 2018 06:37:59 PDT (-0700), li...@roeck-us.net wrote: [...] > Do you have vmlinux embedded in bbl ? > > With separate bbl and vmlinux, and the following qemu command line > (with qemu 3.0) > > qemu-system-riscv64 -M virt -m 512M -no-reboot \ >-bios bbl -kernel vmlinux \ >-netdev user,id=net0 -device virtio-net-device,netdev=net0 \ >-device virtio-blk-device,drive=d0 \ >-drive file=rootfs.ext2,if=none,id=d0,format=raw \ >-append 'root=/dev/vda rw console=ttyS0,115200' \ >-nographic -monitor none > > all I get is > > rom: requested regions overlap (rom mrom.reset. free=0x0001cbe8, addr=0x1000) > > 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. Yes, I have a vmlinux built into my BBL. I didn't actually look closely at the command line I was copying and see that vmlinux in there, my guess would be that it's getting ignored. I don't remember if upstream BBL actually works with the split bbl/vmlinux setup, I've kind of stopped paying attention to BBL as I'm just waiting for someone to tell me instructions as to how to use a real bootloader... :) JFTR, upstream bbl supports the split bbl/vmlinux setup, it's just upstream qemu that lacks the support for now (qemu-riscv has it). Thanks!
Re: [GIT PULL] RISC-V Updates for the 4.19 Merge Window
On Tue, 21 Aug 2018 12:45:50 PDT (-0700), mer...@debian.org wrote: On Tue, Aug 21, 2018 at 11:31:48AM -0700, Palmer Dabbelt wrote: On Sat, 18 Aug 2018 06:37:59 PDT (-0700), li...@roeck-us.net wrote: [...] > Do you have vmlinux embedded in bbl ? > > With separate bbl and vmlinux, and the following qemu command line > (with qemu 3.0) > > qemu-system-riscv64 -M virt -m 512M -no-reboot \ >-bios bbl -kernel vmlinux \ >-netdev user,id=net0 -device virtio-net-device,netdev=net0 \ >-device virtio-blk-device,drive=d0 \ >-drive file=rootfs.ext2,if=none,id=d0,format=raw \ >-append 'root=/dev/vda rw console=ttyS0,115200' \ >-nographic -monitor none > > all I get is > > rom: requested regions overlap (rom mrom.reset. free=0x0001cbe8, addr=0x1000) > > 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. Yes, I have a vmlinux built into my BBL. I didn't actually look closely at the command line I was copying and see that vmlinux in there, my guess would be that it's getting ignored. I don't remember if upstream BBL actually works with the split bbl/vmlinux setup, I've kind of stopped paying attention to BBL as I'm just waiting for someone to tell me instructions as to how to use a real bootloader... :) JFTR, upstream bbl supports the split bbl/vmlinux setup, it's just upstream qemu that lacks the support for now (qemu-riscv has it). Thanks!
Re: [GIT PULL] RISC-V Updates for the 4.19 Merge Window
On Sat, 18 Aug 2018 11:15:18 PDT (-0700), Linus Torvalds wrote: On Fri, Aug 17, 2018 at 1:28 PM Palmer Dabbelt wrote: I remember having sent this on Wednesday, but for some reason I don't see it in your tree or my outbox so I might be crazy. You might indeed have been having hallucinations. I don't see any other pull request from you in my mailbox than this one. Google does find a posting from you saying "Below is the pull request I plan to submit on Wednesday morning" on the RISC-V development google group list, so I think you just remembered your _plan_, not your actual email ... That does sound like something I would do... It's odd because I remember specifically being excited that I finally got the arguments to "git send-pull" correct, but I guess that excitement was pre-mature :) Anyway, I can confirm that this new pull request is now in my queue even if I don't see any earlier ones. Thanks! I'm planning on submitting another PR tomorrow (which has been baking since yesterday like it's supposed to), so fingers crossed I'm slightly less crazy this week.
Re: [GIT PULL] RISC-V Updates for the 4.19 Merge Window
On Sat, 18 Aug 2018 06:37:59 PDT (-0700), li...@roeck-us.net wrote: Hi Palmer, On Fri, Aug 17, 2018 at 01:28:11PM -0700, Palmer Dabbelt wrote: [ ... ] This tag boots a Fedora root filesystem on QEMU's master branch for me, and before this morning's rebase (from 4.18-rc8 to 4.18) it booted on the HiFive Unleashed. Do you have vmlinux embedded in bbl ? With separate bbl and vmlinux, and the following qemu command line (with qemu 3.0) qemu-system-riscv64 -M virt -m 512M -no-reboot \ -bios bbl -kernel vmlinux \ -netdev user,id=net0 -device virtio-net-device,netdev=net0 \ -device virtio-blk-device,drive=d0 \ -drive file=rootfs.ext2,if=none,id=d0,format=raw \ -append 'root=/dev/vda rw console=ttyS0,115200' \ -nographic -monitor none all I get is rom: requested regions overlap (rom mrom.reset. free=0x0001cbe8, addr=0x1000) 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. Yes, I have a vmlinux built into my BBL. I didn't actually look closely at the command line I was copying and see that vmlinux in there, my guess would be that it's getting ignored. I don't remember if upstream BBL actually works with the split bbl/vmlinux setup, I've kind of stopped paying attention to BBL as I'm just waiting for someone to tell me instructions as to how to use a real bootloader... :) I'm building master from QEMU as of a few weeks ago * f7502360397d - (HEAD -> master, tag: v3.0.0-rc3, origin/master, origin/HEAD) Update version for v3.0.0-rc3 release (3 weeks ago) * b89041647422 - Merge remote-tracking branch 'remotes/armbru/tags/pull-monitor-2018-07-31' into staging (3 weeks ago) |\ | * 9a1054061c62 - monitor: temporary fix for dead-lock on event recursion (3 weeks ago) |/ * 42e76456cf68 - Merge remote-tracking branch 'remotes/vivier2/tags/linux-user-for-3.0-pull-request' into staging (3 weeks ago) |\ | * 5d9f3ea08172 - linux-user: ppc64: don't use volatile register during safe_syscall (3 weeks ago) | * 28cbb997d66e - tests: add check_invalid_maps to test-mmap (3 weeks ago) | * 38138fab9358 - linux-user/mmap.c: handle invalid len maps correctly (3 weeks ago) * | 45a505d0a4b3 - Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (3 weeks ago) in general once we get a port upstream I jump over to using master from upstream as that way we'll find any bugs quickly. Michael Clark has a pretty big QEMU patch queue, but nothing appears to be critical for Linux boot. Excellent - once this series hits mainline, I'll add riscv to my boot tests. Thanks! I'm super excited to get CI stuff up and running as now that we can boot I'm worried people will notice when I screw something up :)
Re: [GIT PULL] RISC-V Updates for the 4.19 Merge Window
On Sat, 18 Aug 2018 11:15:18 PDT (-0700), Linus Torvalds wrote: On Fri, Aug 17, 2018 at 1:28 PM Palmer Dabbelt wrote: I remember having sent this on Wednesday, but for some reason I don't see it in your tree or my outbox so I might be crazy. You might indeed have been having hallucinations. I don't see any other pull request from you in my mailbox than this one. Google does find a posting from you saying "Below is the pull request I plan to submit on Wednesday morning" on the RISC-V development google group list, so I think you just remembered your _plan_, not your actual email ... That does sound like something I would do... It's odd because I remember specifically being excited that I finally got the arguments to "git send-pull" correct, but I guess that excitement was pre-mature :) Anyway, I can confirm that this new pull request is now in my queue even if I don't see any earlier ones. Thanks! I'm planning on submitting another PR tomorrow (which has been baking since yesterday like it's supposed to), so fingers crossed I'm slightly less crazy this week.
Re: [GIT PULL] RISC-V Updates for the 4.19 Merge Window
On Sat, 18 Aug 2018 06:37:59 PDT (-0700), li...@roeck-us.net wrote: Hi Palmer, On Fri, Aug 17, 2018 at 01:28:11PM -0700, Palmer Dabbelt wrote: [ ... ] This tag boots a Fedora root filesystem on QEMU's master branch for me, and before this morning's rebase (from 4.18-rc8 to 4.18) it booted on the HiFive Unleashed. Do you have vmlinux embedded in bbl ? With separate bbl and vmlinux, and the following qemu command line (with qemu 3.0) qemu-system-riscv64 -M virt -m 512M -no-reboot \ -bios bbl -kernel vmlinux \ -netdev user,id=net0 -device virtio-net-device,netdev=net0 \ -device virtio-blk-device,drive=d0 \ -drive file=rootfs.ext2,if=none,id=d0,format=raw \ -append 'root=/dev/vda rw console=ttyS0,115200' \ -nographic -monitor none all I get is rom: requested regions overlap (rom mrom.reset. free=0x0001cbe8, addr=0x1000) 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. Yes, I have a vmlinux built into my BBL. I didn't actually look closely at the command line I was copying and see that vmlinux in there, my guess would be that it's getting ignored. I don't remember if upstream BBL actually works with the split bbl/vmlinux setup, I've kind of stopped paying attention to BBL as I'm just waiting for someone to tell me instructions as to how to use a real bootloader... :) I'm building master from QEMU as of a few weeks ago * f7502360397d - (HEAD -> master, tag: v3.0.0-rc3, origin/master, origin/HEAD) Update version for v3.0.0-rc3 release (3 weeks ago) * b89041647422 - Merge remote-tracking branch 'remotes/armbru/tags/pull-monitor-2018-07-31' into staging (3 weeks ago) |\ | * 9a1054061c62 - monitor: temporary fix for dead-lock on event recursion (3 weeks ago) |/ * 42e76456cf68 - Merge remote-tracking branch 'remotes/vivier2/tags/linux-user-for-3.0-pull-request' into staging (3 weeks ago) |\ | * 5d9f3ea08172 - linux-user: ppc64: don't use volatile register during safe_syscall (3 weeks ago) | * 28cbb997d66e - tests: add check_invalid_maps to test-mmap (3 weeks ago) | * 38138fab9358 - linux-user/mmap.c: handle invalid len maps correctly (3 weeks ago) * | 45a505d0a4b3 - Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (3 weeks ago) in general once we get a port upstream I jump over to using master from upstream as that way we'll find any bugs quickly. Michael Clark has a pretty big QEMU patch queue, but nothing appears to be critical for Linux boot. Excellent - once this series hits mainline, I'll add riscv to my boot tests. Thanks! I'm super excited to get CI stuff up and running as now that we can boot I'm worried people will notice when I screw something up :)
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
Guenter
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
Guenter
Re: [GIT PULL] RISC-V Updates for the 4.19 Merge Window
On Sat, Aug 18, 2018 at 06:37:59AM -0700, Guenter Roeck wrote: > On Fri, Aug 17, 2018 at 01:28:11PM -0700, Palmer Dabbelt wrote: > [ ... ] > > > > This tag boots a Fedora root filesystem on QEMU's master branch for me, > > and before this morning's rebase (from 4.18-rc8 to 4.18) it booted on > > the HiFive Unleashed. > > Do you have vmlinux embedded in bbl ? > > With separate bbl and vmlinux, and the following qemu command line > (with qemu 3.0) > > qemu-system-riscv64 -M virt -m 512M -no-reboot \ > -bios bbl -kernel vmlinux \ > -netdev user,id=net0 -device virtio-net-device,netdev=net0 \ > -device virtio-blk-device,drive=d0 \ > -drive file=rootfs.ext2,if=none,id=d0,format=raw \ > -append 'root=/dev/vda rw console=ttyS0,115200' \ > -nographic -monitor none > > all I get is > > rom: requested regions overlap (rom mrom.reset. free=0x0001cbe8, > addr=0x1000) > > 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. Regards, Karsten -- Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der Werbung sowie der Markt- oder Meinungsforschung.
Re: [GIT PULL] RISC-V Updates for the 4.19 Merge Window
On Sat, Aug 18, 2018 at 06:37:59AM -0700, Guenter Roeck wrote: > On Fri, Aug 17, 2018 at 01:28:11PM -0700, Palmer Dabbelt wrote: > [ ... ] > > > > This tag boots a Fedora root filesystem on QEMU's master branch for me, > > and before this morning's rebase (from 4.18-rc8 to 4.18) it booted on > > the HiFive Unleashed. > > Do you have vmlinux embedded in bbl ? > > With separate bbl and vmlinux, and the following qemu command line > (with qemu 3.0) > > qemu-system-riscv64 -M virt -m 512M -no-reboot \ > -bios bbl -kernel vmlinux \ > -netdev user,id=net0 -device virtio-net-device,netdev=net0 \ > -device virtio-blk-device,drive=d0 \ > -drive file=rootfs.ext2,if=none,id=d0,format=raw \ > -append 'root=/dev/vda rw console=ttyS0,115200' \ > -nographic -monitor none > > all I get is > > rom: requested regions overlap (rom mrom.reset. free=0x0001cbe8, > addr=0x1000) > > 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. Regards, Karsten -- Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der Werbung sowie der Markt- oder Meinungsforschung.
Re: [GIT PULL] RISC-V Updates for the 4.19 Merge Window
On Fri, Aug 17, 2018 at 1:28 PM Palmer Dabbelt wrote: > > I remember having sent this on Wednesday, but for some reason I don't see it > in > your tree or my outbox so I might be crazy. You might indeed have been having hallucinations. I don't see any other pull request from you in my mailbox than this one. Google does find a posting from you saying "Below is the pull request I plan to submit on Wednesday morning" on the RISC-V development google group list, so I think you just remembered your _plan_, not your actual email ... Anyway, I can confirm that this new pull request is now in my queue even if I don't see any earlier ones. Linus
Re: [GIT PULL] RISC-V Updates for the 4.19 Merge Window
On Fri, Aug 17, 2018 at 1:28 PM Palmer Dabbelt wrote: > > I remember having sent this on Wednesday, but for some reason I don't see it > in > your tree or my outbox so I might be crazy. You might indeed have been having hallucinations. I don't see any other pull request from you in my mailbox than this one. Google does find a posting from you saying "Below is the pull request I plan to submit on Wednesday morning" on the RISC-V development google group list, so I think you just remembered your _plan_, not your actual email ... Anyway, I can confirm that this new pull request is now in my queue even if I don't see any earlier ones. Linus
Re: [GIT PULL] RISC-V Updates for the 4.19 Merge Window
Hi Palmer, On Fri, Aug 17, 2018 at 01:28:11PM -0700, Palmer Dabbelt wrote: [ ... ] > > This tag boots a Fedora root filesystem on QEMU's master branch for me, > and before this morning's rebase (from 4.18-rc8 to 4.18) it booted on > the HiFive Unleashed. > Do you have vmlinux embedded in bbl ? With separate bbl and vmlinux, and the following qemu command line (with qemu 3.0) qemu-system-riscv64 -M virt -m 512M -no-reboot \ -bios bbl -kernel vmlinux \ -netdev user,id=net0 -device virtio-net-device,netdev=net0 \ -device virtio-blk-device,drive=d0 \ -drive file=rootfs.ext2,if=none,id=d0,format=raw \ -append 'root=/dev/vda rw console=ttyS0,115200' \ -nographic -monitor none all I get is rom: requested regions overlap (rom mrom.reset. free=0x0001cbe8, addr=0x1000) 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. Excellent - once this series hits mainline, I'll add riscv to my boot tests. Thanks, Guenter
Re: [GIT PULL] RISC-V Updates for the 4.19 Merge Window
Hi Palmer, On Fri, Aug 17, 2018 at 01:28:11PM -0700, Palmer Dabbelt wrote: [ ... ] > > This tag boots a Fedora root filesystem on QEMU's master branch for me, > and before this morning's rebase (from 4.18-rc8 to 4.18) it booted on > the HiFive Unleashed. > Do you have vmlinux embedded in bbl ? With separate bbl and vmlinux, and the following qemu command line (with qemu 3.0) qemu-system-riscv64 -M virt -m 512M -no-reboot \ -bios bbl -kernel vmlinux \ -netdev user,id=net0 -device virtio-net-device,netdev=net0 \ -device virtio-blk-device,drive=d0 \ -drive file=rootfs.ext2,if=none,id=d0,format=raw \ -append 'root=/dev/vda rw console=ttyS0,115200' \ -nographic -monitor none all I get is rom: requested regions overlap (rom mrom.reset. free=0x0001cbe8, addr=0x1000) 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. Excellent - once this series hits mainline, I'll add riscv to my boot tests. Thanks, Guenter
