From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.ssi.samsung.com (mx2.ssi.samsung.com [207.140.43.206]) by dpdk.org (Postfix) with ESMTP id C5F17C9AA for ; Wed, 29 Apr 2015 20:25:36 +0200 (CEST) X-ASG-Debug-ID: 1430331935-03754d707e04500001-TfluYd Received: from ssiexch-casht1.ssi.samsung.com ([105.128.134.61]) by mx2.ssi.samsung.com with ESMTP id p0EPSySjDyxBcS6t; Wed, 29 Apr 2015 11:25:35 -0700 (PDT) X-Barracuda-Envelope-From: james.liu@ssi.samsung.com X-Barracuda-Apparent-Source-IP: 105.128.134.61 X-ASG-Whitelist: Client Received: from SSIEXCH-MB3.ssi.samsung.com ([fe80::9dae:55f:7824:a7d1]) by ssiexch-casht1.ssi.samsung.com ([fe80::44fd:e72a:215c:8df1%11]) with mapi id 14.03.0123.003; Wed, 29 Apr 2015 11:25:35 -0700 From: "James (Fei) Liu-SSI" To: "Zhou, Danny" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] Issues of MSIx interrupt enable with user space driver X-ASG-Orig-Subj: RE: [dpdk-dev] Issues of MSIx interrupt enable with user space driver Thread-Index: AQHQggpzghuUOYi9pUSZGIfnejvk6Z1kT1aQ Date: Wed, 29 Apr 2015 18:25:34 +0000 Message-ID: <99767EA2E27DD44DB4E9F9B9ACA458C03B30F401@SSIEXCH-MB3.ssi.samsung.com> References: <99767EA2E27DD44DB4E9F9B9ACA458C03B30F07F@SSIEXCH-MB3.ssi.samsung.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [105.128.13.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Barracuda-Connect: UNKNOWN[105.128.134.61] X-Barracuda-Start-Time: 1430331935 X-Barracuda-URL: http://mx1.ssi.samsung.com:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at ssi.samsung.com X-Barracuda-BRTS-Status: 1 Subject: Re: [dpdk-dev] Issues of MSIx interrupt enable with user space driver X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Apr 2015 18:25:37 -0000 Hi Danny, Thanks a lot for your promptly answer. I am going to check your patch so= on. In the mean time, Have you guys ever try DPDK with PCIe storage device? Regards, James -----Original Message----- From: Zhou, Danny [mailto:danny.zhou@intel.com]=20 Sent: Tuesday, April 28, 2015 4:19 PM To: James (Fei) Liu-SSI; dev@dpdk.org Cc: Liang, Cunming Subject: RE: [dpdk-dev] Issues of MSIx interrupt enable with user space dri= ver The V6 "Interrupt PMD" patch has been sent out to DPDK.org 2 months ago, an= d V7 is under development with changes to include more generic APIs that co= uld support all kinds of interrupts (e.g. HW Rx interrupt and SW ring inter= rupt).=20 Stay tuned.=20 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of James (Fei)=20 > Liu-SSI > Sent: Wednesday, April 29, 2015 5:58 AM > To: dev@dpdk.org > Subject: [dpdk-dev] Issues of MSIx interrupt enable with user space=20 > driver >=20 > Hi All, > We are porting driver from kernel into user space driver with DPDK=20 > for one of our devices. Polling thread works fine without any issue.=20 > However, we want to switch from polling to interrupt based handler. While= we enable interrupt with VFIO MSIx, we always get below errors after issui= ng one command: >=20 > [ 465.464186] dmar: DRHD: handling fault status reg 2 [ 465.464194]=20 > dmar: INTR-REMAP: Request device [[02:00.0] fault index 27 [ =20 > 465.464194] INTR-REMAP:[fault reason 34] Present field in the IRTE=20 > entry is clear >=20 > Here are steps we follow to enable interrupt: > 1. --vfio-intr msix was passed in as parameter for rte_eal_init > 2. rte_intr_enable was called during the drive probe stage. > 3. rte_intr_callback_register was called after interrupt was enabled >=20 >=20 >=20 > Is there anyone in the forum who worked on the interrupt handler to=20 > share with us about your comments? thanks for your help in advance. >=20 > Regards, > James >=20