DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ranran <ranshalit@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Interrupt is catched in kernel, but not handled
Date: Sun, 1 Dec 2019 20:16:59 +0200	[thread overview]
Message-ID: <CAJ2oMh+SYG=n7V9=ruBQKMueHY3pAPEBipwztaq-BfL-wu5fiQ@mail.gmail.com> (raw)
In-Reply-To: <20191201090707.450b6a4f@hermes.lan>

בתאריך יום א׳, 1 בדצמ׳ 2019, 19:07, מאת Stephen Hemminger ‏<
stephen@networkplumber.org>:

> 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.
>

Right.
The device I work with is FPGA xilinx which should support INTx. Yet, even
though irqhandler is called, it does not pass pci_check_and_mask_intx, and
therefore irq is not handled, as I written in the original post.

Thanks

>

  reply	other threads:[~2019-12-01 18:17 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
2019-12-01 18:16       ` Ranran [this message]
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='CAJ2oMh+SYG=n7V9=ruBQKMueHY3pAPEBipwztaq-BfL-wu5fiQ@mail.gmail.com' \
    --to=ranshalit@gmail.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).