From: Fan Zhang <roy.fan.zhang@intel.com>
To: stable@dpdk.org
Cc: maxime.coquelin@redhat.com, ktraynor@redhat.com,
Fan Zhang <roy.fan.zhang@intel.com>
Subject: [dpdk-stable] [PATCH 18.11] vhost/crypto: fix feature negotiation
Date: Thu, 3 Dec 2020 16:50:20 +0000 [thread overview]
Message-ID: <20201203165020.1396969-1-roy.fan.zhang@intel.com> (raw)
[ upstream commit ea1b835a0e74d80915e2e717f20418e2c9f948a2 ]
This patch fixes the incorrect vhost crypto device feature
flags.
Fixes: 939066d96563 ("vhost/crypto: add public function implementation")
Cc: roy.fan.zhang@intel.com
Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
---
lib/librte_vhost/vhost_crypto.c | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/lib/librte_vhost/vhost_crypto.c b/lib/librte_vhost/vhost_crypto.c
index dfbac66f05..849cfa0889 100644
--- a/lib/librte_vhost/vhost_crypto.c
+++ b/lib/librte_vhost/vhost_crypto.c
@@ -35,13 +35,12 @@
#define VC_LOG_DBG(fmt, args...)
#endif
-#define VIRTIO_CRYPTO_FEATURES ((1 << VIRTIO_F_NOTIFY_ON_EMPTY) | \
- (1 << VIRTIO_RING_F_INDIRECT_DESC) | \
- (1 << VIRTIO_RING_F_EVENT_IDX) | \
- (1 << VIRTIO_CRYPTO_SERVICE_CIPHER) | \
- (1 << VIRTIO_CRYPTO_SERVICE_MAC) | \
- (1 << VIRTIO_NET_F_CTRL_VQ) | \
- (1 << VHOST_USER_PROTOCOL_F_CONFIG))
+#define VIRTIO_CRYPTO_FEATURES ((1ULL << VIRTIO_F_NOTIFY_ON_EMPTY) | \
+ (1ULL << VIRTIO_RING_F_INDIRECT_DESC) | \
+ (1ULL << VIRTIO_RING_F_EVENT_IDX) | \
+ (1ULL << VIRTIO_NET_F_CTRL_VQ) | \
+ (1ULL << VIRTIO_F_VERSION_1) | \
+ (1ULL << VHOST_USER_F_PROTOCOL_FEATURES))
#define IOVA_TO_VVA(t, r, a, l, p) \
((t)(uintptr_t)vhost_iova_to_vva(r->dev, r->vq, a, l, p))
--
2.25.1
next reply other threads:[~2020-12-03 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 16:50 Fan Zhang [this message]
2020-12-04 17:03 ` Kevin Traynor
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=20201203165020.1396969-1-roy.fan.zhang@intel.com \
--to=roy.fan.zhang@intel.com \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).