From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Abhishek Maheshwari <abhishek.maheshwari@intel.com>,
xiao.w.wang@intel.com, chenbo.xia@intel.com
Cc: dev@dpdk.org, purna.chandra.mandal@intel.com
Subject: Re: [PATCH] vdpa/ifc/base: wait for queue disable before saving q-state
Date: Wed, 26 Oct 2022 07:32:26 +0200 [thread overview]
Message-ID: <c8e5bbb2-72c7-03dd-5996-4b4cdaa2d449@redhat.com> (raw)
In-Reply-To: <20221025075149.1713006-1-abhishek.maheshwari@intel.com>
Hi Abhishek,
On 10/25/22 09:51, Abhishek Maheshwari wrote:
> Some ifc hardware require synchronization between disabling a queue and
> saving queue-state from LM registers. When queue is disabled from vDPA
> driver, ifc device stops executing new virtio-cmds and then updates LM
> registers with used/avail index. Before saving the queue-state, vDPA
> driver should wait until the queue is disabled from backend.
I think it should be considered a fix, and so requires a Fixes tag and
stable@dpdk.org to be cc'ed.
> Signed-off-by: Abhishek Maheshwari <abhishek.maheshwari@intel.com>
> ---
> drivers/vdpa/ifc/base/ifcvf.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/drivers/vdpa/ifc/base/ifcvf.c b/drivers/vdpa/ifc/base/ifcvf.c
> index f1e1474447..76690c1f55 100644
> --- a/drivers/vdpa/ifc/base/ifcvf.c
> +++ b/drivers/vdpa/ifc/base/ifcvf.c
> @@ -257,6 +257,7 @@ ifcvf_hw_disable(struct ifcvf_hw *hw)
> u32 i;
> struct ifcvf_pci_common_cfg *cfg;
> u32 ring_state;
> + int q_disable_tries;
>
> cfg = hw->common_cfg;
> if (!cfg) {
> @@ -275,6 +276,20 @@ ifcvf_hw_disable(struct ifcvf_hw *hw)
> continue;
> }
>
> + /* Some ifc hardware require synchronization between disabling a queue
> + * and saving queue-state from LM registers. When queue is disabled from
> + * vDPA driver, ifc device stops executing new virtio-cmds and then
> + * updates LM registers with used/avail index. Before saving the
> + * queue-state, vDPA driver waits until the queue is disabled from
> + * backend.
> + */
> + q_disable_tries = 10;
> + while (q_disable_tries-- && IFCVF_READ_REG16(&cfg->queue_enable))
> + msec_delay(10);
> +
> + if (IFCVF_READ_REG16(&cfg->queue_enable))
> + WARNINGOUT("Failed Q disable: %d. saved state is invalid\n", i);
Maybe checking q_disable_tries > 0 is enough here.
Also, should we really continue the disablement if synchronization
failed?
> +
> if (hw->device_type == IFCVF_BLK)
> ring_state = *(u32 *)(hw->lm_cfg +
> IFCVF_LM_RING_STATE_OFFSET +
next prev parent reply other threads:[~2022-10-26 5:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 7:51 Abhishek Maheshwari
2022-10-26 5:32 ` Maxime Coquelin [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-25 7:23 Abhishek Maheshwari
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=c8e5bbb2-72c7-03dd-5996-4b4cdaa2d449@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=abhishek.maheshwari@intel.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=purna.chandra.mandal@intel.com \
--cc=xiao.w.wang@intel.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).