From: Thomas Huth <thuth@redhat.com>
To: jrossi@linux.ibm.com, qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: frankja@linux.ibm.com, nsg@linux.ibm.com
Subject: Re: [PATCH 0/5] s390x: Add Full Boot Order Support
Date: Tue, 4 Jun 2024 20:35:02 +0200 [thread overview]
Message-ID: <7a6160da-e3fb-42a8-9173-55d3b2c7903d@redhat.com> (raw)
In-Reply-To: <20240529154311.734548-1-jrossi@linux.ibm.com>
On 29/05/2024 17.43, jrossi@linux.ibm.com wrote:
> From: Jared Rossi <jrossi@linux.ibm.com>
>
> This patch set primarily adds support for the specification of multiple boot
> devices, allowing for the guest to automatically use an alternative device on
> a failed boot without needing to be reconfigured. It additionally provides the
> ability to define the loadparm attribute on a per-device bases, which allows
> boot devices to use different loadparm values if needed.
>
> In brief, an IPLB is generated for each designated boot device (up to a maximum
> of 8) and stored in guest memory immediately before BIOS. If a device fails to
> boot, the next IPLB is retrieved and we jump back to the start of BIOS.
>
> Devices can be specified using the standard qemu device tag "bootindex" as with
> other architectures. Lower number indices are tried first, with "bootindex=0"
> indicating the first device to try.
>
> A subsequent Libvirt patch will be necessary to allow assignment of per-device
> loadparms in the guest XML
>
> Jared Rossi (5):
> Create include files for s390x IPL definitions
> Add loadparm to CcwDevice
> Build IPLB chain for multiple boot devices
> Add boot device fallback infrastructure
> Enable and document boot device fallback on panic
>
> docs/system/bootindex.rst | 7 +-
> docs/system/s390x/bootdevices.rst | 9 +-
> hw/s390x/ccw-device.h | 2 +
> hw/s390x/ipl.h | 117 +-------------------
> include/hw/s390x/ipl/qipl.h | 128 ++++++++++++++++++++++
> pc-bios/s390-ccw/bootmap.h | 5 +
> pc-bios/s390-ccw/iplb.h | 108 +++++--------------
> pc-bios/s390-ccw/s390-ccw.h | 6 ++
> hw/s390x/ccw-device.c | 49 +++++++++
> hw/s390x/ipl.c | 170 ++++++++++++++++++++++--------
> hw/s390x/s390-virtio-ccw.c | 18 +---
> hw/s390x/sclp.c | 3 +-
> pc-bios/s390-ccw/bootmap.c | 41 ++++---
> pc-bios/s390-ccw/main.c | 25 +++--
> pc-bios/s390-ccw/netmain.c | 4 +
> pc-bios/s390-ccw/Makefile | 2 +-
Hi Jared!
For v2, could you please add at least two tests: one that check booting from
the second disk and one that checks booting from the last boot disk when the
previous ones are invalid?
I could think of two easy ways for adding such tests, up to you what you prefer:
- Extend the tests/qtest/cdrom-test.c - see add_s390x_tests() there
- Add an avocado test - see "grep -l s390 tests/avocado/*.py" for examples.
Thomas
next prev parent reply other threads:[~2024-06-04 18:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 15:43 [PATCH 0/5] s390x: Add Full Boot Order Support jrossi
2024-05-29 15:43 ` [PATCH 1/5] s390x: Create include files for s390x IPL definitions jrossi
2024-06-03 18:51 ` Thomas Huth
2024-05-29 15:43 ` [PATCH 2/5] s390x: Add loadparm to CcwDevice jrossi
2024-06-04 14:27 ` Thomas Huth
2024-06-04 16:27 ` Jared Rossi
2024-06-04 16:59 ` Thomas Huth
2024-06-05 7:49 ` Thomas Huth
2024-05-29 15:43 ` [PATCH 3/5] s390x: Build IPLB chain for multiple boot devices jrossi
2024-06-03 19:03 ` Thomas Huth
2024-06-04 18:26 ` Thomas Huth
2024-06-05 20:01 ` Jared Rossi
2024-06-07 6:11 ` Thomas Huth
2024-05-29 15:43 ` [PATCH 4/5] s390x: Add boot device fallback infrastructure jrossi
2024-06-05 8:20 ` Thomas Huth
2024-06-05 12:13 ` Thomas Huth
2024-05-29 15:43 ` [PATCH 5/5] s390x: Enable and document boot device fallback on panic jrossi
2024-06-05 13:37 ` Thomas Huth
2024-06-05 14:48 ` Jared Rossi
2024-06-07 5:57 ` Thomas Huth
2024-06-16 23:44 ` Jared Rossi
2024-06-20 8:10 ` Thomas Huth
2024-06-17 14:49 ` Christian Borntraeger
2024-06-20 8:14 ` Thomas Huth
2024-06-04 18:35 ` Thomas Huth [this message]
2024-06-05 8:02 ` [PATCH 0/5] s390x: Add Full Boot Order Support Thomas Huth
2024-06-06 19:22 ` Jared Rossi
2024-06-07 6:19 ` Thomas Huth
2024-06-10 3:58 ` Jared Rossi
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=7a6160da-e3fb-42a8-9173-55d3b2c7903d@redhat.com \
--to=thuth@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=jrossi@linux.ibm.com \
--cc=nsg@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.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).