public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Marc Hartmayer <mhartmay@linux.ibm.com>, kvm@vger.kernel.org
Cc: David Hildenbrand <david@redhat.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>,
	Nina Schoetterl-Glausch <nsg@linux.ibm.com>,
	Nico Boehr <nrb@linux.ibm.com>, Thomas Huth <thuth@redhat.com>
Subject: Re: [kvm-unit-tests PATCH 6/9] s390x: define a macro for the stack frame size
Date: Wed, 18 Jan 2023 09:27:25 +0100	[thread overview]
Message-ID: <87ace2e2-8c0f-e4b7-addc-6ef04e8d29c4@linux.ibm.com> (raw)
In-Reply-To: <20230116175757.71059-7-mhartmay@linux.ibm.com>

On 1/16/23 18:57, Marc Hartmayer wrote:
> Define and use a macro for the stack frame size.

There are two more instances in s390x/macros.S and there might be some 
in s390x/gs.c.

> 
> Signed-off-by: Marc Hartmayer <mhartmay@linux.ibm.com>
> ---
>   lib/s390x/asm-offsets.c | 1 +
>   s390x/cstart64.S        | 2 +-
>   2 files changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/lib/s390x/asm-offsets.c b/lib/s390x/asm-offsets.c
> index f612f3277a95..188dd2e51181 100644
> --- a/lib/s390x/asm-offsets.c
> +++ b/lib/s390x/asm-offsets.c
> @@ -87,6 +87,7 @@ int main(void)
>   	OFFSET(STACK_FRAME_INT_GRS0, stack_frame_int, grs0);
>   	OFFSET(STACK_FRAME_INT_GRS1, stack_frame_int, grs1);
>   	DEFINE(STACK_FRAME_INT_SIZE, sizeof(struct stack_frame_int));
> +	DEFINE(STACK_FRAME_SIZE, sizeof(struct stack_frame));

I'm wondering why we didn't do this when Pierre introduced the int stacks...

>   
>   	return 0;
>   }
> diff --git a/s390x/cstart64.S b/s390x/cstart64.S
> index 6f83da2a6c0a..468ace3ea4df 100644
> --- a/s390x/cstart64.S
> +++ b/s390x/cstart64.S
> @@ -38,7 +38,7 @@ start:
>   	/* setup stack */
>   	larl	%r15, stackptr
>   	/* Clear first stack frame */
> -	xc      0(160,%r15), 0(%r15)
> +	xc      0(STACK_FRAME_SIZE,%r15), 0(%r15)
>   	/* setup initial PSW mask + control registers*/
>   	larl	%r1, initial_psw
>   	lpswe	0(%r1)


  reply	other threads:[~2023-01-18  9:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16 17:57 [kvm-unit-tests PATCH 0/9] Some cleanup patches Marc Hartmayer
2023-01-16 17:57 ` [kvm-unit-tests PATCH 1/9] .gitignore: ignore `s390x/comm.key` file Marc Hartmayer
2023-01-18  8:10   ` Janosch Frank
2023-01-16 17:57 ` [kvm-unit-tests PATCH 2/9] s390x/Makefile: simplify `%.hdr` target rules Marc Hartmayer
2023-01-18  8:14   ` Janosch Frank
2023-01-16 17:57 ` [kvm-unit-tests PATCH 3/9] s390x/Makefile: fix `*.gbin` target dependencies Marc Hartmayer
2023-01-16 18:20   ` Claudio Imbrenda
2023-01-18  8:19   ` Janosch Frank
2023-01-18  8:37     ` Marc Hartmayer
2023-01-16 17:57 ` [kvm-unit-tests PATCH 4/9] s390x/Makefile: refactor CPPFLAGS Marc Hartmayer
2023-01-16 17:57 ` [kvm-unit-tests PATCH 5/9] s390x/Makefile: remove unused include path Marc Hartmayer
2023-01-16 18:20   ` Claudio Imbrenda
2023-01-16 17:57 ` [kvm-unit-tests PATCH 6/9] s390x: define a macro for the stack frame size Marc Hartmayer
2023-01-18  8:27   ` Janosch Frank [this message]
2023-01-18  9:04     ` Marc Hartmayer
2023-01-16 17:57 ` [kvm-unit-tests PATCH 7/9] s390x: use C pre-processor for linker script generation Marc Hartmayer
2023-01-16 18:22   ` Claudio Imbrenda
2023-01-17  9:43     ` Marc Hartmayer
2023-01-17 10:24       ` Claudio Imbrenda
2023-01-17 11:19         ` Marc Hartmayer
2023-01-17 11:21       ` Claudio Imbrenda
2023-01-16 17:57 ` [kvm-unit-tests PATCH 8/9] s390x: use STACK_FRAME_SIZE macro in linker scripts Marc Hartmayer
2023-01-16 18:23   ` Claudio Imbrenda
2023-01-18  9:10   ` Marc Hartmayer
2023-01-16 17:57 ` [kvm-unit-tests PATCH 9/9] lib/linux/const.h: test for `__ASSEMBLER__` as well Marc Hartmayer
2023-01-16 18:25   ` Claudio Imbrenda
2023-01-17  9:39     ` Marc Hartmayer
2023-01-17 10:28       ` Claudio Imbrenda

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=87ace2e2-8c0f-e4b7-addc-6ef04e8d29c4@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=mhartmay@linux.ibm.com \
    --cc=nrb@linux.ibm.com \
    --cc=nsg@linux.ibm.com \
    --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