From: Stephen Hemminger <stephen@networkplumber.org>
To: Ranran <ranshalit@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Interrupt is catched in kernel, but not handled
Date: Sun, 1 Dec 2019 09:07:07 -0800 [thread overview]
Message-ID: <20191201090707.450b6a4f@hermes.lan> (raw)
In-Reply-To: <CAJ2oMhJ12TRuk_nvsCiM3q4VcD5CRJ1DMZO5TAKpdh5aNEnk=w@mail.gmail.com>
On Sat, 30 Nov 2019 19:49:16 +0200
Ranran <ranshalit@gmail.com> wrote:
> > >
> > > I also verified that there are no additional irq numbered 23 except
> > > for our device.
> > >
> > > How can it be that irq is catched, but not delivered to userspace ?
> > > Any suggestion is much appreciated,
> > >
> > > ran
> >
> > UIO PCI generic does not support interrupts.
> > You need to use VFIO (preferred) or igb_uio
> >
Actually UIO PCI generic does support interrupts but only legacy INTx,
it does not support MSI or MSI-x modes.
next prev parent reply other threads:[~2019-12-01 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-30 8:40 Ranran
2019-11-30 16:51 ` Stephen Hemminger
2019-11-30 17:49 ` Ranran
2019-12-01 17:07 ` Stephen Hemminger [this message]
2019-12-01 18:16 ` Ranran
2019-12-06 16:55 ` Stephen Hemminger
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=20191201090707.450b6a4f@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=ranshalit@gmail.com \
/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).