DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: abhimanyu.saini@xilinx.com, dev@dpdk.org
Cc: chenbo.xia@intel.com, andrew.rybchenko@oktetlabs.ru,
	stable@dpdk.org, Abhimanyu Saini <absaini@amd.com>,
	Vijay Kumar Srivastava <vsrivast@xilinx.com>
Subject: Re: [PATCH v2] vdpa/sfc: handle sync issue between qemu and vhost-user
Date: Fri, 1 Jul 2022 15:58:41 +0200	[thread overview]
Message-ID: <332cdf10-64dc-def2-194d-3212244bbd7d@redhat.com> (raw)
In-Reply-To: <20220628052926.21319-1-asaini@xilinx.com>



On 6/28/22 07:29, abhimanyu.saini@xilinx.com wrote:
> From: Abhimanyu Saini <absaini@amd.com>
> 
> When DPDK app is running in the VF, it sometimes rings the doorbell
> before dev_config has had a chance to complete and hence it misses
> the event. As workaround, ring the doorbell when vDPA reports the
> notify_area to QEMU.
> 
> Fixes: 630be406dcbf ("vdpa/sfc: get queue notify area info")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Vijay Kumar Srivastava <vsrivast@xilinx.com>
> Signed-off-by: Abhimanyu Saini <absaini@amd.com>
> ---
> v1:
> * Update the commit id that this patch fixes
> 
>   drivers/vdpa/sfc/sfc_vdpa_ops.c | 14 ++++++++++++++
>   1 file changed, 14 insertions(+)
> 

Applied to dpdk-next-virtio/main.

Thanks,
Maxime


      parent reply	other threads:[~2022-07-01 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27  8:49 [PATCH] " abhimanyu.saini
2022-06-27 15:03 ` Andrew Rybchenko
2022-06-28  5:29 ` [PATCH v2] " abhimanyu.saini
2022-06-28  9:01   ` Andrew Rybchenko
2022-06-30 12:56   ` Maxime Coquelin
2022-07-01 13:58   ` Maxime Coquelin [this message]

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=332cdf10-64dc-def2-194d-3212244bbd7d@redhat.com \
    --to=maxime.coquelin@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=stable@dpdk.org \
    --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).