From: Eric Farman <farman@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
qemu-s390x@nongnu.org, jjherne@linux.ibm.com,
frankja@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: Tue, 07 Mar 2023 12:09:31 -0500 [thread overview]
Message-ID: <04f940dd7f0e5540fb1cb0d1fb8be1c95f797695.camel@linux.ibm.com> (raw)
In-Reply-To: <9739da85-adf2-cf33-15c8-6107aaf6b814@redhat.com>
On Fri, 2023-03-03 at 13:38 +0100, Thomas Huth wrote:
> 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 for the heads up, Thomas.
I've been using this on a z16 system with SE guests (with newer zipl to
actually write out LD-IPL data; something that should have been
mentioned here), and it seems to behave fine. I gave a quick glance
through the code, and while nothing jumped out at me this code is
rather opaque. I realize this is already queued by now but I'll still
go through it later this week so it gets another set of eyeballs.
Eric
next prev parent reply other threads:[~2023-03-07 17:10 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
2023-03-07 17:09 ` Eric Farman [this message]
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=04f940dd7f0e5540fb1cb0d1fb8be1c95f797695.camel@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=borntraeger@de.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 \
--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).