DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Jankowski, Konrad" <konrad.jankowski@intel.com>,
	"Dai, Wei" <wei.dai@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/i40evf: regression fix - reenable interrupts in handler
Date: Wed, 28 Mar 2018 03:36:55 +0000	[thread overview]
Message-ID: <039ED4275CED7440929022BC67E7061153175394@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1518633151-29118-1-git-send-email-konrad.jankowski@intel.com>

Hi Jankowski:

> -----Original Message-----
> From: Jankowski, KonradX
> Sent: Thursday, February 15, 2018 2:33 AM
> To: Dai, Wei <wei.dai@intel.com>; Xing, Beilei <beilei.xing@intel.com>; Zhang,
> Qi Z <qi.z.zhang@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>;
> dev@dpdk.org
> Cc: Jankowski, KonradX <konradx.jankowski@intel.com>
> Subject: [PATCH] net/i40evf: regression fix - reenable interrupts in handler
> 
> Commit 66b8304f removed the rte_intr_enable() call from
> i40evf_dev_interrupt_handler() as a "bonus". On one of my systems this
> causes the AdminQ messages to stop beeing delivered to the VF. This results
> in unability to initialize and use the port. With this patch it works again.
> 
> System in question:
> Wind River OVP6 running kernel 3.10.58-ovp-rt58-WR6.0.0.13_preempt-rt
> 
> Signed-off-by: Konrad Jankowski <konrad.jankowski@intel.com>
> ---
>  drivers/net/i40e/i40e_ethdev_vf.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/net/i40e/i40e_ethdev_vf.c
> b/drivers/net/i40e/i40e_ethdev_vf.c
> index fd003fe..b927a35 100644
> --- a/drivers/net/i40e/i40e_ethdev_vf.c
> +++ b/drivers/net/i40e/i40e_ethdev_vf.c
> @@ -1404,6 +1404,7 @@ i40evf_dev_interrupt_handler(void *param)
> 
>  done:
>  	i40evf_enable_irq0(hw);
> +	rte_intr_enable(dev->intr_handle);'

Would you explain more about why the patch fix the issue?
Usually we will not accept a fix just because it work but not understand the root cause.

Regards
Qi

>  }
> 
>  static int
> --
> 2.5.5

  reply	other threads:[~2018-03-28  3:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 18:32 Konrad Jankowski
2018-03-28  3:36 ` Zhang, Qi Z [this message]
2018-04-04 17:12   ` Jankowski, Konrad
2018-04-06 15:47     ` Zhang, Helin
2018-04-06 15:52     ` Zhang, Helin
2018-04-10 13:26     ` Zhang, Qi Z
2018-04-10 14:06       ` Jankowski, Konrad

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=039ED4275CED7440929022BC67E7061153175394@SHSMSX103.ccr.corp.intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=konrad.jankowski@intel.com \
    --cc=wei.dai@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).