qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jared Rossi <jrossi@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
	qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Cc: frankja@linux.ibm.com, jjherne@linux.ibm.com
Subject: Re: [PATCH 0/1] pc-bios: Support List-Directed IPL from ECKD DASD
Date: Mon, 20 Feb 2023 11:21:28 -0500	[thread overview]
Message-ID: <eba35cef-32d1-69cd-2fc5-638880e2ee63@linux.ibm.com> (raw)
In-Reply-To: <837e025f-2307-225d-2b87-5f58ccda183a@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2274 bytes --]

On 2/20/23 10:45 AM, Thomas Huth wrote:
> On 20/02/2023 16.13, Jared Rossi wrote:
>> Hi,
>>
>> Pinging this patch since v2.26.0 of s390-tools adds ECKD DASD 
>> list-directed IPL.
>> This patch set allows QEMU to utilize that new boot pointer format.
>> Any feedback about what needs to be changed for acceptance is much 
>> appreciated.
>
> Where did you send your patches to? I can't find it in neither my 
> qemu-s390x nor my qemu-devel mailing list folders.
>
>  Thomas

Hi Thomas,

I tried to send them toqemu-s390x@nongnu.org  andqemu-devel@nongnu.org  lists with some additional people (including you)
in CC.  The initial mail was on January 30th.  I can resend them if there was a problem with the delivery.

Regards,
Jared Rossi

>
>
>>
>> On 1/30/23 4:24 PM, Jared Rossi wrote:
>>
>>> Add support for List-Directed IPL (LD-IPL) type pointers.
>>>
>>> We check for a boot record indicating LD-IPL and use it if it is valid,
>>> otherwise we use the CCW CDL or LDL format as usual. When a block is 
>>> accessed
>>> during IPL the block number is first calculated based on the 
>>> cylinder, head,
>>> and record numbers included in the block pointer; if LD-IPL has been 
>>> initiated
>>> then each pointer will be interpreted using the new format.
>>>
>>> For simplicity, there is no choice presented to forcibly use CCW-IPL 
>>> if LD-IPL
>>> is available.  Because both sets of pointers ultimately go to the same
>>> kernel/initrd, using CCW- or LD-IPL is transparent to the user.
>>>
>>> One aspect of the user experience that does change is the 
>>> availability of the
>>> interactive boot menu when a loadparm is not specified.  For the 
>>> existing
>>> CCW-IPL, when the user does not specify a loadparm they are 
>>> presented with a
>>> list of boot options; however, this list is only written in the old 
>>> style
>>> pointers.  Therefore, if no loadparm is specified, and LD-IPL is 
>>> supported, the
>>> default boot option will be used automatically.
>>>
>>> Jared Rossi (1):
>>>    pc-bios: Add support for List-Directed IPL from ECKD DASD
>>>
>>>   pc-bios/s390-ccw/bootmap.c | 157 
>>> ++++++++++++++++++++++++++++---------
>>>   pc-bios/s390-ccw/bootmap.h |  30 ++++++-
>>>   2 files changed, 148 insertions(+), 39 deletions(-)
>>>
>

[-- Attachment #2: Type: text/html, Size: 3796 bytes --]

  reply	other threads:[~2023-02-20 16:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230130212411.1167822-1-jrossi@linux.ibm.com>
2023-02-20 15:13 ` [PATCH 0/1] pc-bios: Support List-Directed IPL from ECKD DASD Jared Rossi
2023-02-20 15:45   ` Thomas Huth
2023-02-20 16:21     ` Jared Rossi [this message]
2023-02-20 16:33       ` Thomas Huth

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=eba35cef-32d1-69cd-2fc5-638880e2ee63@linux.ibm.com \
    --to=jrossi@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=jjherne@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).