From: Janosch Frank <frankja@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>, linux-kernel@vger.kernel.org
Cc: borntraeger@de.ibm.com, david@redhat.com, cohuck@redhat.com,
kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH v4 0/2] s390/kvm: fix MVPG when in VSIE
Date: Wed, 24 Feb 2021 09:15:59 +0100 [thread overview]
Message-ID: <e35ab218-3725-86b5-cea0-c403cf39b0a6@linux.ibm.com> (raw)
In-Reply-To: <20210223191353.267981-1-imbrenda@linux.ibm.com>
On 2/23/21 8:13 PM, Claudio Imbrenda wrote:
> The current handling of the MVPG instruction when executed in a nested
> guest is wrong, and can lead to the nested guest hanging.
>
> This patchset fixes the behaviour to be more architecturally correct,
> and fixes the hangs observed.
Could you please push this to devel so we get some CI coverage.
And before you do that please exchange my ACK mail address in the first
patch for the linux one.
>
> v3->v4
> * added PEI_ prefix to DAT_PROT and NOT_PTE macros
> * added small comment to explain what they are about
>
> v2->v3
> * improved some comments
> * improved some variable and parameter names for increased readability
> * fixed missing handling of page faults in the MVPG handler
> * small readability improvements
>
> v1->v2
> * complete rewrite
>
> Claudio Imbrenda (2):
> s390/kvm: extend kvm_s390_shadow_fault to return entry pointer
> s390/kvm: VSIE: correctly handle MVPG when in VSIE
>
> arch/s390/kvm/gaccess.c | 30 ++++++++++--
> arch/s390/kvm/gaccess.h | 6 ++-
> arch/s390/kvm/vsie.c | 101 ++++++++++++++++++++++++++++++++++++----
> 3 files changed, 122 insertions(+), 15 deletions(-)
>
prev parent reply other threads:[~2021-02-24 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 19:13 [PATCH v4 0/2] s390/kvm: fix MVPG when in VSIE Claudio Imbrenda
2021-02-23 19:13 ` [PATCH v4 1/2] s390/kvm: extend kvm_s390_shadow_fault to return entry pointer Claudio Imbrenda
2021-02-23 19:13 ` [PATCH v4 2/2] s390/kvm: VSIE: correctly handle MVPG when in VSIE Claudio Imbrenda
2021-02-25 19:12 ` David Hildenbrand
2021-02-24 8:15 ` 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=e35ab218-3725-86b5-cea0-c403cf39b0a6@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).