From: Cornelia Huck <cohuck@redhat.com>
To: "Jason J. Herne" <jjherne@linux.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org, thuth@redhat.com,
alifm@linux.ibm.com, borntraeger@de.ibm.com
Subject: Re: [Qemu-devel] [PATCH] s390-bios: Skip bootmap signature entries
Date: Mon, 29 Apr 2019 15:40:03 +0200 [thread overview]
Message-ID: <20190429154003.7f8fc423.cohuck@redhat.com> (raw)
In-Reply-To: <1556543381-12671-1-git-send-email-jjherne@linux.ibm.com>
On Mon, 29 Apr 2019 09:09:41 -0400
"Jason J. Herne" <jjherne@linux.ibm.com> wrote:
> Newer versions of zipl have the ability to write signature entries to the boot
> script for secure boot. We don't yet support secure boot, but we need to skip
> over signature entries while reading the boot script in order to maintain our
> ability to boot guest operating systems that have a secure bootloader.
>
> Signed-off-by: Jason J. Herne <jjherne@linux.ibm.com>
> Reviewed-by: Farhan Ali <alifm@linux.ibm.com>
> ---
> pc-bios/s390-ccw/bootmap.c | 19 +++++++++++++++++--
> pc-bios/s390-ccw/bootmap.h | 10 ++++++----
> 2 files changed, 23 insertions(+), 6 deletions(-)
Skipping something that we don't have support for yet, but that doesn't
hinder normal operation sounds reasonable; but can you point me to the
relevant commit implementing this in zipl or some documentation? I
haven't been able to find something like that in the s390-tools git
tree.
WARNING: multiple messages have this Message-ID (diff)
From: Cornelia Huck <cohuck@redhat.com>
To: "Jason J. Herne" <jjherne@linux.ibm.com>
Cc: thuth@redhat.com, borntraeger@de.ibm.com, qemu-s390x@nongnu.org,
alifm@linux.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] s390-bios: Skip bootmap signature entries
Date: Mon, 29 Apr 2019 15:40:03 +0200 [thread overview]
Message-ID: <20190429154003.7f8fc423.cohuck@redhat.com> (raw)
Message-ID: <20190429134003.bx_A53cZG1dTpebMQP_yWWpTYxNU8C0MXcIuniLY4bc@z> (raw)
In-Reply-To: <1556543381-12671-1-git-send-email-jjherne@linux.ibm.com>
On Mon, 29 Apr 2019 09:09:41 -0400
"Jason J. Herne" <jjherne@linux.ibm.com> wrote:
> Newer versions of zipl have the ability to write signature entries to the boot
> script for secure boot. We don't yet support secure boot, but we need to skip
> over signature entries while reading the boot script in order to maintain our
> ability to boot guest operating systems that have a secure bootloader.
>
> Signed-off-by: Jason J. Herne <jjherne@linux.ibm.com>
> Reviewed-by: Farhan Ali <alifm@linux.ibm.com>
> ---
> pc-bios/s390-ccw/bootmap.c | 19 +++++++++++++++++--
> pc-bios/s390-ccw/bootmap.h | 10 ++++++----
> 2 files changed, 23 insertions(+), 6 deletions(-)
Skipping something that we don't have support for yet, but that doesn't
hinder normal operation sounds reasonable; but can you point me to the
relevant commit implementing this in zipl or some documentation? I
haven't been able to find something like that in the s390-tools git
tree.
next prev parent reply other threads:[~2019-04-29 13:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 13:09 [Qemu-devel] [PATCH] s390-bios: Skip bootmap signature entries Jason J. Herne
2019-04-29 13:09 ` Jason J. Herne
2019-04-29 13:40 ` Cornelia Huck [this message]
2019-04-29 13:40 ` Cornelia Huck
2019-04-29 13:45 ` Christian Borntraeger
2019-04-29 13:45 ` Christian Borntraeger
2019-04-30 9:24 ` Peter Oberparleiter
2019-04-30 9:24 ` Peter Oberparleiter
2019-04-30 9:44 ` Cornelia Huck
2019-04-30 9:44 ` Cornelia Huck
2019-05-03 9:34 ` Thomas Huth
2019-05-03 9:34 ` Thomas Huth
2019-05-06 8:08 ` Christian Borntraeger
2019-05-06 13:03 ` Jason J. Herne
2019-05-06 10:01 ` [Qemu-devel] [qemu-s390x] " David Hildenbrand
2019-05-06 10:10 ` David Hildenbrand
2019-05-06 10:16 ` Thomas Huth
2019-05-06 10:18 ` Christian Borntraeger
2019-05-06 10:34 ` Cornelia Huck
2019-05-06 10:46 ` Christian Borntraeger
2019-05-06 11:05 ` Cornelia Huck
2019-05-06 11:13 ` Christian Borntraeger
2019-05-06 11:23 ` Cornelia Huck
2019-05-06 11:24 ` Christian Borntraeger
2019-05-06 10:14 ` Christian Borntraeger
2019-05-06 10:30 ` Cornelia Huck
2019-05-06 10:45 ` Christian Borntraeger
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=20190429154003.7f8fc423.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alifm@linux.ibm.com \
--cc=borntraeger@de.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).