From: Andrea Bolognani <abologna@redhat.com>
To: Michael Clark <mjc@sifive.com>, Peter Maydell <peter.maydell@linaro.org>
Cc: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
Palmer Dabbelt <palmer@sifive.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
RISC-V Patches <patches@groups.riscv.org>
Subject: Re: [Qemu-devel] [PULL] RISC-V QEMU Port Submission v8
Date: Tue, 06 Mar 2018 10:13:43 +0100 [thread overview]
Message-ID: <1520327623.4132.10.camel@redhat.com> (raw)
In-Reply-To: <CAHNT7Nv-Whr=fdgXANnSuw1yxb6EEBzdxVFSfkLZhh6knzS3sA@mail.gmail.com>
On Tue, 2018-03-06 at 14:30 +1300, Michael Clark wrote:
> I'm currently working on some changes locally to split the firmware from
> the kernel image. Currently the kernel image is embedded in the firmware (r
> iscv-pk/bbl).
I was wondering about this just yesterday.
Will this eventually lead to a situation where we can have a single
firmware image which is shared between all guests, a la OVMF/AAVMF,
with grub and the kernels stored on the virtual disk itself, like
on most other architectures?
That should make it less awkward to add RISC-V support to libvirt,
plus I expect it to be kind of a requirement for full distribution
support, especially when it comes to updates and such.
--
Andrea Bolognani / Red Hat / Virtualization
next prev parent reply other threads:[~2018-03-06 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 13:55 [Qemu-devel] [PULL] RISC-V QEMU Port Submission v8 Michael Clark
2018-03-02 14:22 ` Peter Maydell
2018-03-03 2:46 ` Michael Clark
2018-03-03 22:52 ` Peter Maydell
2018-03-05 23:10 ` Michael Clark
2018-03-06 1:30 ` Michael Clark
2018-03-06 9:13 ` Andrea Bolognani [this message]
2018-03-07 3:40 ` Michael Clark
2018-03-06 11:09 ` Peter Maydell
2018-03-07 3:49 ` Michael Clark
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=1520327623.4132.10.camel@redhat.com \
--to=abologna@redhat.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=mjc@sifive.com \
--cc=palmer@sifive.com \
--cc=patches@groups.riscv.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
/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).