patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Guo, Junfeng" <junfeng.guo@intel.com>
To: "Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v3] raw/ntb: clear all valid DB bits when DB init
Date: Thu, 10 Feb 2022 07:08:11 +0000	[thread overview]
Message-ID: <DM6PR11MB37238791D8C5C9E37321B890E72F9@DM6PR11MB3723.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MW3PR11MB4587D18F403777A309A98509E32F9@MW3PR11MB4587.namprd11.prod.outlook.com>



> -----Original Message-----
> From: Wu, Jingjing <jingjing.wu@intel.com>
> Sent: Thursday, February 10, 2022 14:51
> To: Guo, Junfeng <junfeng.guo@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org
> Subject: RE: [PATCH v3] raw/ntb: clear all valid DB bits when DB init
> 
> 
> 
> > -----Original Message-----
> > From: Guo, Junfeng <junfeng.guo@intel.com>
> > Sent: Wednesday, February 9, 2022 12:47 PM
> > To: Wu, Jingjing <jingjing.wu@intel.com>
> > Cc: dev@dpdk.org; stable@dpdk.org; Guo, Junfeng
> <junfeng.guo@intel.com>
> > Subject: [PATCH v3] raw/ntb: clear all valid DB bits when DB init
> >
> > Before registering the doorbell interrupt handler callback function,
> > all the valid doorbell bits within the NTB private data struct should
> > be cleared to avoid the confusion of the handshake timing sequence
> > diagram when setting up the NTB connection in back-to-back mode.
> >
> > Fixes: 62012a76811e ("raw/ntb: add handshake process")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
> > ---
> >  drivers/raw/ntb/ntb.c | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> Better to add changes compared to previous version, which would help
> reviewers.

Sure, I'll add the version change commit in the coming version. Thanks!

> 
> > diff --git a/drivers/raw/ntb/ntb.c b/drivers/raw/ntb/ntb.c
> > index 46ac02e5ab..cc611dfbb9 100644
> > --- a/drivers/raw/ntb/ntb.c
> > +++ b/drivers/raw/ntb/ntb.c
> > @@ -1398,6 +1398,8 @@ ntb_init_hw(struct rte_rawdev *dev, struct
> rte_pci_device
> > *pci_dev)
> >
> >  	/* Init doorbell. */
> >  	hw->db_valid_mask = RTE_LEN2MASK(hw->db_cnt, uint64_t);
> > +	/* Clear all valid doorbell bits before registering intr handler */
> > +	(*hw->ntb_ops->db_clear)(dev, hw->db_valid_mask);
> 
> Check if hw->ntb_ops->db_clear is NULL before call it.

OK, will add it in the coming version. Thanks for review! 

> 
> >
> >  	intr_handle = pci_dev->intr_handle;
> >  	/* Register callback func to eal lib */
> > --
> > 2.25.1


  reply	other threads:[~2022-02-10  7:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09  4:35 [PATCH] " Junfeng Guo
2022-02-09  4:39 ` [PATCH v2] " Junfeng Guo
2022-02-09  4:47   ` [PATCH v3] " Junfeng Guo
2022-02-10  6:50     ` Wu, Jingjing
2022-02-10  7:08       ` Guo, Junfeng [this message]
2022-02-10  7:06     ` [PATCH v4] " Junfeng Guo
2022-02-10  7:09       ` Wu, Jingjing
2022-02-13 11:26         ` Thomas Monjalon

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=DM6PR11MB37238791D8C5C9E37321B890E72F9@DM6PR11MB3723.namprd11.prod.outlook.com \
    --to=junfeng.guo@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=stable@dpdk.org \
    /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).