From: David Marchand <david.marchand@redhat.com>
To: abhimanyu.saini@xilinx.com, vsrivast@xilinx.com
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>, dev <dev@dpdk.org>,
"Xia, Chenbo" <chenbo.xia@intel.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Abhimanyu Saini <absaini@amd.com>
Subject: Re: [PATCH] vdpa/sfc: resolve race between libvhost and dev_conf
Date: Fri, 8 Jul 2022 10:13:10 +0200 [thread overview]
Message-ID: <CAJFAV8xkwg0f67yuVjtkNYhESjRrsjW8RJyfdi2wrv+vSUZujA@mail.gmail.com> (raw)
In-Reply-To: <04f993c8-24dc-aa76-9f02-faa4e6a25855@redhat.com>
Hello Abhimanyu, Vijay,
On Thu, Jul 7, 2022 at 2:38 PM Maxime Coquelin
<maxime.coquelin@redhat.com> wrote:
> On 7/6/22 11:24, abhimanyu.saini@xilinx.com wrote:
> > From: Abhimanyu Saini <absaini@amd.com>
> >
> > libvhost calls dev_conf() before prosessing the
> > VHOST_USER_SET_VRING_CALL message for the last VQ. So
> > this message is processed after dev_conf() returns.
> >
> > However, the dev_conf() function spawns a thread to set
> > rte_vhost_host_notifier_ctrl() before returning control to
> > libvhost. This parallel thread in turn invokes get_notify_area().
> > To get the notify_area, the vdpa driver needs to query the HW and
> > for this query it needs an enabled VQ.
> >
> > But at the same time libvhost is processing the last
> > VHOST_USER_SET_VRING_CALL, and to do that it disables the last VQ.
> >
> > Hence there is a race b/w the libvhost and the vdpa driver.
> >
> > To resolve this race condition, query the HW and cache notify_area
> > inside dev_conf() instead of doing it the parallel thread.
> >
> > Signed-off-by: Abhimanyu Saini <absaini@amd.com>
> > ---
> > drivers/vdpa/sfc/sfc_vdpa_ops.c | 36 ++++++++++++++++++------------------
> > drivers/vdpa/sfc/sfc_vdpa_ops.h | 1 +
> > 2 files changed, 19 insertions(+), 18 deletions(-)
> >
>
> During today's Release status meeting, Andrew mentioned that this patch
> has been for a log time already in your internal tree.
>
> So it gives a bit of confidence in taking it in -rc4.
- But it is neither reviewed, nor acked by the driver maintainer.
Vijay, as this driver maintainer, your opinion matters.
We are in rc4 stage and we merge only critical fixes now.
There won't be much time to test this fix once merged (and I am not
talking about fixing a regression).
Are you confident with this fix? is it required for the 22.07 release?
If we don't get an answer, the safer is to let those fixes slip to a
next release.
- Besides, I see there is a new fix for some sfc driver.
https://patches.dpdk.org/project/dpdk/patch/20220708073702.29391-1-asaini@xilinx.com/
The same questions will be asked.
--
David Marchand
next prev parent reply other threads:[~2022-07-08 8:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 9:24 abhimanyu.saini
2022-07-06 12:32 ` Maxime Coquelin
2022-07-07 12:38 ` Maxime Coquelin
2022-07-08 8:13 ` David Marchand [this message]
2022-07-08 9:02 ` Srivastava, Vijay
2022-07-08 9:23 ` Maxime Coquelin
2022-07-08 9:25 ` Maxime Coquelin
2022-07-08 10:25 ` Saini, Abhimanyu
2022-07-08 10:39 ` 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=CAJFAV8xkwg0f67yuVjtkNYhESjRrsjW8RJyfdi2wrv+vSUZujA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=abhimanyu.saini@xilinx.com \
--cc=absaini@amd.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=vsrivast@xilinx.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).