From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Patil, Harish" <Harish.Patil@cavium.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
Gregory Etelson <gregory@weka.io>
Cc: "Thotton, Shijith" <Shijith.Thotton@cavium.com>,
"Tan, Jianfeng" <jianfeng.tan@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v2 2/2] igb_uio: fix interrupt enablement after FLR in VM
Date: Tue, 17 Oct 2017 01:37:06 +0000 [thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F810E97950@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <D60AAB9C.16B790%Harish.Patil@cavium.com>
> -----Original Message-----
> From: Patil, Harish [mailto:Harish.Patil@cavium.com]
> Sent: Tuesday, October 17, 2017 9:32 AM
> To: Yigit, Ferruh <ferruh.yigit@intel.com>; Gregory Etelson <gregory@weka.io>
> Cc: Thotton, Shijith <Shijith.Thotton@cavium.com>; Wu, Jingjing
> <jingjing.wu@intel.com>; Tan, Jianfeng <jianfeng.tan@intel.com>; Xing, Beilei
> <beilei.xing@intel.com>; dev@dpdk.org; stable@dpdk.org
> Subject: Re: [PATCH v2 2/2] igb_uio: fix interrupt enablement after FLR in VM
>
>
>
> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> Date: Monday, October 16, 2017 at 4:52 PM
> To: Harish Patil <Harish.Patil@cavium.com>, Gregory Etelson
> <gregory@weka.io>
> Cc: "Thotton, Shijith" <Shijith.Thotton@cavium.com>, "Wu, Jingjing"
> <jingjing.wu@intel.com>, "Tan, Jianfeng" <jianfeng.tan@intel.com>, "Xing,
> Beilei" <beilei.xing@intel.com>, "dev@dpdk.org" <dev@dpdk.org>,
> "stable@dpdk.org" <stable@dpdk.org>
> Subject: Re: [PATCH v2 2/2] igb_uio: fix interrupt enablement after FLR in
> VM
>
> >On 10/16/2017 3:49 PM, Patil, Harish wrote:
> >> From: Gregory Etelson <gregory@weka.io <mailto:gregory@weka.io>>
> >> Date: Saturday, October 14, 2017 at 8:10 PM
> >> To: Ferruh Yigit <ferruh.yigit@intel.com
> >><mailto:ferruh.yigit@intel.com>>
> >> Cc: "Thotton, Shijith" <Shijith.Thotton@cavium.com
> >> <mailto:Shijith.Thotton@cavium.com>>, "Wu, Jingjing"
> >> <jingjing.wu@intel.com <mailto:jingjing.wu@intel.com>>, Harish Patil
> >> <Harish.Patil@cavium.com <mailto:Harish.Patil@cavium.com>>, "Tan,
> >> Jianfeng" <jianfeng.tan@intel.com <mailto:jianfeng.tan@intel.com>>,
> >> "Xing, Beilei" <beilei.xing@intel.com <mailto:beilei.xing@intel.com>>,
> >> "dev@dpdk.org <mailto:dev@dpdk.org>" <dev@dpdk.org
> >> <mailto:dev@dpdk.org>>, "stable@dpdk.org <mailto:stable@dpdk.org>"
> >> <stable@dpdk.org <mailto:stable@dpdk.org>>
> >> Subject: Re: [PATCH v2 2/2] igb_uio: fix interrupt enablement after FLR
> >> in VM
> >>
> >> I'll start to build setup environment this week.
> >> Regards,
> >> Gregory
> >>
> >> On Sat, Oct 14, 2017 at 12:11 AM, Ferruh Yigit
> >> <ferruh.yigit@intel.com <mailto:ferruh.yigit@intel.com>> wrote:
> >>
> >> On 10/13/2017 9:12 AM, Shijith Thotton wrote:
> >> <...>
> >>
> >> > Hi Jingjing,
> >> >
> >> > This patch perfectly meets requirements as both resets are
> >>retained
> >> > (open and release). Tested it with LiquidIO NIC and it works
> >>fine.
> >> > I can see MSI-X re-enabled on each run with new patch.
> >> >
> >> > Gregory, Harish,
> >> > Please verify the patch on your setup if possible.
> >>
> >> Hi Gregory, Harish,
> >>
> >> Did you able to test this patch?
> >>
> >> Thanks,
> >> ferruh
> >>
> >> >
> >> > Thanks,
> >> > Shijith
> >> >
> >>
> >>
> >>
> >> Hi all,
> >> Its not working for qede VF device.
> >> So request to back out all igb_uio changes related to the patch:
> >> igb_uio: issue FLR during open and release of device file
> >
> >Hi Harish,
> >
> >Thanks for testing. We tried.
> >
> >For this release, agreed to revert back to original state, I will send a
> >patch soon.
> >
> >
> >But for further investigation in next release, can you please share more
> >details? What is not working exactly, what is your setup, any
> >kernel/DPDK log to share?
> >
> >Thanks,
> >Ferruh
>
> Okay, sure.
> thanks.
> >
> >>
> >> Thanks,
> >> Harish
> >>
> >
Can you share more details? Only doesn't work in vfio pci passthrough?
next prev parent reply other threads:[~2017-10-17 1:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 20:31 [dpdk-stable] [PATCH 1/2] net/i40e: fix VF initialization error Jingjing Wu
2017-10-09 20:31 ` [dpdk-stable] [PATCH 2/2] igb_uio: fix interrupt enablement after FLR in VM Jingjing Wu
2017-10-09 22:09 ` [dpdk-stable] [PATCH v2 " Jingjing Wu
2017-10-12 5:43 ` Wu, Jingjing
2017-10-13 8:12 ` Shijith Thotton
2017-10-13 21:11 ` Ferruh Yigit
2017-10-13 21:21 ` [dpdk-stable] [dpdk-dev] " Patil, Harish
2017-10-15 3:10 ` [dpdk-stable] " Gregory Etelson
2017-10-16 22:49 ` Patil, Harish
2017-10-16 23:52 ` Ferruh Yigit
2017-10-17 1:32 ` Patil, Harish
2017-10-17 1:37 ` Wu, Jingjing [this message]
2017-10-13 20:54 ` [dpdk-stable] [PATCH " Ferruh Yigit
2017-10-13 21:15 ` Thomas Monjalon
2017-10-13 21:38 ` Ferruh Yigit
2017-10-09 22:08 ` [dpdk-stable] [PATCH v2 1/2] net/i40e: fix VF initialization error Jingjing Wu
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=9BB6961774997848B5B42BEC655768F810E97950@SHSMSX103.ccr.corp.intel.com \
--to=jingjing.wu@intel.com \
--cc=Harish.Patil@cavium.com \
--cc=Shijith.Thotton@cavium.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gregory@weka.io \
--cc=jianfeng.tan@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).