From: Thomas Huth <thuth@redhat.com>
To: jrossi@linux.ibm.com, qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: frankja@linux.ibm.com
Subject: Re: [PATCH 12/18] pc-bios/s390-ccw: Enable failed IPL to return after error
Date: Mon, 30 Sep 2024 12:11:56 +0200 [thread overview]
Message-ID: <e935ee2e-6e6e-44fa-a580-e0ac848d7686@redhat.com> (raw)
In-Reply-To: <20240927005117.1679506-13-jrossi@linux.ibm.com>
On 27/09/2024 02.51, jrossi@linux.ibm.com wrote:
> From: Jared Rossi <jrossi@linux.ibm.com>
>
> Remove panic-on-error from IPL functions such that a return code is propagated
> back to the main IPL calling function (rather than terminating immediately),
> which facilitates possible error recovery in the future.
>
> A select few panics remain, which indicate fatal non-devices errors that must
> result in termination.
>
> Signed-off-by: Jared Rossi <jrossi@linux.ibm.com>
>
> ---
...
> @@ -1054,16 +1073,19 @@ void zipl_load(void)
>
> if (vdev->is_cdrom) {
> ipl_iso_el_torito();
> - panic("\n! Cannot IPL this ISO image !\n");
> + puts("Failed to IPL this ISO image!");
> + return;
> }
>
> if (virtio_get_device_type() == VIRTIO_ID_NET) {
> netmain();
> - panic("\n! Cannot IPL from this network !\n");
> + puts("Failed to IPL from this network!");
> + return;
> }
>
> if (ipl_scsi()) {
> - panic("\n! Cannot IPL this device !\n");
> + puts("Failed to IPL from this device!");
I'd maybe say "Failed to IPL from this SCSI device" now, just to make sure
that it is easier to match the message with one of the boot device types later?
> + return;
> }
...
> void jump_to_low_kernel(void)
> diff --git a/pc-bios/s390-ccw/main.c b/pc-bios/s390-ccw/main.c
> index 2345432abb..f818bd7210 100644
> --- a/pc-bios/s390-ccw/main.c
> +++ b/pc-bios/s390-ccw/main.c
> @@ -77,6 +77,9 @@ static int is_dev_possibly_bootable(int dev_no, int sch_no)
>
> enable_subchannel(blk_schid);
> cutype = cu_type(blk_schid);
> + if (cutype == CU_TYPE_UNKNOWN) {
> + return -EIO;
> + }
>
> /*
> * Note: we always have to run virtio_is_supported() here to make
> @@ -194,10 +197,10 @@ static void boot_setup(void)
> have_iplb = store_iplb(&iplb);
> }
>
> -static void find_boot_device(void)
> +static bool find_boot_device(void)
> {
> VDev *vdev = virtio_get_device();
> - bool found;
> + bool found = false;
>
> switch (iplb.pbt) {
> case S390_IPL_TYPE_CCW:
> @@ -215,10 +218,10 @@ static void find_boot_device(void)
> found = find_subch(iplb.scsi.devno);
> break;
> default:
> - panic("List-directed IPL not supported yet!\n");
> + puts("Invalid IPLB");
Maybe rather say "Unsupported IPLB" ? At least the original message sounds
like it was rather something that has not been implemented yet, and not
something that is wrong on the disk...?
> }
>
> - IPL_assert(found, "Boot device not found\n");
> + return found;
> }
...
> unsigned long virtio_load_direct(unsigned long rec_list1, unsigned long rec_list2,
> @@ -73,13 +73,13 @@ unsigned long virtio_load_direct(unsigned long rec_list1, unsigned long rec_list
> unsigned long addr = (unsigned long)load_addr;
>
> if (sec_len != virtio_get_block_size()) {
> - return -1;
> + return 0;
> }
>
> printf(".");
> status = virtio_read_many(sec, (void *)addr, sec_num);
> if (status) {
> - panic("I/O Error");
> + return 0;
> }
> addr += sec_num * virtio_get_block_size();
Ah, here's the fix for virtio_load_direct() ... since you changed the call
site in patch 09 already, I think you should move this hunk to patch 09, too.
> diff --git a/pc-bios/s390-ccw/virtio.c b/pc-bios/s390-ccw/virtio.c
> index 8c6b0a8a92..e3fdb95b3c 100644
> --- a/pc-bios/s390-ccw/virtio.c
> +++ b/pc-bios/s390-ccw/virtio.c
> @@ -217,16 +217,19 @@ int virtio_run(VDev *vdev, int vqid, VirtioCmd *cmd)
> return 0;
> }
>
> -void virtio_setup_ccw(VDev *vdev)
> +int virtio_setup_ccw(VDev *vdev)
> {
> - int i, rc, cfg_size = 0;
> + int i, cfg_size = 0;
> uint8_t status;
> struct VirtioFeatureDesc {
> uint32_t features;
> uint8_t index;
> } __attribute__((packed)) feats;
>
> - IPL_assert(virtio_is_supported(vdev->schid), "PE");
> + if (!virtio_is_supported(vdev->schid)) {
> + puts("PE");
Do you remember what "PE" means here? ... might be a good opportunity to fix
this error message as well...
> + return -ENODEV;
> + }
Thomas
next prev parent reply other threads:[~2024-09-30 10:13 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 0:50 [PATCH V2 0/18] s390x: Add Full Boot Order Support jrossi
2024-09-27 0:51 ` [PATCH 01/18] hw/s390x/ipl: Provide more memory to the s390-ccw.img firmware jrossi
2024-09-27 0:51 ` [PATCH 02/18] pc-bios/s390-ccw: Use the libc from SLOF and remove sclp prints jrossi
2024-09-27 0:51 ` [PATCH 03/18] pc-bios/s390-ccw: Link the netboot code into the main s390-ccw.img binary jrossi
2024-09-27 0:51 ` [PATCH 04/18] hw/s390x: Remove the possibility to load the s390-netboot.img binary jrossi
2024-09-27 0:51 ` [PATCH 05/18] pc-bios/s390-ccw: Merge netboot.mak into the main Makefile jrossi
2024-09-27 0:51 ` [PATCH 06/18] docs/system/s390x/bootdevices: Update the documentation about network booting jrossi
2024-09-27 0:51 ` [PATCH 07/18] pc-bios/s390-ccw: Remove panics from ISO IPL path jrossi
2024-09-27 15:02 ` Thomas Huth
2024-09-27 17:15 ` Jared Rossi
2024-09-30 6:11 ` Thomas Huth
2024-09-30 13:10 ` Jared Rossi
2024-09-27 0:51 ` [PATCH 08/18] pc-bios/s390-ccw: Remove panics from ECKD " jrossi
2024-09-27 15:29 ` Thomas Huth
2024-09-27 17:25 ` Jared Rossi
2024-09-27 0:51 ` [PATCH 09/18] pc-bios/s390-ccw: Remove panics from SCSI " jrossi
2024-09-30 7:48 ` Thomas Huth
2024-09-30 10:13 ` Thomas Huth
2024-09-27 0:51 ` [PATCH 10/18] pc-bios/s390-ccw: Remove panics from DASD " jrossi
2024-09-30 8:14 ` Thomas Huth
2024-09-27 0:51 ` [PATCH 11/18] pc-bios/s390-ccw: Remove panics from Netboot " jrossi
2024-09-30 9:39 ` Thomas Huth
2024-09-30 13:15 ` Jared Rossi
2024-09-27 0:51 ` [PATCH 12/18] pc-bios/s390-ccw: Enable failed IPL to return after error jrossi
2024-09-30 10:11 ` Thomas Huth [this message]
2024-09-30 13:29 ` Jared Rossi
2024-09-27 0:51 ` [PATCH 13/18] include/hw/s390x: Add include files for common IPL structs jrossi
2024-09-30 10:42 ` Thomas Huth
2024-09-30 13:31 ` Jared Rossi
2024-09-27 0:51 ` [PATCH 14/18] s390x: Add individual loadparm assignment to CCW device jrossi
2024-09-30 11:25 ` Thomas Huth
2024-09-27 0:51 ` [PATCH 15/18] hw/s390x: Build an IPLB for each boot device jrossi
2024-09-30 11:59 ` Thomas Huth
2024-09-30 13:39 ` Jared Rossi
2024-09-27 0:51 ` [PATCH 16/18] s390x: Rebuild IPLB for SCSI device directly from DIAG308 jrossi
2024-09-30 12:15 ` Thomas Huth
2024-09-30 13:46 ` Jared Rossi
2024-09-27 0:51 ` [PATCH 17/18] pc-bios/s390x: Enable multi-device boot loop jrossi
2024-09-30 12:32 ` Thomas Huth
2024-09-30 13:48 ` Jared Rossi
2024-09-30 13:08 ` Thomas Huth
2024-09-30 13:52 ` Jared Rossi
2024-09-27 0:51 ` [PATCH 18/18] docs/system: Update documentation for s390x IPL jrossi
2024-09-30 12:34 ` Thomas Huth
2024-09-30 13:14 ` [PATCH V2 0/18] s390x: Add Full Boot Order Support Thomas Huth
2024-09-30 14:20 ` 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=e935ee2e-6e6e-44fa-a580-e0ac848d7686@redhat.com \
--to=thuth@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=jrossi@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).