From: "Xia, Chenbo" <chenbo.xia@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: RE: [PATCH v2 1/2] vduse: fix missing event index features
Date: Thu, 6 Jul 2023 08:38:59 +0000 [thread overview]
Message-ID: <SN6PR11MB3504003938E7FCAA145282D99C2CA@SN6PR11MB3504.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230706081223.151832-2-maxime.coquelin@redhat.com>
> -----Original Message-----
> From: Maxime Coquelin <maxime.coquelin@redhat.com>
> Sent: Thursday, July 6, 2023 4:12 PM
> To: dev@dpdk.org; Xia, Chenbo <chenbo.xia@intel.com>;
> david.marchand@redhat.com
> Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
> Subject: [PATCH v2 1/2] vduse: fix missing event index features
>
> This features was mistakenly removed, add it back.
>
> Fixes: 0adb8eccc6a6 ("vhost: add VDUSE device creation and destruction")
>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> ---
> lib/vhost/vduse.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/lib/vhost/vduse.c b/lib/vhost/vduse.c
> index a509daf80c..b9514e6c29 100644
> --- a/lib/vhost/vduse.c
> +++ b/lib/vhost/vduse.c
> @@ -41,6 +41,7 @@
> (1ULL << VIRTIO_NET_F_GUEST_UFO) | \
> (1ULL << VIRTIO_NET_F_GUEST_ECN) | \
> (1ULL << VIRTIO_RING_F_INDIRECT_DESC) | \
> + (1ULL << VIRTIO_RING_F_EVENT_IDX) | \
> (1ULL << VIRTIO_F_IN_ORDER) | \
> (1ULL << VIRTIO_F_IOMMU_PLATFORM) | \
> (1ULL << VIRTIO_NET_F_CTRL_VQ) | \
> --
> 2.41.0
Reviewed-by: Chenbo Xia <chenbo.xia@intel.com>
next prev parent reply other threads:[~2023-07-06 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 8:12 [PATCH v2 0/2] VDUSE fixes for v23.07 Maxime Coquelin
2023-07-06 8:12 ` [PATCH v2 1/2] vduse: fix missing event index features Maxime Coquelin
2023-07-06 8:38 ` Xia, Chenbo [this message]
2023-07-06 8:12 ` [PATCH v2 2/2] vhost: fix vduse features negotiation Maxime Coquelin
2023-07-06 8:39 ` Xia, Chenbo
2023-07-06 8:16 ` [PATCH v2 0/2] VDUSE fixes for v23.07 David Marchand
2023-07-06 9:06 ` Maxime Coquelin
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=SN6PR11MB3504003938E7FCAA145282D99C2CA@SN6PR11MB3504.namprd11.prod.outlook.com \
--to=chenbo.xia@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@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).