From: Alexander Graf <agraf@suse.de>
To: Laszlo Ersek <lersek@redhat.com>,
peter.maydell@linaro.org, qemu-devel@nongnu.org,
rjones@redhat.com, drjones@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 7/8] hw/arm: pass pristine kernel image to guest firmware over fw_cfg
Date: Tue, 16 Dec 2014 13:15:28 +0100 [thread overview]
Message-ID: <54902260.2060105@suse.de> (raw)
In-Reply-To: <1418399932-7658-8-git-send-email-lersek@redhat.com>
On 12.12.14 16:58, Laszlo Ersek wrote:
> Introduce the new boolean field "arm_boot_info.firmware_loaded". When this
> field is set, it means that the portion of guest DRAM that the VCPU
> normally starts to execute, or the pflash chip that the VCPU normally
> starts to execute, has been populated by board-specific code with
> full-fledged guest firmware code, before the board calls
> arm_load_kernel().
>
> Simultaneously, "arm_boot_info.firmware_loaded" guarantees that the board
> code has set up the global firmware config instance, for arm_load_kernel()
> to find with fw_cfg_find().
>
> Guest kernel (-kernel) and guest firmware (-bios, -pflash) has always been
> possible to specify independently on the command line. The following cases
> should be considered:
>
> nr -bios -pflash -kernel description
> unit#0
> -- ------- ------- ------- -------------------------------------------
> 1 present present absent Board code rejects this case, -bios and
> present present present -pflash unit#0 are exclusive. Left intact
> by this patch.
>
> 2 absent absent present Traditional kernel loading, with qemu's
> minimal board firmware. Left intact by this
> patch.
>
> 3 absent present absent Preexistent case for booting guest firmware
> present absent absent loaded with -bios or -pflash. Left intact
> by this patch.
>
> 4 absent absent absent Preexistent case for not loading any
> firmware or kernel up-front. Left intact by
> this patch.
>
> 5 present absent present New case introduced by this patch: kernel
> absent present present image is passed to externally loaded
> firmware in unmodified form, using fw_cfg.
>
> An easy way to see that this patch doesn't interfere with existing cases
> is to realize that "info->firmware_loaded" is constant zero at this point.
> Which makes the "outer" condition unchanged, and the "inner" condition
> (with the fw_cfg-related code) dead.
>
> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
> ---
>
> Notes:
> v4:
> - drop space "between function name and open parenthesis '('" [Peter]
>
> v3:
> - unchanged
>
> include/hw/arm/arm.h | 5 +++
> hw/arm/boot.c | 91 +++++++++++++++++++++++++++++++++++++++++++++++++---
> 2 files changed, 91 insertions(+), 5 deletions(-)
>
> diff --git a/include/hw/arm/arm.h b/include/hw/arm/arm.h
> index cefc9e6..dd69d66 100644
> --- a/include/hw/arm/arm.h
> +++ b/include/hw/arm/arm.h
> @@ -65,8 +65,13 @@ struct arm_boot_info {
> int is_linux;
> hwaddr initrd_start;
> hwaddr initrd_size;
> hwaddr entry;
> +
> + /* Boot firmware has been loaded, typically at address 0, with -bios or
> + * -pflash. It also implies that fw_cfg_find() will succeed.
> + */
> + bool firmware_loaded;
> };
> void arm_load_kernel(ARMCPU *cpu, struct arm_boot_info *info);
>
> /* Multiplication factor to convert from system clock ticks to qemu timer
> diff --git a/hw/arm/boot.c b/hw/arm/boot.c
> index e6a3c5b..5c65d16 100644
> --- a/hw/arm/boot.c
> +++ b/hw/arm/boot.c
> @@ -477,8 +477,62 @@ static void do_cpu_reset(void *opaque)
> }
> }
> }
>
> +/**
> + * load_image_to_fw_cfg() - Load an image file into an fw_cfg entry identified
> + * by key.
> + * @fw_cfg: The firmware config instance to store the data in.
> + * @size_key: The firmware config key to store the size of the loaded data
> + * under, with fw_cfg_add_i32().
> + * @data_key: The firmware config key to store the loaded data under, with
> + * fw_cfg_add_bytes().
> + * @image_name: The name of the image file to load. If it is NULL, the function
> + * returns without doing anything.
> + * @decompress: Whether the image should be decompressed (gunzipped) before
> + * adding it to fw_cfg.
> + *
> + * In case of failure, the function prints an error message to stderr and the
> + * process exits with status 1.
> + */
> +static void load_image_to_fw_cfg(FWCfgState *fw_cfg, uint16_t size_key,
> + uint16_t data_key, const char *image_name,
> + bool decompress)
> +{
> + size_t size;
> + uint8_t *data;
> +
> + if (image_name == NULL) {
> + return;
> + }
> +
> + if (decompress) {
> + int bytes;
> +
> + bytes = load_image_gzipped_buffer(image_name,
> + LOAD_IMAGE_MAX_GUNZIP_BYTES, &data);
> + if (bytes == -1) {
> + fprintf(stderr, "failed to load and decompress \"%s\"\n",
> + image_name);
> + exit(1);
> + }
> + size = bytes;
> + } else {
> + gchar *contents;
> + gsize length;
> +
> + if (!g_file_get_contents(image_name, &contents, &length, NULL)) {
> + fprintf(stderr, "failed to load \"%s\"\n", image_name);
> + exit(1);
> + }
> + size = length;
> + data = (uint8_t *)contents;
> + }
> +
> + fw_cfg_add_i32(fw_cfg, size_key, size);
> + fw_cfg_add_bytes(fw_cfg, data_key, data, size);
> +}
> +
> void arm_load_kernel(ARMCPU *cpu, struct arm_boot_info *info)
> {
> CPUState *cs;
> int kernel_size;
> @@ -499,21 +553,48 @@ void arm_load_kernel(ARMCPU *cpu, struct arm_boot_info *info)
> qemu_register_reset(do_cpu_reset, ARM_CPU(cs));
> }
>
> /* Load the kernel. */
> - if (!info->kernel_filename) {
> + if (!info->kernel_filename || info->firmware_loaded) {
>
> if (have_dtb(info)) {
> - /* If we have a device tree blob, but no kernel to supply it to,
> - * copy it to the base of RAM for a bootloader to pick up.
> + /* If we have a device tree blob, but no kernel to supply it to (or
> + * the kernel is supposed to be loaded by the bootloader), copy the
> + * DTB to the base of RAM for the bootloader to pick up.
> */
> if (load_dtb(info->loader_start, info, 0) < 0) {
> exit(1);
> }
> }
>
> - /* If no kernel specified, do nothing; we will start from address 0
> - * (typically a boot ROM image) in the same way as hardware.
> + if (info->kernel_filename) {
> + FWCfgState *fw_cfg;
> + bool decompress_kernel;
> +
> + fw_cfg = fw_cfg_find();
> + decompress_kernel = arm_feature(&cpu->env, ARM_FEATURE_AARCH64);
I don't understand this. On AArch64 I can simply do -kernel Image and it
boots without decompressing anything, no?
Alex
next prev parent reply other threads:[~2014-12-16 12:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 15:58 [Qemu-devel] [PATCH v4 0/8] fw_cfg, bootorder, and UEFI+'-kernel' on arm/virt Laszlo Ersek
2014-12-12 15:58 ` [Qemu-devel] [PATCH v4 1/8] fw_cfg: max access size and region size are the same for MMIO data reg Laszlo Ersek
2014-12-16 13:48 ` Andrew Jones
2014-12-16 19:00 ` Laszlo Ersek
2014-12-16 19:49 ` Paolo Bonzini
2014-12-16 20:06 ` Laszlo Ersek
2014-12-16 20:17 ` Laszlo Ersek
2014-12-16 21:47 ` Paolo Bonzini
2014-12-17 4:52 ` Laszlo Ersek
2014-12-16 20:40 ` Paolo Bonzini
2014-12-16 21:47 ` Peter Maydell
2014-12-17 5:06 ` Laszlo Ersek
2014-12-17 9:23 ` Paolo Bonzini
2014-12-17 9:31 ` Alexander Graf
2014-12-16 20:41 ` Peter Maydell
2014-12-17 7:13 ` Laszlo Ersek
2014-12-17 8:28 ` Alexander Graf
2014-12-17 8:40 ` Laszlo Ersek
2014-12-12 15:58 ` [Qemu-devel] [PATCH v4 2/8] fw_cfg: generalize overlap check for combining control and data I/O ports Laszlo Ersek
2014-12-12 15:58 ` [Qemu-devel] [PATCH v4 3/8] fw_cfg: introduce the "data_memwidth" property Laszlo Ersek
2014-12-16 12:06 ` Alexander Graf
2014-12-16 12:42 ` Laszlo Ersek
2014-12-16 16:59 ` Laszlo Ersek
2014-12-16 17:10 ` Peter Maydell
2014-12-16 17:20 ` Alexander Graf
2014-12-16 18:52 ` Laszlo Ersek
2014-12-12 15:58 ` [Qemu-devel] [PATCH v4 4/8] fw_cfg: expose the "data_memwidth" prop with fw_cfg_init_data_memwidth() Laszlo Ersek
2014-12-12 15:58 ` [Qemu-devel] [PATCH v4 5/8] arm: add fw_cfg to "virt" board Laszlo Ersek
2014-12-12 15:58 ` [Qemu-devel] [PATCH v4 6/8] hw/loader: split out load_image_gzipped_buffer() Laszlo Ersek
2014-12-12 15:58 ` [Qemu-devel] [PATCH v4 7/8] hw/arm: pass pristine kernel image to guest firmware over fw_cfg Laszlo Ersek
2014-12-16 12:15 ` Alexander Graf [this message]
2014-12-16 12:18 ` Peter Maydell
2014-12-16 12:20 ` Alexander Graf
2014-12-16 12:25 ` Peter Maydell
2014-12-16 12:42 ` Richard W.M. Jones
2014-12-16 12:44 ` Laszlo Ersek
2014-12-12 15:58 ` [Qemu-devel] [PATCH v4 8/8] hw/arm/virt: enable passing of EFI-stubbed kernel to guest UEFI firmware Laszlo Ersek
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=54902260.2060105@suse.de \
--to=agraf@suse.de \
--cc=drjones@redhat.com \
--cc=lersek@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@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.