qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: julien@xen.org, masami.hiramatsu@linaro.org,
	andre.przywara@arm.com, stefano.stabellini@linaro.org,
	takahiro.akashi@linaro.org, stefano.stabellini@xilinx.com,
	"Alex Bennée" <alex.bennee@linaro.org>,
	stratos-dev@op-lists.linaro.org
Subject: [PATCH  v1 0/4] add guest-loader (for direct Xen boot)
Date: Wed, 21 Oct 2020 18:08:38 +0100	[thread overview]
Message-ID: <20201021170842.25762-1-alex.bennee@linaro.org> (raw)

Hi,

This is a refinement of the Xen loader I posted a few weeks ago.
Rather than complicate the generic loader with extra options I went
for the more expedient approach of adding a completely new device
called the guest-loader. As it didn't need to deal with any of the
subtleties of the generic-loader it also worked out somewhat simpler.

Instead of allowing the user to hand hack FDT blobs we simply add
syntactic sugar that understands the difference between a kernel and
initrd. This could be expanded in future if we want although at the
moment I don't know what else you would add.

The new syntax is now simpler:

  -device guest-loader,addr=0x42000000,kernel=Image,bootargs="console=hvc0 earlyprintk=xen" \
  -device guest-loader,addr=0x47000000,initrd=rootfs.cpio

So any objections? It would be nice to get in this cycle but we only
have a week left until soft-freeze.

Alex Bennée (4):
  hw/board: promote fdt from ARM VirtMachineState to MachineState
  hw/riscv: migrate fdt field to generic MachineState
  device_tree: add qemu_fdt_setprop_string_array helper
  hw/core: implement a guest-loader to support static hypervisor guests

 hw/core/guest-loader.h       |  34 ++++
 include/hw/arm/virt.h        |   1 -
 include/hw/boards.h          |   1 +
 include/hw/riscv/virt.h      |   1 -
 include/sysemu/device_tree.h |  17 ++
 hw/arm/virt.c                | 322 ++++++++++++++++++-----------------
 hw/core/guest-loader.c       | 140 +++++++++++++++
 hw/riscv/virt.c              |  18 +-
 softmmu/device_tree.c        |  26 +++
 hw/core/meson.build          |   2 +
 10 files changed, 398 insertions(+), 164 deletions(-)
 create mode 100644 hw/core/guest-loader.h
 create mode 100644 hw/core/guest-loader.c

-- 
2.20.1



             reply	other threads:[~2020-10-21 17:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21 17:08 Alex Bennée [this message]
2020-10-21 17:08 ` [PATCH v1 1/4] hw/board: promote fdt from ARM VirtMachineState to MachineState Alex Bennée
2020-10-21 17:08 ` [PATCH v1 2/4] hw/riscv: migrate fdt field to generic MachineState Alex Bennée
2020-10-23 15:35   ` Alistair Francis
2020-10-21 17:08 ` [PATCH v1 3/4] device_tree: add qemu_fdt_setprop_string_array helper Alex Bennée
2020-10-24  0:28   ` Alistair Francis
2020-10-21 17:08 ` [PATCH v1 4/4] hw/core: implement a guest-loader to support static hypervisor guests Alex Bennée
2020-10-24  0:35   ` Alistair Francis
2020-10-21 17:18 ` [PATCH v1 0/4] add guest-loader (for direct Xen boot) no-reply

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=20201021170842.25762-1-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=andre.przywara@arm.com \
    --cc=julien@xen.org \
    --cc=masami.hiramatsu@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@linaro.org \
    --cc=stefano.stabellini@xilinx.com \
    --cc=stratos-dev@op-lists.linaro.org \
    --cc=takahiro.akashi@linaro.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).