From: Michael Mueller <mimu@linux.ibm.com>
To: Steffen Eiden <seiden@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
kvm@vger.kernel.org
Cc: Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
Michael Mueller <mimu@linux.vnet.ibm.com>,
Marc Hartmayer <mhartmay@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Viktor Mihajlovski <mihajlov@linux.ibm.com>
Subject: Re: [PATCH v4 1/4] KVM: s390: pv: relax WARN_ONCE condition for destroy fast
Date: Thu, 17 Aug 2023 12:59:54 +0200 [thread overview]
Message-ID: <5b671c7c-dcc8-9c33-6eb5-58c5921708a1@linux.ibm.com> (raw)
In-Reply-To: <20230815151415.379760-2-seiden@linux.ibm.com>
On 15.08.23 17:14, Steffen Eiden wrote:
> From: Viktor Mihajlovski <mihajlov@linux.ibm.com>
>
> Destroy configuration fast may return with RC 0x104 if there
> are still bound APQNs in the configuration. The final cleanup
> will occur with the standard destroy configuration UVC as
> at this point in time all APQNs have been reset and thus
> unbound. Therefore, don't warn if RC 0x104 is reported.
>
> Signed-off-by: Viktor Mihajlovski <mihajlov@linux.ibm.com>
> Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
> Reviewed-by: Steffen Eiden <seiden@linux.ibm.com>
Reviewed-by: Michael Mueller <mimu@linux.ibm.com>
> ---
> arch/s390/kvm/pv.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/s390/kvm/pv.c b/arch/s390/kvm/pv.c
> index 8d3f39a8a11e..8570ee324607 100644
> --- a/arch/s390/kvm/pv.c
> +++ b/arch/s390/kvm/pv.c
> @@ -285,7 +285,8 @@ static int kvm_s390_pv_deinit_vm_fast(struct kvm *kvm, u16 *rc, u16 *rrc)
> WRITE_ONCE(kvm->arch.gmap->guest_handle, 0);
> KVM_UV_EVENT(kvm, 3, "PROTVIRT DESTROY VM FAST: rc %x rrc %x",
> uvcb.header.rc, uvcb.header.rrc);
> - WARN_ONCE(cc, "protvirt destroy vm fast failed handle %llx rc %x rrc %x",
> + WARN_ONCE(cc && uvcb.header.rc != 0x104,
> + "protvirt destroy vm fast failed handle %llx rc %x rrc %x",
> kvm_s390_pv_get_handle(kvm), uvcb.header.rc, uvcb.header.rrc);
> /* Intended memory leak on "impossible" error */
> if (!cc)
next prev parent reply other threads:[~2023-08-17 11:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 15:14 [PATCH v4 0/4] KVM: s390: Enable AP instructions for PV-guests Steffen Eiden
2023-08-15 15:14 ` [PATCH v4 1/4] KVM: s390: pv: relax WARN_ONCE condition for destroy fast Steffen Eiden
2023-08-17 10:59 ` Michael Mueller [this message]
2023-08-15 15:14 ` [PATCH v4 2/4] s390: uv: UV feature check utility Steffen Eiden
2023-08-17 11:00 ` Michael Mueller
2023-08-15 15:14 ` [PATCH v4 3/4] KVM: s390: Add UV feature negotiation Steffen Eiden
2023-08-17 11:49 ` Michael Mueller
2023-08-15 15:14 ` [PATCH v4 4/4] KVM: s390: pv: Allow AP-instructions for pv-guests Steffen Eiden
2023-08-17 11:51 ` Michael Mueller
2023-08-17 11:56 ` [PATCH v4 0/4] KVM: s390: Enable AP instructions for PV-guests Janosch Frank
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=5b671c7c-dcc8-9c33-6eb5-58c5921708a1@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-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mhartmay@linux.ibm.com \
--cc=mihajlov@linux.ibm.com \
--cc=mimu@linux.vnet.ibm.com \
--cc=seiden@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