DPDK patches and discussions
 help / color / mirror / Atom feed
From: "James (Fei) Liu-SSI" <james.liu@ssi.samsung.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Issues of MSIx interrupt enable with user space driver
Date: Tue, 28 Apr 2015 21:57:31 +0000	[thread overview]
Message-ID: <99767EA2E27DD44DB4E9F9B9ACA458C03B30F07F@SSIEXCH-MB3.ssi.samsung.com> (raw)

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.

Regards,
James
   

             reply	other threads:[~2015-04-28 22:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 21:57 James (Fei) Liu-SSI [this message]
2015-04-28 23:19 ` Zhou, Danny
2015-04-29 18:25   ` James (Fei) Liu-SSI
2015-04-29 22:36     ` Zhou, Danny
2015-04-28 23:42 ` Stephen Hemminger
2015-04-29 18:24   ` James (Fei) Liu-SSI
2015-04-28 23:46 ` James (Fei) Liu-SSI

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=99767EA2E27DD44DB4E9F9B9ACA458C03B30F07F@SSIEXCH-MB3.ssi.samsung.com \
    --to=james.liu@ssi.samsung.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).