From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pd0-f180.google.com (mail-pd0-f180.google.com [209.85.192.180]) by dpdk.org (Postfix) with ESMTP id E4618C6DA for ; Wed, 29 Apr 2015 01:42:31 +0200 (CEST) Received: by pdbqa5 with SMTP id qa5so10359843pdb.1 for ; Tue, 28 Apr 2015 16:42:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=R2oVHZcUnwpEFk8V2p/444ISTPASX8pRNyF0zXozwo8=; b=CcrOJ3Z48wGV1hOFx96/NZwJWqBaTXBYpbTG/g9vp927Vx/cC76VuNwAB3uY9cC36S w1poQtpBh33cCAHdE/AqDSZLmYWzk1foOuoOBceXq19go82cxPtEjhdgrfOhCjBErBho j9CfYiD2rJQ3oSeswMCiFxECt1ObBLdFMQaXbneQoip5ZDUr+gJSgk5QwmXqfyG4zNKC XQuG08UUARkGT4ZKol4y7wj654T8bE9T8S1dfZpheNkl2tKukXX7fwoBkEs2ZSnK5eFU mXTylWv5KUZAW1WgC9rdJiirkzBV6o8vyby4FTZUfHXGSzOq2y0gLpEPY5SXKPhuW6sh Jfgw== X-Gm-Message-State: ALoCoQnXgoEMFDa+VU8SIxFGdaEskG2zHON7QfGiDhpHxxjrKFVaAR/wz80Nwky4HJCLt0znuATn X-Received: by 10.68.107.97 with SMTP id hb1mr21599854pbb.122.1430264551026; Tue, 28 Apr 2015 16:42:31 -0700 (PDT) Received: from urahara (static-50-53-82-155.bvtn.or.frontiernet.net. [50.53.82.155]) by mx.google.com with ESMTPSA id v3sm23410387pbs.18.2015.04.28.16.42.30 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Apr 2015 16:42:30 -0700 (PDT) Date: Tue, 28 Apr 2015 16:42:34 -0700 From: Stephen Hemminger To: "James (Fei) Liu-SSI" Message-ID: <20150428164234.4a191ef4@urahara> In-Reply-To: <99767EA2E27DD44DB4E9F9B9ACA458C03B30F07F@SSIEXCH-MB3.ssi.samsung.com> References: <99767EA2E27DD44DB4E9F9B9ACA458C03B30F07F@SSIEXCH-MB3.ssi.samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Tue, 28 Apr 2015 23:42:32 -0000 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 for 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 command: > > [ 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?