From: Laszlo Ersek <lersek@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Wei Huang <wei@redhat.com>, Drew Jones <drjones@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
qemu devel list <qemu-devel@nongnu.org>"Richard W.M. Jones"
<rjones@redhat.com>, Cole Robinson <crobinso@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/3] hw/arm/virt: boot with -kernel -initrd -append on top of UEFI
Date: Tue, 09 Dec 2014 01:07:20 +0100 [thread overview]
Message-ID: <54863D38.2070906@redhat.com> (raw)
In-Reply-To: <CAFEAcA-BOrLWmZWu2E227f9eJ87495TGF0c+c1TeiR_10KUPdg@mail.gmail.com>
On 12/05/14 19:55, Peter Maydell wrote:
> On 5 December 2014 at 18:36, Laszlo Ersek <lersek@redhat.com> wrote:
>> A number of tools depend on passing the kernel image, the initial
>> ramdisk, and the kernel command line to the guest on the QEMU command
>> line (options -kernel, -initrd, -append, respectively). At the moment,
>> these QEMU options work, but the guest kernel loaded this way is
>> launched by a minimal binary firmware that is dynamically composed by
>> QEMU. As a consequence, such a kernel has no UEFI environment.
>>
>> In this patchset the kernel, initrd and cmdline blobs are passed to the
>> guest firmware to process & load. This mode is activated when both
>> -kernel and -pflash unit#0 (or -bios) are specified.
>
> ...so we avoid back-compat problems on the assumption that
> nobody was previously trying to provide both -bios and
> -kernel at once. I *think* that's probably a reasonable
> assumption...
I'm including these three too in the new patchset that I'll post soon,
so no need to keep these queued.
Thanks
Laszlo
prev parent reply other threads:[~2014-12-09 0:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 18:36 [Qemu-devel] [PATCH 0/3] hw/arm/virt: boot with -kernel -initrd -append on top of UEFI Laszlo Ersek
2014-12-05 18:36 ` [Qemu-devel] [PATCH 1/3] hw/loader: split out load_image_gzipped_buffer() Laszlo Ersek
2014-12-05 18:36 ` [Qemu-devel] [PATCH 2/3] hw/arm: pass pristine kernel image to guest firmware over fw_cfg Laszlo Ersek
2014-12-05 18:36 ` [Qemu-devel] [PATCH 3/3] hw/arm/virt: enable passing of EFI-stubbed kernel to guest UEFI firmware Laszlo Ersek
2014-12-05 18:55 ` [Qemu-devel] [PATCH 0/3] hw/arm/virt: boot with -kernel -initrd -append on top of UEFI Peter Maydell
2014-12-09 0:07 ` Laszlo Ersek [this message]
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=54863D38.2070906@redhat.com \
--to=lersek@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=drjones@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=wei@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.