From: Janosch Frank <frankja@linux.ibm.com>
To: qemu-devel@nongnu.org
Cc: borntraeger@de.ibm.com, thuth@redhat.com, cohuck@redhat.com,
david@redhat.com
Subject: [PATCH v2 0/4] pc-bios: s390x: Cleanup part 2
Date: Thu, 27 Aug 2020 05:31:48 -0400 [thread overview]
Message-ID: <20200827093152.3026-1-frankja@linux.ibm.com> (raw)
So, here are a few more cleanup patches mostly cleaning up ipl code
and some of the assembly.
The patches are available here:
https://github.com/frankjaa/qemu/pull/new/cleanup_bios2
v2:
* Fixed psw saving in use reset psw patch (thanks Jason)
* Dropped a lot of patches which weren't strictly necessary
* Added disabled wait patch
* Added RFC PSW save patch
Janosch Frank (4):
pc-bios: s390x: Fix bootmap.c zipl component entry data handling
pc-bios: s390x: Use reset PSW if avaliable
pc-bios: s390x: Save io and external new PSWs before overwriting them
pc-bios: s390x: Go into disabled wait when encountering a PGM
exception
pc-bios/s390-ccw/bootmap.c | 6 ++--
pc-bios/s390-ccw/bootmap.h | 7 +++-
pc-bios/s390-ccw/jump2ipl.c | 51 ++++++++++++++++++-----------
pc-bios/s390-ccw/s390-ccw.h | 1 +
pc-bios/s390-ccw/start.S | 65 +++++++++++++++++++++++++++----------
5 files changed, 91 insertions(+), 39 deletions(-)
--
2.25.1
next reply other threads:[~2020-08-27 9:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 9:31 Janosch Frank [this message]
2020-08-27 9:31 ` [PATCH v2 1/4] pc-bios: s390x: Fix bootmap.c zipl component entry data handling Janosch Frank
2020-08-27 9:31 ` [PATCH v2 2/4] pc-bios: s390x: Use reset PSW if avaliable Janosch Frank
2020-08-27 12:43 ` Thomas Huth
2020-08-27 9:31 ` [PATCH RFC v2 3/4] pc-bios: s390x: Save io and external new PSWs before overwriting them Janosch Frank
2020-08-27 12:52 ` Thomas Huth
2020-08-27 14:30 ` Janosch Frank
2020-08-27 16:16 ` Thomas Huth
2020-08-27 9:31 ` [PATCH v2 4/4] pc-bios: s390x: Go into disabled wait when encountering a PGM exception Janosch Frank
2020-08-31 8:23 ` 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=20200827093152.3026-1-frankja@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=qemu-devel@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).