From: Thomas Huth <thuth@redhat.com>
To: qemu-s390x@nongnu.org, jjherne@linux.ibm.com,
frankja@linux.ibm.com, Eric Farman <farman@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Cc: jrossi@linux.ibm.com, qemu-devel@nongnu.org
Subject: Re: [RESEND PATCH 1/1] pc-bios: Add support for List-Directed IPL from ECKD DASD
Date: Fri, 3 Mar 2023 13:38:37 +0100 [thread overview]
Message-ID: <9739da85-adf2-cf33-15c8-6107aaf6b814@redhat.com> (raw)
In-Reply-To: <20230221174548.1866861-2-jrossi@linux.ibm.com>
On 21/02/2023 18.45, jrossi@linux.ibm.com wrote:
> From: Jared Rossi <jrossi@linux.ibm.com>
>
> Check for a List Directed IPL Boot Record, which would supersede the CCW type
> entries. If the record is valid, proceed to use the new style pointers
> and perform LD-IPL. Each block pointer is interpreted as either an LD-IPL
> pointer or a legacy CCW pointer depending on the type of IPL initiated.
>
> In either case CCW- or LD-IPL is transparent to the user and will boot the same
> image regardless of which set of pointers is used. Because the interactive boot
> menu is only written with the old style pointers, the menu will be disabled for
> List Directed IPL from ECKD DASD.
>
> If the LD-IPL fails, retry the IPL using the CCW type pointers.
>
> If no LD-IPL boot record is found, simply perform CCW type IPL as usual.
>
> Signed-off-by: Jared Rossi <jrossi@linux.ibm.com>
>
> ---
> pc-bios/s390-ccw/bootmap.c | 157 ++++++++++++++++++++++++++++---------
> pc-bios/s390-ccw/bootmap.h | 30 ++++++-
> 2 files changed, 148 insertions(+), 39 deletions(-)
Janosch, Jason, Eric, Christian,
could you please help with reviewing + testing this patch?
Thanks,
Thomas
next prev parent reply other threads:[~2023-03-03 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 17:45 [RESEND PATCH 0/1] pc-bios: Support List-Directed IPL from ECKD DASD jrossi
2023-02-21 17:45 ` [RESEND PATCH 1/1] pc-bios: Add support for " jrossi
2023-03-03 12:38 ` Thomas Huth [this message]
2023-03-07 17:09 ` Eric Farman
2023-03-03 16:29 ` Thomas Huth
2023-03-06 12:12 ` Thomas Huth
2023-03-06 15:39 ` 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=9739da85-adf2-cf33-15c8-6107aaf6b814@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=farman@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=jjherne@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).