public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>, KVM <kvm@vger.kernel.org>
Cc: david@redhat.com, borntraeger@de.ibm.com, imbrenda@linux.ibm.com,
	cohuck@redhat.com, linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v2] s390x: Fix uv_call() exception behavior
Date: Mon, 18 Jan 2021 16:15:43 +0100	[thread overview]
Message-ID: <d876410c-fd7b-5fb8-1f9e-d3a13e9f44c3@redhat.com> (raw)
In-Reply-To: <20210118150922.5229-1-frankja@linux.ibm.com>

On 18/01/2021 16.09, Janosch Frank wrote:
> On a program exception we usually skip the instruction that caused the
> exception and continue. That won't work for UV calls since a "brc
> 3,0b" will retry the instruction if the CC is > 1. Let's forgo the brc
> when checking for privilege exceptions and use a uv_call_once().
> 
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> Suggested-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> 
> ---
>   lib/s390x/asm/uv.h | 24 ++++++++++++++++--------
>   s390x/uv-guest.c   |  6 +++---
>   2 files changed, 19 insertions(+), 11 deletions(-)
> 
> diff --git a/lib/s390x/asm/uv.h b/lib/s390x/asm/uv.h
> index 4c2fc48..39d2dc0 100644
> --- a/lib/s390x/asm/uv.h
> +++ b/lib/s390x/asm/uv.h
> @@ -50,19 +50,12 @@ struct uv_cb_share {
>   	u64 reserved28;
>   } __attribute__((packed))  __attribute__((aligned(8)));
>   
> -static inline int uv_call(unsigned long r1, unsigned long r2)
> +static inline int uv_call_once(unsigned long r1, unsigned long r2)
>   {
>   	int cc;
>   
> -	/*
> -	 * The brc instruction will take care of the cc 2/3 case where
> -	 * we need to continue the execution because we were
> -	 * interrupted. The inline assembly will only return on
> -	 * success/error i.e. cc 0/1.
> -	*/
>   	asm volatile(
>   		"0:	.insn rrf,0xB9A40000,%[r1],%[r2],0,0\n"
> -		"		brc	3,0b\n"
>   		"		ipm	%[cc]\n"
>   		"		srl	%[cc],28\n"
>   		: [cc] "=d" (cc)
> @@ -71,4 +64,19 @@ static inline int uv_call(unsigned long r1, unsigned long r2)
>   	return cc;
>   }
>   
> +static inline int uv_call(unsigned long r1, unsigned long r2)
> +{
> +	int cc;
> +
> +	/*
> +	 * CC 2 and 3 tell us to re-execute because the instruction
> +	 * hasn't yet finished.
> +	 */
> +	do {
> +		cc = uv_call_once(r1, r2);
> +	} while (cc > 1);
> +
> +	return cc;
> +}
> +
>   #endif
> diff --git a/s390x/uv-guest.c b/s390x/uv-guest.c
> index d47333e..091a19b 100644
> --- a/s390x/uv-guest.c
> +++ b/s390x/uv-guest.c
> @@ -31,7 +31,7 @@ static void test_priv(void)
>   	uvcb.len = sizeof(struct uv_cb_qui);
>   	expect_pgm_int();
>   	enter_pstate();
> -	uv_call(0, (u64)&uvcb);
> +	uv_call_once(0, (u64)&uvcb);
>   	check_pgm_int_code(PGM_INT_CODE_PRIVILEGED_OPERATION);
>   	report_prefix_pop();
>   
> @@ -40,7 +40,7 @@ static void test_priv(void)
>   	uvcb.len = sizeof(struct uv_cb_share);
>   	expect_pgm_int();
>   	enter_pstate();
> -	uv_call(0, (u64)&uvcb);
> +	uv_call_once(0, (u64)&uvcb);
>   	check_pgm_int_code(PGM_INT_CODE_PRIVILEGED_OPERATION);
>   	report_prefix_pop();
>   
> @@ -49,7 +49,7 @@ static void test_priv(void)
>   	uvcb.len = sizeof(struct uv_cb_share);
>   	expect_pgm_int();
>   	enter_pstate();
> -	uv_call(0, (u64)&uvcb);
> +	uv_call_once(0, (u64)&uvcb);
>   	check_pgm_int_code(PGM_INT_CODE_PRIVILEGED_OPERATION);
>   	report_prefix_pop();

That looks nicer, indeed.

Reviewed-by: Thomas Huth <thuth@redhat.com>

  reply	other threads:[~2021-01-18 15:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 14:03 [kvm-unit-tests PATCH] s390x: Fix uv_call() exception behavior Janosch Frank
2021-01-18 14:40 ` Thomas Huth
2021-01-18 14:46   ` Janosch Frank
2021-01-18 15:09 ` [kvm-unit-tests PATCH v2] " Janosch Frank
2021-01-18 15:15   ` Thomas Huth [this message]
2021-01-19 16:28   ` Cornelia Huck

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=d876410c-fd7b-5fb8-1f9e-d3a13e9f44c3@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=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.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