From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 03383C690 for ; Wed, 29 Apr 2015 01:23:02 +0200 (CEST) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga103.jf.intel.com with ESMTP; 28 Apr 2015 16:19:23 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,667,1422950400"; d="scan'208";a="563347763" Received: from pgsmsx103.gar.corp.intel.com ([10.221.44.82]) by orsmga003.jf.intel.com with ESMTP; 28 Apr 2015 16:19:21 -0700 Received: from shsmsx103.ccr.corp.intel.com (10.239.110.14) by PGSMSX103.gar.corp.intel.com (10.221.44.82) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 29 Apr 2015 07:19:20 +0800 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.162]) by SHSMSX103.ccr.corp.intel.com ([10.239.4.69]) with mapi id 14.03.0224.002; Wed, 29 Apr 2015 07:19:19 +0800 From: "Zhou, Danny" To: "James (Fei) Liu-SSI" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] Issues of MSIx interrupt enable with user space driver Thread-Index: AQHQgf144QHvEesiRkOMFxvdtP0IsZ1jDizg Date: Tue, 28 Apr 2015 23:19:20 +0000 Message-ID: References: <99767EA2E27DD44DB4E9F9B9ACA458C03B30F07F@SSIEXCH-MB3.ssi.samsung.com> In-Reply-To: <99767EA2E27DD44DB4E9F9B9ACA458C03B30F07F@SSIEXCH-MB3.ssi.samsung.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: Tue, 28 Apr 2015 23:23:03 -0000 The V6 "Interrupt PMD" patch has been sent out to DPDK.org 2 months ago, an= d V7 is under development with changes=20 to include more generic APIs that could support all kinds of interrupts (e.= g. HW Rx interrupt and SW ring interrupt).=20 Stay tuned.=20 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of James (Fei) 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 drive= r >=20 > 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 han= dler. While we enable interrupt with VFIO MSIx, we > always get below errors after issuing one command: >=20 > [ 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 ent= ry 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 share= with us about your comments? thanks for your help > in advance. >=20 > Regards, > James >=20