From: Jared Rossi <jrossi@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: frankja@linux.ibm.com
Subject: Re: [PATCH 15/18] hw/s390x: Build an IPLB for each boot device
Date: Mon, 30 Sep 2024 09:39:09 -0400 [thread overview]
Message-ID: <9b32531b-2f83-42fe-baf4-1dfb8e15e040@linux.ibm.com> (raw)
In-Reply-To: <b3674e3b-5a23-41a0-a100-7fb2810a2775@redhat.com>
On 9/30/24 7:59 AM, Thomas Huth wrote:
> On 27/09/2024 02.51, jrossi@linux.ibm.com wrote:
>> From: Jared Rossi <jrossi@linux.ibm.com>
>> ...
>> @@ -484,8 +499,8 @@ static bool s390_gen_initial_iplb(S390IPLState *ipl)
>> lp = S390_CCW_MACHINE(qdev_get_machine())->loadparm;
>> }
>> - s390_ipl_convert_loadparm((char *)lp, ipl->iplb.loadparm);
>> - ipl->iplb.flags |= DIAG308_FLAGS_LP_VALID;
>> + s390_ipl_convert_loadparm((char *)lp, iplb->loadparm);
>> + iplb->flags |= DIAG308_FLAGS_LP_VALID;
>> return true;
>> }
>> @@ -493,6 +508,58 @@ static bool s390_gen_initial_iplb(S390IPLState
>> *ipl)
>> return false;
>> }
>> +static bool s390_init_all_iplbs(S390IPLState *ipl)
>> +{
>> + int iplb_num = 0;
>> + IplParameterBlock iplb_chain[7];
>> + DeviceState *dev_st = get_boot_device(0);
>> +
>> + /*
>> + * Parse the boot devices. Generate an IPLB for the first boot
>> device,
>> + * which will later be set with DIAG308. Index any fallback boot
>> devices.
>> + */
>
> The comment looks like it rather belongs to the whole function, and
> not to the if-statement below? So maybe move it at the top?
Agreed.
>
>> + if (!dev_st) {
>> + ipl->qipl.chain_len = 0;
>> + return false;
>> + }
>> +
>> + iplb_num = 1;
>> + s390_build_iplb(dev_st, &ipl->iplb);
>> + ipl->iplb.flags |= DIAG308_FLAGS_LP_VALID;
>
> Isn't DIAG308_FLAGS_LP_VALID set within s390_build_iplb() already?
>
>> + while (get_boot_device(iplb_num)) {
>> + iplb_num++;
>> + }
>
> I'd maybe move the code block below to this spot here, so you've got
> to assign ipl->qipl.chain_len only once:
>
> + if (iplb_num > MAX_IPLB_CHAIN + 1) {
> + warn_report("Excess boot devices defined! %d boot devices
> found, "
> + "but only the first %d will be considered.",
> + iplb_num, MAX_IPLB_CHAIN + 1);
> +
> + iplb_num = MAX_IPLB_CHAIN + 1;
> + }
>
>> + ipl->qipl.chain_len = iplb_num - 1;
>> +
>> + /*
>> + * Build fallback IPLBs for any boot devices above index 0, up to a
>> + * maximum amount as defined in ipl.h
>> + */
>> + if (iplb_num > 1) {
>> + if (iplb_num > MAX_IPLB_CHAIN + 1) {
>> + warn_report("Excess boot devices defined! %d boot
>> devices found, "
>> + "but only the first %d will be considered.",
>> + iplb_num, MAX_IPLB_CHAIN + 1);
>> +
>> + ipl->qipl.chain_len = MAX_IPLB_CHAIN;
>> + iplb_num = MAX_IPLB_CHAIN + 1;
>> + }
>
> i.e. move this code block -^
> and remove the "ipl->qipl.chain_len = MAX_IPLB_CHAIN;" in there.
>
>> + /* Start at 1 because the IPLB for boot index 0 is not
>> chained */
>> + for (int i = 1; i < iplb_num; i++) {
>> + dev_st = get_boot_device(i);
>> + s390_build_iplb(dev_st, &iplb_chain[i - 1]);
>> + iplb_chain[i - 1].flags |= DIAG308_FLAGS_LP_VALID;
>
> Again, setting DIAG308_FLAGS_LP_VALID should not be necessary since it
> is already done in s390_build_iplb() ?
>
I’ll see if I can clean section this up and remove redundant flag
assignments.
Jared Rossi
next prev parent reply other threads:[~2024-09-30 13:40 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
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 [this message]
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=9b32531b-2f83-42fe-baf4-1dfb8e15e040@linux.ibm.com \
--to=jrossi@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@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 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).