From: Halil Pasic <pasic@linux.ibm.com>
To: Tony Krowiak <akrowiak@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, jjherne@linux.ibm.com,
borntraeger@linux.ibm.com, frankja@linux.ibm.com,
imbrenda@linux.ibm.com, david@redhat.com,
Halil Pasic <pasic@linux.ibm.com>
Subject: Re: [PATCH v2 2/3] s390/vfio-ap: set status response code to 06 on gisc registration failure
Date: Fri, 27 Oct 2023 12:56:38 +0200 [thread overview]
Message-ID: <20231027125638.67a65ab9.pasic@linux.ibm.com> (raw)
In-Reply-To: <20231018133829.147226-3-akrowiak@linux.ibm.com>
On Wed, 18 Oct 2023 09:38:24 -0400
Tony Krowiak <akrowiak@linux.ibm.com> wrote:
> From: Anthony Krowiak <akrowiak@linux.ibm.com>
>
> The interception handler for the PQAP(AQIC) command calls the
> kvm_s390_gisc_register function to register the guest ISC with the channel
> subsystem. If that call fails, the status response code 08 - indicating
> Invalid ZONE/GISA designation - is returned to the guest. This response
> code does not make sense because the non-zero return code from the
> kvm_s390_gisc_register function can be due one of two things: Either the
> ISC passed as a parameter by the guest to the PQAP(AQIC) command is greater
> than the maximum ISC value allowed, or the guest is not using a GISA.
The "ISC passed as a parameter by the guest to the PQAP(AQIC) command is
greater than the maximum ISC value allowed" is not possible. The isc is
3 bits wide and all 8 values that can be represented on 3 bits are valid.
This is only possible if the hypervisor was to mess up, or if the machine
was broken.
>
> Since this scenario is very unlikely to happen and there is no status
> response code to indicate an invalid ISC value, let's set the
> response code to 06 indicating 'Invalid address of AP-queue notification
> byte'. While this is not entirely accurate, it is better than indicating
> that the ZONE/GISA designation is invalid which is something the guest
> can do nothing about since those values are set by the hypervisor.
>
> Signed-off-by: Anthony Krowiak <akrowiak@linux.ibm.com>
> Suggested-by: Halil Pasic <pasic@linux.ibm.com>
> ---
> drivers/s390/crypto/vfio_ap_ops.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/s390/crypto/vfio_ap_ops.c b/drivers/s390/crypto/vfio_ap_ops.c
> index 9cb28978c186..25d7ce2094f8 100644
> --- a/drivers/s390/crypto/vfio_ap_ops.c
> +++ b/drivers/s390/crypto/vfio_ap_ops.c
> @@ -393,8 +393,8 @@ static int ensure_nib_shared(unsigned long addr, struct gmap *gmap)
> * Register the guest ISC to GIB interface and retrieve the
> * host ISC to issue the host side PQAP/AQIC
> *
> - * Response.status may be set to AP_RESPONSE_INVALID_ADDRESS in case the
> - * vfio_pin_pages failed.
> + * status.response_code may be set to AP_RESPONSE_INVALID_ADDRESS in case the
> + * vfio_pin_pages or kvm_s390_gisc_register failed.
> *
> * Otherwise return the ap_queue_status returned by the ap_aqic(),
> * all retry handling will be done by the guest.
> @@ -458,7 +458,7 @@ static struct ap_queue_status vfio_ap_irq_enable(struct vfio_ap_queue *q,
> __func__, nisc, isc, q->apqn);
>
> vfio_unpin_pages(&q->matrix_mdev->vdev, nib, 1);
> - status.response_code = AP_RESPONSE_INVALID_GISA;
> + status.response_code = AP_RESPONSE_INVALID_ADDRESS;
> return status;
> }
>
next prev parent reply other threads:[~2023-10-27 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 13:38 [PATCH v2 0/3] a couple of corrections to the IRQ enablement function Tony Krowiak
2023-10-18 13:38 ` [PATCH v2 1/3] s390/vfio-ap: unpin pages on gisc registration failure Tony Krowiak
2023-10-26 12:18 ` Christian Borntraeger
2023-10-26 13:16 ` Tony Krowiak
2023-10-26 13:25 ` Christian Borntraeger
2023-10-26 14:20 ` Tony Krowiak
2023-10-18 13:38 ` [PATCH v2 2/3] s390/vfio-ap: set status response code to 06 " Tony Krowiak
2023-10-27 10:56 ` Halil Pasic [this message]
[not found] ` <8eb41445-1eff-4da7-830f-156f420afd5d@linux.ibm.com>
[not found] ` <20231027160347.05c6cd60.pasic@linux.ibm.com>
2023-10-27 17:06 ` Tony Krowiak
2023-10-18 13:38 ` [PATCH v2 3/3] s390/vfio-ap: improve reaction to response code 07 from PQAP(AQIC) command Tony Krowiak
2023-10-26 14:15 ` Matthew Rosato
2023-10-26 18:18 ` Tony Krowiak
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=20231027125638.67a65ab9.pasic@linux.ibm.com \
--to=pasic@linux.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=jjherne@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