From: Stefan Hajnoczi <stefanha@redhat.com>
To: Gonglei <arei.gonglei@huawei.com>
Cc: qemu-devel@nongnu.org, virtio-dev@lists.oasis-open.org,
luonengjun@huawei.com, mst@redhat.com, pbonzini@redhat.com,
berrange@redhat.com, weidong.huang@huawei.com,
wu.wubin@huawei.com, mike.caraman@nxp.com, agraf@suse.de,
xin.zeng@intel.com, claudio.fontana@huawei.com, nmorey@kalray.eu,
vincent.jardin@6wind.com, jianjay.zhou@huawei.com,
hanweidong@huawei.com, peter.huangpeng@huawei.com
Subject: Re: [Qemu-devel] [PATCH v4 05/13] virtio-crypto: add virtio crypto device emulation
Date: Tue, 4 Oct 2016 10:38:20 +0100 [thread overview]
Message-ID: <20161004093820.GE4587@stefanha-x1.localdomain> (raw)
In-Reply-To: <1475051152-400276-6-git-send-email-arei.gonglei@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2609 bytes --]
On Wed, Sep 28, 2016 at 04:25:44PM +0800, Gonglei wrote:
> Introduce the virtio crypto realization, I'll
> finish the core code in the following patches. The
> thoughts came from virtio net realization.
>
> For more information see:
> http://qemu-project.org/Features/VirtioCrypto
This patch contains functions and struct fields that are unused. It
would make code review easier if you add them when they are needed
throughout the patch series.
> +static void virtio_crypto_device_realize(DeviceState *dev, Error **errp)
> +{
> + VirtIODevice *vdev = VIRTIO_DEVICE(dev);
> + VirtIOCrypto *vcrypto = VIRTIO_CRYPTO(dev);
> + int i;
> +
> + vcrypto->cryptodev = vcrypto->conf.cryptodev;
> + if (vcrypto->cryptodev == NULL) {
> + error_setg(errp, "'cryptodev' parameter expects a valid object");
> + return;
> + }
> +
> + vcrypto->max_queues = MAX(vcrypto->cryptodev->conf.peers.queues, 1);
> + if (vcrypto->max_queues + 1 > VIRTIO_QUEUE_MAX) {
> + error_setg(errp, "Invalid number of queues (= %" PRIu16 "), "
> + "must be a postive integer less than %d.",
> + vcrypto->max_queues, VIRTIO_QUEUE_MAX - 1);
The error message is off by 1:
must be a positive integer less than VIRTIO_QUEUE_MAX
> + return;
> + }
> +
> + virtio_init(vdev, "virtio-crypto", VIRTIO_ID_CRYPTO, vcrypto->config_size);
> + vcrypto->curr_queues = 1;
> +
> + for (i = 0; i < vcrypto->max_queues; i++) {
> + virtio_add_queue(vdev, 1024, virtio_crypto_handle_dataq);
> + }
> +
> + vcrypto->ctrl_vq = virtio_add_queue(vdev, 64, virtio_crypto_handle_ctrl);
> + if (!vcrypto->cryptodev->ready) {
> + vcrypto->status &= ~VIRTIO_CRYPTO_S_HW_READY;
> + } else {
> + vcrypto->status |= VIRTIO_CRYPTO_S_HW_READY;
> + }
> + register_savevm(dev, "virtio-crypto", -1, 1, virtio_crypto_save,
> + virtio_crypto_load, vcrypto);
Please use VMSTATE_VIRTIO_DEVICE() instead of calling register_savevm().
> +#ifdef DEBUG_VIRTIO_CRYPTO
> +#define DPRINTF(fmt, ...) \
> +do { printf("virtio_crypto: " fmt , ## __VA_ARGS__); } while (0)
> +#else
> +#define DPRINTF(fmt, ...) do { } while (0)
> +#endif
Please use tracing (see docs/tracing.txt) or if you really want to use
debug printfs then define DPRINTF() in a way that prevents bitrot:
#define DEBUG_VIRTIO_CRYPTO 0
#define DPRINTF(fmt, ...) \
do { \
if (DEBUG_VIRTIO_CRYPTO) { \
fprintf(stderr, "virtio_crypto: " fmt, ##__VA_ARGS__); \
} \
} while (0)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2016-10-04 9:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 8:25 [Qemu-devel] [PATCH v4 00/13] virtio-crypto: introduce framework and device emulation Gonglei
2016-09-28 8:25 ` [Qemu-devel] [PATCH v4 01/13] cryptodev: introduce cryptodev backend interface Gonglei
2016-10-03 16:10 ` Stefan Hajnoczi
2016-10-03 16:15 ` Daniel P. Berrange
2016-10-05 3:06 ` Gonglei (Arei)
2016-09-28 8:25 ` [Qemu-devel] [PATCH v4 02/13] cryptodev: add symmetric algorithm operation stuff Gonglei
2016-10-03 16:13 ` Stefan Hajnoczi
2016-10-05 3:07 ` [Qemu-devel] [virtio-dev] " Gonglei (Arei)
2016-09-28 8:25 ` [Qemu-devel] [PATCH v4 03/13] virtio-crypto: introduce virtio_crypto.h Gonglei
2016-10-03 16:14 ` Stefan Hajnoczi
2016-09-28 8:25 ` [Qemu-devel] [PATCH v4 04/13] cryptodev: introduce a new cryptodev backend Gonglei
2016-10-03 16:31 ` Stefan Hajnoczi
2016-10-05 3:19 ` Gonglei (Arei)
2016-10-05 12:53 ` Stefan Hajnoczi
2016-09-28 8:25 ` [Qemu-devel] [PATCH v4 05/13] virtio-crypto: add virtio crypto device emulation Gonglei
2016-10-04 9:38 ` Stefan Hajnoczi [this message]
2016-10-05 3:26 ` Gonglei (Arei)
2016-09-28 8:25 ` [Qemu-devel] [PATCH v4 06/13] virtio-crypto-pci: add virtio crypto pci support Gonglei
2016-09-28 8:25 ` [Qemu-devel] [PATCH v4 07/13] virtio-crypto: set capacity of algorithms supported Gonglei
2016-10-04 9:46 ` Stefan Hajnoczi
2016-10-05 3:30 ` [Qemu-devel] [virtio-dev] " Gonglei (Arei)
2016-10-05 12:55 ` Stefan Hajnoczi
2016-09-28 8:25 ` [Qemu-devel] [PATCH v4 08/13] virtio-crypto: add control queue handler Gonglei
2016-10-04 10:09 ` Stefan Hajnoczi
2016-10-05 3:38 ` Gonglei (Arei)
2016-09-28 8:25 ` [Qemu-devel] [PATCH v4 09/13] virtio-crypto: add data queue processing handler Gonglei
2016-09-28 8:25 ` [Qemu-devel] [PATCH v4 10/13] cryptodev: introduce an unified wrapper for crypto operation Gonglei
2016-09-28 8:25 ` [Qemu-devel] [PATCH v4 11/13] virtio-crypto: emulate virtio crypto as a legacy device by default Gonglei
2016-09-28 8:25 ` [Qemu-devel] [PATCH v4 12/13] virtio-crypto-test: add qtest case for virtio-crypto Gonglei
2016-09-28 8:25 ` [Qemu-devel] [PATCH v4 13/13] virtio-crypto: add myself as virtio-crypto and cryptodev backends maintainer Gonglei
2016-09-28 9:14 ` [Qemu-devel] [PATCH v4 00/13] virtio-crypto: introduce framework and device emulation no-reply
2016-09-28 9:18 ` Gonglei (Arei)
2016-10-03 12:02 ` Gonglei (Arei)
2016-10-04 10:13 ` Stefan Hajnoczi
2016-10-05 3:42 ` [Qemu-devel] [virtio-dev] " Gonglei (Arei)
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=20161004093820.GE4587@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=agraf@suse.de \
--cc=arei.gonglei@huawei.com \
--cc=berrange@redhat.com \
--cc=claudio.fontana@huawei.com \
--cc=hanweidong@huawei.com \
--cc=jianjay.zhou@huawei.com \
--cc=luonengjun@huawei.com \
--cc=mike.caraman@nxp.com \
--cc=mst@redhat.com \
--cc=nmorey@kalray.eu \
--cc=pbonzini@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=vincent.jardin@6wind.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=weidong.huang@huawei.com \
--cc=wu.wubin@huawei.com \
--cc=xin.zeng@intel.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).