From: Thomas Huth <thuth@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>, qemu-devel@nongnu.org
Cc: borntraeger@de.ibm.com, cohuck@redhat.com, david@redhat.com
Subject: Re: [PATCH RFC v2 3/4] pc-bios: s390x: Save io and external new PSWs before overwriting them
Date: Thu, 27 Aug 2020 14:52:55 +0200 [thread overview]
Message-ID: <c5190ed1-a4f9-45c3-97b3-4924cff5da31@redhat.com> (raw)
In-Reply-To: <20200827093152.3026-4-frankja@linux.ibm.com>
On 27/08/2020 11.31, Janosch Frank wrote:
> Currently we always overwrite the mentioned exception new PSWs before
> loading the enabled wait PSW. Let's save the PSW before overwriting
> and restore it right before starting the loaded kernel.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> ---
>
> Maybe we should rather statically allocate a lowcore so we don't dirty
> 0x0 at all.
>
> ---
> pc-bios/s390-ccw/jump2ipl.c | 3 ++
> pc-bios/s390-ccw/start.S | 62 +++++++++++++++++++++++++++----------
> 2 files changed, 48 insertions(+), 17 deletions(-)
>
> diff --git a/pc-bios/s390-ccw/jump2ipl.c b/pc-bios/s390-ccw/jump2ipl.c
> index 143d027bf7..a44f3ab5b3 100644
> --- a/pc-bios/s390-ccw/jump2ipl.c
> +++ b/pc-bios/s390-ccw/jump2ipl.c
> @@ -13,12 +13,15 @@
> #define KERN_IMAGE_START 0x010000UL
> #define RESET_PSW_MASK (PSW_MASK_SHORTPSW | PSW_MASK_64)
>
> +extern uint64_t *psw_save_io, *psw_save_ext;
I think that should be
extern uint64_t psw_save_io[], psw_save_ext[];
instead ... otherwise you'll end up with some funny bugs here, won't you?
> uint64_t *reset_psw = 0, save_psw, ipl_continue;
>
> static void jump_to_IPL_2(void)
> {
> /* Restore reset PSW and io and external new PSWs */
Ok, now the comment makes sense :-)
> *reset_psw = save_psw;
> + memcpy((void *)0x1f0, psw_save_io, 16);
> + memcpy((void *)0x1b0, psw_save_ext, 16);
Could you use &lowcore->external_new_psw and &lowcore->io_new_psw
instead of the magic numbers?
Thomas
next prev parent reply other threads:[~2020-08-27 12:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 9:31 [PATCH v2 0/4] pc-bios: s390x: Cleanup part 2 Janosch Frank
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 [this message]
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=c5190ed1-a4f9-45c3-97b3-4924cff5da31@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=qemu-devel@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).