From: Cornelia Huck <cohuck@redhat.com>
To: Ladi Prosek <lprosek@redhat.com>
Cc: qemu-devel@nongnu.org, casasfernando@hotmail.com, mst@redhat.com,
jasowang@redhat.com, armbru@redhat.com, groug@kaod.org,
arei.gonglei@huawei.com, aneesh.kumar@linux.vnet.ibm.com,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 8/8] virtio-crypto: use virtqueue_error for errors with queue context
Date: Thu, 13 Jul 2017 17:20:44 +0200 [thread overview]
Message-ID: <20170713172044.418abc4b@gondolin> (raw)
In-Reply-To: <20170713110237.6712-9-lprosek@redhat.com>
On Thu, 13 Jul 2017 13:02:37 +0200
Ladi Prosek <lprosek@redhat.com> wrote:
> virtqueue_error includes queue index in the error output and is preferred
> for errors that pertain to a virtqueue rather than to the device as a whole.
>
> Signed-off-by: Ladi Prosek <lprosek@redhat.com>
> ---
> hw/virtio/virtio-crypto.c | 56 ++++++++++++++++++++++++-----------------------
> 1 file changed, 29 insertions(+), 27 deletions(-)
>
> diff --git a/hw/virtio/virtio-crypto.c b/hw/virtio/virtio-crypto.c
> index 0353eb6..08e6c03 100644
> --- a/hw/virtio/virtio-crypto.c
> +++ b/hw/virtio/virtio-crypto.c
> @@ -35,6 +35,7 @@ static inline int virtio_crypto_vq2q(int queue_index)
>
> static int
> virtio_crypto_cipher_session_helper(VirtIODevice *vdev,
> + VirtQueue *ctrl_vq,
> CryptoDevBackendSymSessionInfo *info,
> struct virtio_crypto_cipher_session_para *cipher_para,
> struct iovec **iov, unsigned int *out_num)
> @@ -61,7 +62,7 @@ virtio_crypto_cipher_session_helper(VirtIODevice *vdev,
> info->cipher_key = g_malloc(info->key_len);
> s = iov_to_buf(*iov, num, 0, info->cipher_key, info->key_len);
> if (unlikely(s != info->key_len)) {
> - virtio_error(vdev, "virtio-crypto cipher key incorrect");
> + virtqueue_error(ctrl_vq, "virtio-crypto cipher key incorrect");
As virtio-crypto devices always have one control queue, I would just
use the pointer stored in the vcrypto structure. This avoids some of
the cascading function signature changes.
> return -EFAULT;
> }
> iov_discard_front(iov, &num, info->key_len);
next prev parent reply other threads:[~2017-07-13 15:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 11:02 [Qemu-devel] [PATCH v2 0/8] virtio: enhance virtio_error messages Ladi Prosek
2017-07-13 11:02 ` [Qemu-devel] [PATCH v2 1/8] qemu-error: introduce error_report_nolf Ladi Prosek
2017-07-13 13:32 ` Stefan Hajnoczi
2017-07-13 13:48 ` Ladi Prosek
2017-07-14 10:25 ` Stefan Hajnoczi
2017-07-15 5:50 ` Markus Armbruster
2017-07-17 6:43 ` Ladi Prosek
2017-07-14 10:41 ` Daniel P. Berrange
2017-07-17 6:54 ` Ladi Prosek
2017-07-17 8:58 ` Daniel P. Berrange
2017-07-17 9:30 ` Ladi Prosek
2017-07-13 11:02 ` [Qemu-devel] [PATCH v2 2/8] virtio: enhance virtio_error messages Ladi Prosek
2017-07-13 13:40 ` Stefan Hajnoczi
2017-07-13 13:58 ` Ladi Prosek
2017-07-13 11:02 ` [Qemu-devel] [PATCH v2 3/8] virtio: introduce virtqueue_error Ladi Prosek
2017-07-13 14:42 ` Cornelia Huck
2017-07-13 15:02 ` Ladi Prosek
2017-07-14 10:28 ` Stefan Hajnoczi
2017-07-13 11:02 ` [Qemu-devel] [PATCH v2 4/8] virtio-9p: use virtqueue_error for errors with queue context Ladi Prosek
2017-07-13 14:21 ` Greg Kurz
2017-07-13 14:49 ` Cornelia Huck
2017-07-14 10:29 ` Stefan Hajnoczi
2017-07-13 11:02 ` [Qemu-devel] [PATCH v2 5/8] virtio-blk: " Ladi Prosek
2017-07-13 14:54 ` Cornelia Huck
2017-07-14 10:29 ` Stefan Hajnoczi
2017-07-13 11:02 ` [Qemu-devel] [PATCH v2 6/8] virtio-net: " Ladi Prosek
2017-07-13 15:00 ` Cornelia Huck
2017-07-14 10:30 ` Stefan Hajnoczi
2017-07-13 11:02 ` [Qemu-devel] [PATCH v2 7/8] virtio-scsi: " Ladi Prosek
2017-07-13 15:03 ` Cornelia Huck
2017-07-14 10:30 ` Stefan Hajnoczi
2017-07-13 11:02 ` [Qemu-devel] [PATCH v2 8/8] virtio-crypto: " Ladi Prosek
2017-07-13 15:20 ` Cornelia Huck [this message]
2017-07-13 15:31 ` Ladi Prosek
2017-07-13 15:36 ` Cornelia Huck
2017-07-14 0:51 ` Gonglei (Arei)
2017-07-14 10:31 ` Stefan Hajnoczi
2017-07-13 14:36 ` [Qemu-devel] [PATCH v2 0/8] virtio: enhance virtio_error messages Greg Kurz
2017-07-13 15:00 ` Ladi Prosek
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=20170713172044.418abc4b@gondolin \
--to=cohuck@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=arei.gonglei@huawei.com \
--cc=armbru@redhat.com \
--cc=casasfernando@hotmail.com \
--cc=groug@kaod.org \
--cc=jasowang@redhat.com \
--cc=lprosek@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).