Linux virtualization list
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, kvm@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] virtio-ccw: diag 500 may return a negative cookie
Date: Wed, 19 Dec 2018 11:06:11 +0100	[thread overview]
Message-ID: <20181219110611.66c7b18b.cohuck@redhat.com> (raw)
In-Reply-To: <20181218132034.14863-1-cohuck@redhat.com>

On Tue, 18 Dec 2018 14:20:34 +0100
Cornelia Huck <cohuck@redhat.com> wrote:

> If something goes wrong in the kvm io bus handling, the virtio-ccw
> diagnose may return a negative error value in the cookie gpr.
> 
> Document this.
> 
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
> 
> Even if the virtio spec is the correct place to specify what diag 500
> subcode 3 does, we also should mention here that the cookie may be
> an error.
> 
> ---
>  Documentation/virtual/kvm/s390-diag.txt | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/virtual/kvm/s390-diag.txt b/Documentation/virtual/kvm/s390-diag.txt
> index 48c4921794ed..7c52e5f8b210 100644
> --- a/Documentation/virtual/kvm/s390-diag.txt
> +++ b/Documentation/virtual/kvm/s390-diag.txt
> @@ -68,7 +68,8 @@ Subcode 3 - virtio-ccw notification
>      identifier, it is ignored.
>  
>      After completion of the DIAGNOSE call, general register 2 may contain
> -    a 64bit identifier (in the kvm_io_bus cookie case).
> +    a 64bit identifier (in the kvm_io_bus cookie case), or a negative
> +    error value, if an internal error occurred.
>  
>      See also the virtio standard for a discussion of this hypercall.
>  

Queued.

      reply	other threads:[~2018-12-19 10:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18 13:20 [PATCH] virtio-ccw: diag 500 may return a negative cookie Cornelia Huck
2018-12-19 10:06 ` 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=20181219110611.66c7b18b.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pasic@linux.ibm.com \
    --cc=virtualization@lists.linux-foundation.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