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 v2 4/8] s390x: Introduce and use CALL_INT_HANDLER macro
Date: Wed, 17 Feb 2021 16:49:39 +0100 [thread overview]
Message-ID: <3cb211f9-cf95-4035-c880-59e0387d68e9@redhat.com> (raw)
In-Reply-To: <20210217144116.3368-5-frankja@linux.ibm.com>
On 17/02/2021 15.41, Janosch Frank wrote:
> The ELF ABI dictates that we need to allocate 160 bytes of stack space
> for the C functions we're calling.
So this actually some kind of bug fix, since we should have allocated that
area before already? Why did we never experienced any issues here so far?
Are the called functions not using the save area?
>
> diff --git a/s390x/cstart64.S b/s390x/cstart64.S
> index 35d20293..666a9567 100644
> --- a/s390x/cstart64.S
> +++ b/s390x/cstart64.S
> @@ -92,37 +92,19 @@ memsetxc:
>
> .section .text
> pgm_int:
> - SAVE_REGS_STACK
> - lgr %r2, %r15
> - brasl %r14, handle_pgm_int
> - RESTORE_REGS_STACK
> - lpswe GEN_LC_PGM_OLD_PSW
> + CALL_INT_HANDLER handle_pgm_int, GEN_LC_PGM_OLD_PSW
>
> ext_int:
> - SAVE_REGS_STACK
> - lgr %r2, %r15
> - brasl %r14, handle_ext_int
> - RESTORE_REGS_STACK
> - lpswe GEN_LC_EXT_OLD_PSW
> + CALL_INT_HANDLER handle_ext_int, GEN_LC_EXT_OLD_PSW
>
> mcck_int:
> - SAVE_REGS_STACK
> - brasl %r14, handle_mcck_int
> - RESTORE_REGS_STACK
> - lpswe GEN_LC_MCCK_OLD_PSW
> + CALL_INT_HANDLER handle_mcck_int, GEN_LC_MCCK_OLD_PSW
>
> io_int:
> - SAVE_REGS_STACK
> - lgr %r2, %r15
> - brasl %r14, handle_io_int
> - RESTORE_REGS_STACK
> - lpswe GEN_LC_IO_OLD_PSW
> + CALL_INT_HANDLER handle_io_int, GEN_LC_IO_OLD_PSW
>
> svc_int:
> - SAVE_REGS_STACK
> - brasl %r14, handle_svc_int
> - RESTORE_REGS_STACK
> - lpswe GEN_LC_SVC_OLD_PSW
> + CALL_INT_HANDLER handle_svc_int, GEN_LC_SVC_OLD_PSW
>
> .align 8
> initial_psw:
> diff --git a/s390x/macros.S b/s390x/macros.S
> index a7d62c6f..212a3823 100644
> --- a/s390x/macros.S
> +++ b/s390x/macros.S
> @@ -11,6 +11,23 @@
> * David Hildenbrand <david@redhat.com>
> */
> #include <asm/asm-offsets.h>
> +/*
> + * Exception handler macro that saves registers on the stack,
> + * allocates stack space and calls the C handler function. Afterwards
> + * we re-load the registers and load the old PSW.
> + */
> + .macro CALL_INT_HANDLER c_func, old_psw
> + SAVE_REGS_STACK
> + /* Save the stack address in GR2 which is the first function argument */
> + lgr %r2, %r15
> + /* Allocate stack pace for called C function, as specified in s390 ELF ABI */
s/pace/space/
> + slgfi %r15, 160
> + brasl %r14, \c_func
> + algfi %r15, 160
> + RESTORE_REGS_STACK
> + lpswe \old_psw
> + .endm
As long as the macro is only used in cstart64.S, I think you could also put
it there (no strong opinion on this, though).
Anyway, with the typo fixed:
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2021-02-17 15:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 14:41 [kvm-unit-tests PATCH v2 0/8] s390x: Cleanup exception register save/restore and implement backtrace Janosch Frank
2021-02-17 14:41 ` [kvm-unit-tests PATCH v2 1/8] s390x: Fix fpc store address in RESTORE_REGS_STACK Janosch Frank
2021-02-17 14:41 ` [kvm-unit-tests PATCH v2 2/8] s390x: Fully commit to stack save area for exceptions Janosch Frank
2021-02-17 15:35 ` Thomas Huth
2021-02-17 16:54 ` Janosch Frank
2021-02-17 14:41 ` [kvm-unit-tests PATCH v2 3/8] RFC: s390x: Define STACK_FRAME_INT_SIZE macro Janosch Frank
2021-02-17 15:38 ` Thomas Huth
2021-02-17 16:08 ` Janosch Frank
2021-02-17 16:10 ` Thomas Huth
2021-02-17 14:41 ` [kvm-unit-tests PATCH v2 4/8] s390x: Introduce and use CALL_INT_HANDLER macro Janosch Frank
2021-02-17 15:49 ` Thomas Huth [this message]
2021-02-17 15:55 ` Thomas Huth
2021-02-17 16:22 ` Janosch Frank
2021-02-17 17:03 ` Thomas Huth
2021-02-18 9:16 ` Janosch Frank
2021-02-17 14:41 ` [kvm-unit-tests PATCH v2 5/8] s390x: Provide preliminary backtrace support Janosch Frank
2021-02-17 16:01 ` Thomas Huth
2021-02-17 16:12 ` Janosch Frank
2021-02-17 14:41 ` [kvm-unit-tests PATCH v2 6/8] s390x: Print more information on program exceptions Janosch Frank
2021-02-17 14:41 ` [kvm-unit-tests PATCH v2 7/8] s390x: Move diag308_load_reset to stack saving Janosch Frank
2021-02-17 14:41 ` [kvm-unit-tests PATCH v2 8/8] s390x: Remove SAVE/RESTORE_stack Janosch Frank
2021-02-17 16:18 ` Thomas Huth
2021-02-17 16:46 ` Janosch Frank
2021-02-17 16:50 ` 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=3cb211f9-cf95-4035-c880-59e0387d68e9@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.