From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Dai, Wei" <wei.dai@intel.com>, "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Wang, Liang-min" <liang-min.wang@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] net/ixgbe: fix mailbox interrupt handler
Date: Thu, 11 Jan 2018 08:07:59 +0000 [thread overview]
Message-ID: <039ED4275CED7440929022BC67E706115312B29A@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <49759EB36A64CF4892C1AFEC9231E8D65156D94A@PGSMSX112.gar.corp.intel.com>
> -----Original Message-----
> From: Dai, Wei
> Sent: Thursday, December 28, 2017 12:39 PM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Lu, Wenzhuo
> <wenzhuo.lu@intel.com>
> Cc: dev@dpdk.org; Wang, Liang-min <liang-min.wang@intel.com>;
> stable@dpdk.org
> Subject: RE: [PATCH 1/2] net/ixgbe: fix mailbox interrupt handler
>
> According to step 7 & 8 in Table 7-74 PF-to-VF Messaging Flow in 82599
> datasheet, The calling of ixgbe_read_mbx( ) can be replaced by following lines
> to avoid touching ->mbx.v2p_mailbox, IXGBE_WRITE_REG(hw,
> IXGBE_VFMAILBOX, IXGBE_VFMAILBOX_ACK);
Thanks for the suggestion.
I think the patch try to keep things unchanged when a PF reset happen, but it is not going to cover the case that PF reset interrupt and a foreground VF to PF request happen simultaneously which is an knowing issue
Your suggestion may help on that, but it is not a complete fix. I think it will be better to have a separate patch that focus on it.
Regards
Qi
>
> > -----Original Message-----
> > From: Zhang, Qi Z
> > Sent: Thursday, December 28, 2017 4:22 AM
> > To: Lu, Wenzhuo <wenzhuo.lu@intel.com>
> > Cc: dev@dpdk.org; Dai, Wei <wei.dai@intel.com>; Wang, Liang-min
> > <liang-min.wang@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>;
> > stable@dpdk.org
> > Subject: [PATCH 1/2] net/ixgbe: fix mailbox interrupt handler
> >
> > Mailbox interrupt handler only take care of PF reset notification, for
> > other message ixgbe_read_mbx should not be called since it get chance
> > to break the foreground VF to PF communication.
> > This can be simply repeated by
> > testpmd>rx_vlan rm all 0
> >
> > Fixes: 77234603fba0 ("net/ixgbe: support VF mailbox interrupt for link
> > up/down")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
> > ---
> > drivers/net/ixgbe/ixgbe_ethdev.c | 10 +++++++---
> > 1 file changed, 7 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/net/ixgbe/ixgbe_ethdev.c
> > b/drivers/net/ixgbe/ixgbe_ethdev.c
> > index ff19a56..02121f4 100644
> > --- a/drivers/net/ixgbe/ixgbe_ethdev.c
> > +++ b/drivers/net/ixgbe/ixgbe_ethdev.c
> > @@ -8165,13 +8165,17 @@ static void ixgbevf_mbx_process(struct
> > rte_eth_dev *dev)
> > struct ixgbe_hw *hw =
> > IXGBE_DEV_PRIVATE_TO_HW(dev->data->dev_private);
> > u32 in_msg = 0;
> >
> > - if (ixgbe_read_mbx(hw, &in_msg, 1, 0))
> > - return;
> > + /* peek the message first */
> > + in_msg = IXGBE_READ_REG(hw, IXGBE_VFMBMEM);
> >
> > /* PF reset VF event */
> > - if (in_msg == IXGBE_PF_CONTROL_MSG)
> > + if (in_msg == IXGBE_PF_CONTROL_MSG) {
> > + /* dummy mbx read to ack pf */
> > + if (ixgbe_read_mbx(hw, &in_msg, 1, 0))
> > + return;
> > _rte_eth_dev_callback_process(dev,
> > RTE_ETH_EVENT_INTR_RESET,
> > NULL, NULL);
> > + }
> > }
> >
> > static int
> > --
> > 2.7.4
next prev parent reply other threads:[~2018-01-11 8:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-27 20:22 Qi Zhang
2017-12-27 20:22 ` [dpdk-dev] [PATCH 2/2] net/e1000: " Qi Zhang
2018-01-12 2:32 ` Dai, Wei
2018-01-13 16:14 ` Zhang, Helin
2017-12-28 4:38 ` [dpdk-dev] [PATCH 1/2] net/ixgbe: " Dai, Wei
2018-01-11 8:07 ` Zhang, Qi Z [this message]
2018-01-12 2:29 ` Dai, Wei
2018-01-12 2:30 ` Dai, Wei
2018-01-13 6:27 ` Zhang, Helin
2018-01-13 16:13 ` Zhang, Helin
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=039ED4275CED7440929022BC67E706115312B29A@SHSMSX103.ccr.corp.intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=liang-min.wang@intel.com \
--cc=stable@dpdk.org \
--cc=wei.dai@intel.com \
--cc=wenzhuo.lu@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).