From: "Michael S. Tsirkin" <mst@redhat.com>
To: Dominic Eschweiler <eschweiler@fias.uni-frankfurt.de>
Cc: "Hans J. Koch" <hjk@hansjkoch.de>,
Andreas Schallenberg <embedded@gmx.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kvm@vger.kernel.org
Subject: Re: UIO: missing resource mapping
Date: Fri, 13 Jul 2012 16:22:23 +0300 [thread overview]
Message-ID: <20120713132223.GA10959@redhat.com> (raw)
In-Reply-To: <1342166955.6607.5.camel@blech>
On Fri, Jul 13, 2012 at 10:09:15AM +0200, Dominic Eschweiler wrote:
> Am Freitag, den 13.07.2012, 02:16 +0300 schrieb Michael S. Tsirkin:
> > My concern was people will ask for more and more stuff that pci
> > sysfs already has.
> > If we do add these is there a way to not duplicate code from pci?
>
> I have some concerns about the placing for the BAR mapping code inside
> the kernel. The point is, that sysfs currently makes it possible to map
> BARs of all card which are handled by any driver. This is fine in case
> of UIO, because it is intended that a user-space program maps BARs, but
> it is also possible to map BARs that are already handle by a kernel
> driver. It i therefore possible to jam the system by confusing sysfs
> entries.
>
> I don't know which implications this has, but I would move the BAR
> mapping capabilities completely to UIO. This should ensure that only
> BARs can be mapped, which are handled by UIO and no other kernel-space
> driver.
Could you give an example of the problem? How do you bind
both UIO and another driver to the same device?
--
MST
next prev parent reply other threads:[~2012-07-13 13:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FFE7C1F.7080702@gmx.net>
2012-07-12 19:44 ` UIO: missing resource mapping Hans J. Koch
2012-07-12 23:16 ` Michael S. Tsirkin
2012-07-12 23:40 ` Hans J. Koch
2012-07-12 23:58 ` Michael S. Tsirkin
2012-07-13 8:09 ` Dominic Eschweiler
2012-07-13 13:22 ` Michael S. Tsirkin [this message]
2012-07-13 14:18 ` Hans J. Koch
2012-07-13 14:44 ` Dominic Eschweiler
2012-07-13 14:42 ` Dominic Eschweiler
2012-07-13 18:19 ` Michael S. Tsirkin
2012-07-16 18:16 ` Dominic Eschweiler
2012-07-16 21:58 ` Hans J. Koch
2012-07-18 10:40 ` Dominic Eschweiler
2012-07-18 23:47 ` Hans J. Koch
2012-08-06 11:49 ` Dominic Eschweiler
2012-08-08 22:08 ` Hans J. Koch
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=20120713132223.GA10959@redhat.com \
--to=mst@redhat.com \
--cc=embedded@gmx.net \
--cc=eschweiler@fias.uni-frankfurt.de \
--cc=gregkh@linuxfoundation.org \
--cc=hjk@hansjkoch.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).