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 36A73C6DE for ; Wed, 29 Apr 2015 00:03:48 +0200 (CEST) X-ASG-Debug-ID: 1430258620-03754d3e0f0008000c-TfluYd Received: from ssiexch-casht2.ssi.samsung.com ([105.128.134.61]) by mx2.ssi.samsung.com with ESMTP id avkl5msxDfhaeQS3 for ; Tue, 28 Apr 2015 15:03:46 -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-casht2.ssi.samsung.com ([fe80::b5ff:5921:7ac7:4da4%11]) with mapi id 14.03.0123.003; Tue, 28 Apr 2015 14:57:53 -0700 From: "James (Fei) Liu-SSI" To: "dev@dpdk.org" Thread-Topic: Issues of MSIx interrupt enable with user space driver X-ASG-Orig-Subj: Issues of MSIx interrupt enable with user space driver Thread-Index: AQHQgf144QHvEesiRkOMFxvdtP0IsQ== Date: Tue, 28 Apr 2015 21:57:31 +0000 Message-ID: <99767EA2E27DD44DB4E9F9B9ACA458C03B30F07F@SSIEXCH-MB3.ssi.samsung.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [105.128.34.135] 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: 1430258625 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: [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 22:03:48 -0000 Hi All,=0A= We are porting driver from kernel into user space driver with DPDK for = one of our devices. Polling thread works fine without any issue. However, w= e want to switch from polling to interrupt based handler. While we enable i= nterrupt with VFIO MSIx, we always get below errors after issuing one comma= nd:=0A= =0A= [ 465.464186] dmar: DRHD: handling fault status reg 2=0A= [ 465.464194] dmar: INTR-REMAP: Request device [[02:00.0] fault index 27= =0A= [ 465.464194] INTR-REMAP:[fault reason 34] Present field in the IRTE entry= is clear=0A= =0A= Here are steps we follow to enable interrupt:=0A= 1. --vfio-intr msix was passed in as parameter for rte_eal_init=0A= 2. rte_intr_enable was called during the drive probe stage.=0A= 3. rte_intr_callback_register was called after interrupt was enabled=0A= =0A= =0A= =0A= Is there anyone in the forum who worked on the interrupt handler to share w= ith us about your comments? thanks for your help in advance.=0A= =0A= Regards,=0A= James=0A= =