public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org,
	Claudio Imbrenda <imbrenda@linux.ibm.com>,
	David Hildenbrand <david@redhat.com>
Subject: Re: [kvm-unit-tests PATCH] s390x/snippets: Define all things that are needed to link the libc
Date: Wed, 13 Oct 2021 11:51:27 +0200	[thread overview]
Message-ID: <4bb5ae96-2a01-c151-c1d9-9efedd2960f0@linux.ibm.com> (raw)
In-Reply-To: <20211008092649.959956-1-thuth@redhat.com>

On 10/8/21 11:26, Thomas Huth wrote:
> In the long run, we want to use parts of the libc like memset() etc.,
> too. However, to be able to link it correctly, we have to provide
> some stub functions like puts() and exit() to avoid that too much
> other stuff from the lib folder gets pulled into the binaries, which
> we cannot provide in the snippets (like the sclp support).
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>

Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
Thanks, picked!

> ---
>   s390x/Makefile            |  2 +-
>   s390x/snippets/c/cstart.S | 11 +++++++++++
>   2 files changed, 12 insertions(+), 1 deletion(-)
> 
> diff --git a/s390x/Makefile b/s390x/Makefile
> index ef8041a..b2a7c1f 100644
> --- a/s390x/Makefile
> +++ b/s390x/Makefile
> @@ -80,7 +80,7 @@ asmlib = $(TEST_DIR)/cstart64.o $(TEST_DIR)/cpu.o
>   FLATLIBS = $(libcflat)
>   
>   SNIPPET_DIR = $(TEST_DIR)/snippets
> -snippet_asmlib = $(SNIPPET_DIR)/c/cstart.o
> +snippet_asmlib = $(SNIPPET_DIR)/c/cstart.o lib/auxinfo.o
>   
>   # perquisites (=guests) for the snippet hosts.
>   # $(TEST_DIR)/<snippet-host>.elf: snippets = $(SNIPPET_DIR)/<c/asm>/<snippet>.gbin
> diff --git a/s390x/snippets/c/cstart.S b/s390x/snippets/c/cstart.S
> index a175480..1862703 100644
> --- a/s390x/snippets/c/cstart.S
> +++ b/s390x/snippets/c/cstart.S
> @@ -20,6 +20,17 @@ start:
>   	lghi	%r15, 0x4000 - 160
>   	sam64
>   	brasl	%r14, main
> +	/*
> +	 * If main() returns, we stop the CPU with the code below. We also
> +	 * route some functions that are required by the libc (but not usable
> +	 * from snippets) to the CPU stop code below, so that snippets can
> +	 * still be linked against the libc code (to use non-related functions
> +	 * like memset() etc.)
> +	 */
> +.global puts
> +.global exit
> +puts:
> +exit:
>   	/* For now let's only use cpu 0 in snippets so this will always work. */
>   	xgr	%r0, %r0
>   	sigp    %r2, %r0, SIGP_STOP
> 


      reply	other threads:[~2021-10-13  9:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08  9:26 [kvm-unit-tests PATCH] s390x/snippets: Define all things that are needed to link the libc Thomas Huth
2021-10-13  9:51 ` Janosch Frank [this message]

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=4bb5ae96-2a01-c151-c1d9-9efedd2960f0@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.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