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 38C81C998 for ; Wed, 29 Apr 2015 20:24:06 +0200 (CEST) X-ASG-Debug-ID: 1430331844-03754d707e044a0001-TfluYd Received: from ssiexch-casht1.ssi.samsung.com ([105.128.134.172]) by mx2.ssi.samsung.com with ESMTP id OfXLBAaX72v1bJvK; Wed, 29 Apr 2015 11:24:04 -0700 (PDT) X-Barracuda-Envelope-From: james.liu@ssi.samsung.com X-Barracuda-Apparent-Source-IP: 105.128.134.172 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:24:04 -0700 From: "James (Fei) Liu-SSI" To: Stephen Hemminger 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: AQHQggz+EmLAGaiv6k+txz6zgkM47p1kThnQ Date: Wed, 29 Apr 2015 18:24:03 +0000 Message-ID: <99767EA2E27DD44DB4E9F9B9ACA458C03B30F3F1@SSIEXCH-MB3.ssi.samsung.com> References: <99767EA2E27DD44DB4E9F9B9ACA458C03B30F07F@SSIEXCH-MB3.ssi.samsung.com> <20150428164234.4a191ef4@urahara> In-Reply-To: <20150428164234.4a191ef4@urahara> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [105.128.13.180] MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Barracuda-Connect: UNKNOWN[105.128.134.172] X-Barracuda-Start-Time: 1430331844 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 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" 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:24:06 -0000 Do you have kernel version in your build environment that has ? [James] The kernel version is 3.17.2 Do you have iommu enabled on your target machine? [James] Yes Did you program the MSI-X correctly? [James] We can issues several admin commands successfully with interrupt en= abled , however. It is going to fail during IO traffic. By the way, we are = using DPDK for PCIe storage driver development. Have you guys ever use dpdk= for PCIe storage device? Thanks so much. Regards, James -----Original Message----- From: Stephen Hemminger [mailto:stephen@networkplumber.org] Sent: Tuesday, April 28, 2015 4:43 PM To: James (Fei) Liu-SSI Cc: dev@dpdk.org Subject: Re: [dpdk-dev] Issues of MSIx interrupt enable with user space dri= ver On Tue, 28 Apr 2015 21:57:31 +0000 "James (Fei) Liu-SSI" > wrote: > Hi All, > We are porting driver from kernel into user space driver with DPDK fo= r one of our devices. Polling thread works fine without any issue. However,= we want to switch from polling to interrupt based handler. While we enable= interrupt with VFIO MSIx, we always get below errors after issuing one com= mand: > > [ 465.464186] dmar: DRHD: handling fault status reg 2 [ 465.464194] > dmar: INTR-REMAP: Request device [[02:00.0] fault index 27 [ > 465.464194] INTR-REMAP:[fault reason 34] Present field in the IRTE > entry is clear > > 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 > > > > Is there anyone in the forum who worked on the interrupt handler to share= with us about your comments? thanks for your help in advance. Do you have kernel version in your build environment that has ? Do you have iommu enabled on your target machine? Did you program the MSI-X correctly?