From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org, maxime.coquelin@redhat.com, david.marchand@redhat.com
Cc: Thomas Monjalon <thomas@monjalon.net>,
Chenbo Xia <chenbo.xia@intel.com>,
Kevin Traynor <ktraynor@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] vhost: fix wrong IOTLB initialization
Date: Thu, 13 May 2021 14:10:04 +0100 [thread overview]
Message-ID: <16af9049-f7b5-f4f8-a6f8-6897e904591f@intel.com> (raw)
In-Reply-To: <20210513122826.49910-1-chenbo.xia@intel.com>
On 5/13/2021 1:28 PM, Chenbo Xia wrote:
> This patch fixes an issue of application crash because of vhost iotlb
> not initialized when virtio has multiqueue enabled.
>
> iotlb messages will be sent when some queues are not enabled. If we
> initialize iotlb in vhost_user_set_vring_num, it could happen that
> iotlb update comes when iotlb pool of disabled queues are not
> initialized.
>
> Fixes: 968bbc7e2e50 ("vhost: avoid IOTLB mempool allocation while IOMMU disabled")
>
> Signed-off-by: Chenbo Xia <chenbo.xia@intel.com>
Hi Maxime, David,
Can Red Hat QA verify this patch please?
Btw, the issue is for defect:
https://bugs.dpdk.org/show_bug.cgi?id=703
next prev parent reply other threads:[~2021-05-13 13:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 12:28 [dpdk-dev] [PATCH] vhost: fix wrong IOTLB initialization Chenbo Xia
2021-05-13 13:10 ` Ferruh Yigit [this message]
2021-05-13 13:26 ` Kevin Traynor
2021-05-13 14:11 ` David Marchand
2021-05-13 14:38 ` Kevin Traynor
2021-05-13 15:03 ` Ferruh Yigit
2021-05-14 8:18 ` David Marchand
2021-05-14 9:09 ` Ferruh Yigit
2021-05-14 9:25 ` Thomas Monjalon
2021-05-14 8:16 ` David Marchand
2021-05-17 12:46 ` Xia, Chenbo
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=16af9049-f7b5-f4f8-a6f8-6897e904591f@intel.com \
--to=ferruh.yigit@intel.com \
--cc=chenbo.xia@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=thomas@monjalon.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.