From: Thomas Huth <thuth@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, imbrenda@linux.ibm.com,
pmorel@linux.ibm.com, david@redhat.com
Subject: Re: [kvm-unit-tests PATCH v3 6/7] s390x: Move diag308_load_reset to stack saving
Date: Thu, 4 Mar 2021 13:26:47 +0100 [thread overview]
Message-ID: <c26c5d2f-5111-af3e-abde-234f199decc3@redhat.com> (raw)
In-Reply-To: <20210222085756.14396-7-frankja@linux.ibm.com>
On 22/02/2021 09.57, Janosch Frank wrote:
> By moving the last user of SAVE/RESTORE_REGS to the macros that use
> the stack we can finally remove these macros.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> Reviewed-by: Pierre Morel <pmorel@linux.ibm.com>
> ---
> s390x/cpu.S | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/s390x/cpu.S b/s390x/cpu.S
> index 5267f029..e2ad56c8 100644
> --- a/s390x/cpu.S
> +++ b/s390x/cpu.S
> @@ -18,7 +18,7 @@
> */
> .globl diag308_load_reset
> diag308_load_reset:
> - SAVE_REGS
> + SAVE_REGS_STACK
> /* Backup current PSW mask, as we have to restore it on success */
> epsw %r0, %r1
> st %r0, GEN_LC_SW_INT_PSW
> @@ -31,6 +31,7 @@ diag308_load_reset:
> ogr %r0, %r1
> /* Store it at the reset PSW location (real 0x0) */
> stg %r0, 0
> + stg %r15, GEN_LC_SW_INT_GRS + 15 * 8
> /* Do the reset */
> diag %r0,%r2,0x308
> /* Failure path */
> @@ -40,7 +41,8 @@ diag308_load_reset:
> /* load a cr0 that has the AFP control bit which enables all FPRs */
> 0: larl %r1, initial_cr0
> lctlg %c0, %c0, 0(%r1)
> - RESTORE_REGS
> + lg %r15, GEN_LC_SW_INT_GRS + 15 * 8
> + RESTORE_REGS_STACK
> lhi %r2, 1
> larl %r0, 1f
> stg %r0, GEN_LC_SW_INT_PSW + 8
>
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2021-03-04 12:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 8:57 [kvm-unit-tests PATCH v3 0/7] s390x: Cleanup exception register save/restore and implement backtrace Janosch Frank
2021-02-22 8:57 ` [kvm-unit-tests PATCH v3 1/7] s390x: Fix fpc store address in RESTORE_REGS_STACK Janosch Frank
2021-02-22 8:57 ` [kvm-unit-tests PATCH v3 2/7] s390x: Fully commit to stack save area for exceptions Janosch Frank
2021-03-04 11:37 ` Thomas Huth
2021-03-04 15:57 ` Janosch Frank
2021-02-22 8:57 ` [kvm-unit-tests PATCH v3 3/7] s390x: Introduce and use CALL_INT_HANDLER macro Janosch Frank
2021-03-04 12:58 ` Claudio Imbrenda
2021-02-22 8:57 ` [kvm-unit-tests PATCH v3 4/7] s390x: Provide preliminary backtrace support Janosch Frank
2021-03-04 12:23 ` Thomas Huth
2021-03-04 13:02 ` Claudio Imbrenda
2021-02-22 8:57 ` [kvm-unit-tests PATCH v3 5/7] s390x: Print more information on program exceptions Janosch Frank
2021-03-04 12:24 ` Thomas Huth
2021-02-22 8:57 ` [kvm-unit-tests PATCH v3 6/7] s390x: Move diag308_load_reset to stack saving Janosch Frank
2021-03-04 12:26 ` Thomas Huth [this message]
2021-02-22 8:57 ` [kvm-unit-tests PATCH v3 7/7] s390x: Remove SAVE/RESTORE_STACK and lowcore fpc and fprs save areas Janosch Frank
2021-03-04 12:28 ` 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=c26c5d2f-5111-af3e-abde-234f199decc3@redhat.com \
--to=thuth@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pmorel@linux.ibm.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