public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Mueller <mimu@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, imbrenda@linux.ibm.com,
	david@redhat.com, borntraeger@linux.ibm.com, pasic@linux.ibm.com,
	Janosch Frank <frankja@linux.ibm.com>
Subject: Re: [PATCH v4 0/2] KVM: s390: make use of ultravisor AIV support
Date: Thu, 24 Feb 2022 16:04:20 +0100	[thread overview]
Message-ID: <f0dfd041-8be4-8569-27ac-63f5a7635823@linux.ibm.com> (raw)
In-Reply-To: <20220223102000.3733712-1-mimu@linux.ibm.com>



On 23.02.22 11:19, Michael Mueller wrote:
> This patch enables the ultravisor adapter interruption vitualization
> support.
> 
> Changes in v4:
> - All vcpus are pulled out of SIE and disbled before the control
>    blocks are changed to disable/enable the gisa and re-enabled
>    afterwards instead of taking the vcpu specific lock.


Christian,

I'm pulling back this v4 and ask for v3 to be re-applied as it turned
out that the described issue is related to kvm_s390_set_tod_clock()
being called in SIE intercepted context.

> 
> Changes in v3:
> - cache and test GISA descriptor only once in kvm_s390_gisa_enable()
> - modified some comments
> - removed some whitespace issues
> 
> Changes in v2:
> - moved GISA disable into "put CPUs in PV mode" routine
> - moved GISA enable into "pull CPUs out of PV mode" routine
> 
> [1] https://lore.kernel.org/lkml/ae7c65d8-f632-a7f4-926a-50b9660673a1@linux.ibm.com/T/#mcb67699bf458ba7482f6b7529afe589d1dbb5930
> [2] https://lore.kernel.org/all/20220208165310.3905815-1-mimu@linux.ibm.com/
> [3] https://lore.kernel.org/all/20220209152217.1793281-2-mimu@linux.ibm.com/
> 
> Michael Mueller (2):
>    KVM: s390: pv: pull all vcpus out of SIE before converting to/from pv
>      vcpu
>    KVM: s390: pv: make use of ultravisor AIV support
> 
>   arch/s390/include/asm/uv.h |  1 +
>   arch/s390/kvm/interrupt.c  | 54 +++++++++++++++++++++++++++++++++-----
>   arch/s390/kvm/kvm-s390.c   | 19 +++++++++-----
>   arch/s390/kvm/kvm-s390.h   | 11 ++++++++
>   4 files changed, 72 insertions(+), 13 deletions(-)
> 

      parent reply	other threads:[~2022-02-24 15:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 10:19 [PATCH v4 0/2] KVM: s390: make use of ultravisor AIV support Michael Mueller
2022-02-23 10:19 ` [PATCH v4 1/2] KVM: s390: pv: pull all vcpus out of SIE before converting to/from pv vcpu Michael Mueller
2022-02-23 10:20 ` [PATCH v4 2/2] KVM: s390: pv: make use of ultravisor AIV support Michael Mueller
2022-02-24 15:04 ` Michael Mueller [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=f0dfd041-8be4-8569-27ac-63f5a7635823@linux.ibm.com \
    --to=mimu@linux.ibm.com \
    --cc=borntraeger@linux.ibm.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 \
    --cc=pasic@linux.ibm.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