From: Guenter Roeck <linux@roeck-us.net>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Hans J. Koch" <hjk@hansjkoch.de>, Rob Landley <rob@landley.net>,
linux-doc@vger.kernel.org
Subject: Re: [RFC PATCH] uio: uio_pci_generic: Add support for MSI interrupts
Date: Thu, 27 Jun 2013 06:52:20 -0700 [thread overview]
Message-ID: <20130627135220.GA5518@roeck-us.net> (raw)
In-Reply-To: <20130627074501.GC5489@redhat.com>
On Thu, Jun 27, 2013 at 10:45:01AM +0300, Michael S. Tsirkin wrote:
> On Wed, Jun 26, 2013 at 03:30:23PM -0700, Guenter Roeck wrote:
> > Enable support for MSI interrupts if the device supports it.
> > Since MSI interrupts are edge triggered, it is no longer necessary to
> > disable interrupts in the kernel and re-enable them from user-space.
> > Instead, clearing the interrupt condition in the user space application
> > automatically re-enables the interrupt.
> >
> > Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> > ---
> > An open question is if we can just do this unconditionally
> > or if there should be some flag to enable it. A module parameter, maybe ?
>
> NACK
>
> UIO is for devices that don't do memory writes.
> Anything that can do writes must be protected by an IOMMU
> and/or have a secure kernel driver, not a UIO stub.
>
> MSI is done by memory writes so if userspace
> controls the device it can trick it to write
> anywhere in memory.
>
Interesting. Thanks for letting me know.
Guenter
next prev parent reply other threads:[~2013-06-27 13:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 22:30 [RFC PATCH] uio: uio_pci_generic: Add support for MSI interrupts Guenter Roeck
2013-06-27 7:45 ` Michael S. Tsirkin
2013-06-27 13:52 ` Guenter Roeck [this message]
2013-06-27 17:00 ` Guenter Roeck
2013-07-04 7:20 ` Michael S. Tsirkin
2013-07-04 14:25 ` Guenter Roeck
2013-07-04 14:34 ` Michael S. Tsirkin
2013-07-04 16:35 ` Guenter Roeck
2013-07-07 8:15 ` Michael S. Tsirkin
2013-07-07 14:39 ` Guenter Roeck
2013-07-07 14:42 ` Michael S. Tsirkin
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=20130627135220.GA5518@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=hjk@hansjkoch.de \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=rob@landley.net \
/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.