All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: thuth@redhat.com, david@redhat.com, borntraeger@de.ibm.com,
	imbrenda@linux.ibm.com, linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v2] s390x: Fix uv_call() exception behavior
Date: Tue, 19 Jan 2021 17:28:30 +0100	[thread overview]
Message-ID: <20210119172754.6eefa4da.cohuck@redhat.com> (raw)
In-Reply-To: <20210118150922.5229-1-frankja@linux.ibm.com>

On Mon, 18 Jan 2021 10:09:22 -0500
Janosch Frank <frankja@linux.ibm.com> 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(-)

Reviewed-by: Cornelia Huck <cohuck@redhat.com>

      parent reply	other threads:[~2021-01-19 16:30 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
2021-01-19 16:28   ` Cornelia Huck [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=20210119172754.6eefa4da.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --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 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.