From: Stephen Hemminger <stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
To: "Carew, Alan" <alan.carew-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: [PATCH 00/10] igb_uio patches
Date: Tue, 10 Jun 2014 13:49:02 -0700 [thread overview]
Message-ID: <20140610134902.754d9261@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <0E29434AEE0C3A4180987AB476A6F630593A5F6C-kPTMFJFq+rF9qrmMLTLiibfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Tue, 10 Jun 2014 19:26:08 +0000
"Carew, Alan" <alan.carew-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:
> A question then, how does uio_pci_generic handle interrupt modes in terms of userspace interface when determining the configured interrupt mode?
uio_pci_generic only handles INTX disable, and nothing else. It doesn't do MSI
or allow IRQ control.
Also, it doesn't do iomap of resources, so theoretically if IOMMU is enabled
userspace would still not be able to access the resources.
prev parent reply other threads:[~2014-06-10 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140606212644.203613327@networkplumber.org>
2014-06-10 15:55 ` [PATCH 00/10] igb_uio patches Carew, Alan
[not found] ` <0E29434AEE0C3A4180987AB476A6F630593A5EC8-kPTMFJFq+rF9qrmMLTLiibfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-06-10 15:59 ` Burakov, Anatoly
[not found] ` <0E29434AEE0C3A4180987AB476A6F630593A5E2D@IRSMSX101.ger.corp.intel.com>
[not found] ` <20140610104035.08d3946a@nehalam.linuxnetplumber.net>
[not found] ` <20140610104035.08d3946a-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2014-06-10 19:26 ` Carew, Alan
[not found] ` <0E29434AEE0C3A4180987AB476A6F630593A5F6C-kPTMFJFq+rF9qrmMLTLiibfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-06-10 20:47 ` Stephen Hemminger
[not found] ` <20140610134709.03524b62-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2014-06-11 10:30 ` Neil Horman
2014-06-10 20:49 ` Stephen Hemminger [this message]
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=20140610134902.754d9261@nehalam.linuxnetplumber.net \
--to=stephen-otpzqlsittunbdjkjebofr2eb7je58tq@public.gmane.org \
--cc=alan.carew-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.