From: linux@roeck-us.net (Guenter Roeck)
To: linux-riscv@lists.infradead.org
Subject: Building Risc-V Linux kernel images for qemu without rebuilding bbl
Date: Tue, 27 Feb 2018 14:55:49 -0800 [thread overview]
Message-ID: <20180227225549.GA20986@roeck-us.net> (raw)
Hi folks,
I have been trying to set up Risc-V qemu test builds on kerneltests.org.
Major hold-up at this point is the need to continuously rebuild bbl images
with embedded kernel images. Due to various reasons, this is all but
impossible with my auto-build system.
Is there a means to load bbl and vmlinux images separately into qemu,
or maybe a tool to attach the kernel to a pre-built bbl image ?
Of course, it would be even better if it was possible to just specify
"-kernel vmlinux" or something similar on the kernel command line.
Thanks,
Guenter
next reply other threads:[~2018-02-27 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 22:55 Guenter Roeck [this message]
2018-02-27 23:12 ` Building Risc-V Linux kernel images for qemu without rebuilding bbl Stef O'Rear
2018-02-27 23:38 ` Guenter Roeck
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=20180227225549.GA20986@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-riscv@lists.infradead.org \
/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).