From: David Gibson <david@gibson.dropbear.id.au>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Joerg Roedel <joerg.roedel@amd.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu: making IOMMU sysfs nodes API public
Date: Mon, 25 Feb 2013 11:03:22 +1100 [thread overview]
Message-ID: <20130225000322.GN30946@truffula.fritz.box> (raw)
In-Reply-To: <1361506273.2801.327.camel@bling.home>
[-- Attachment #1: Type: text/plain, Size: 2103 bytes --]
On Thu, Feb 21, 2013 at 09:11:13PM -0700, Alex Williamson wrote:
> On Fri, 2013-02-22 at 11:04 +1100, David Gibson wrote:
> > On Tue, Feb 19, 2013 at 01:11:51PM -0700, Alex Williamson wrote:
> > > On Tue, 2013-02-19 at 18:38 +1100, David Gibson wrote:
> > > > On Mon, Feb 18, 2013 at 10:24:00PM -0700, Alex Williamson wrote:
> > > > > On Mon, 2013-02-18 at 17:15 +1100, Alexey Kardashevskiy wrote:
> > [snip]
> > > > > Adding the window size to sysfs seems more readily convenient,
> > > > > but is it so hard for userspace to open the files and call a couple
> > > > > ioctls to get far enough to call IOMMU_GET_INFO? I'm unconvinced the
> > > > > clutter in sysfs more than just a quick fix. Thanks,
> > > >
> > > > And finally, as Alexey points out, isn't the point here so we know how
> > > > much rlimit to give qemu? Using ioctls we'd need a special tool just
> > > > to check the dma window sizes, which seems a bit hideous.
> > >
> > > Is it more hideous that using iommu groups to report a vfio imposed
> > > restriction? Are a couple open files and a handful of ioctls worse than
> > > code to parse directory entries and the future maintenance of an
> > > unrestricted grab bag of sysfs entries?
> >
> > The fact that the memory is locked is a vfio restriction, but the
> > actual dma window size is, genuinely, a property of the group.
>
> A group is an association of devices based on isolation and visibility.
> The dma window happens to be associated with a group on your platform,
> but that's not always the case.
It's certainly an iommu driver specific group property, but a group
property nonetheless.
> This is why I was hoping something in
> sysfs already reported the dma window so that we could point to it
> rather than creating an interface where it doesn't really belong.
Alas, no. There's been no reason to expose PEs previously.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2013-02-25 0:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 11:54 [PATCH 0/2] vfio on power Alexey Kardashevskiy
2013-02-11 11:54 ` [PATCH 1/2] vfio powerpc: enabled on powernv platform Alexey Kardashevskiy
2013-02-11 22:16 ` Alex Williamson
2013-02-11 23:19 ` Alexey Kardashevskiy
2013-02-12 0:01 ` Alex Williamson
2013-02-25 2:21 ` Paul Mackerras
2013-02-11 11:54 ` [PATCH 2/2] vfio powerpc: implemented IOMMU driver for VFIO Alexey Kardashevskiy
2013-02-11 22:17 ` Alex Williamson
2013-02-11 23:45 ` Alexey Kardashevskiy
2013-02-12 0:25 ` Alex Williamson
2013-02-12 4:06 ` [PATCH] iommu: making IOMMU sysfs nodes API public Alexey Kardashevskiy
2013-02-12 5:07 ` Alex Williamson
2013-02-12 14:42 ` Alexey Kardashevskiy
2013-02-12 17:15 ` Alex Williamson
2013-02-18 6:15 ` Alexey Kardashevskiy
2013-02-19 5:24 ` Alex Williamson
2013-02-19 5:48 ` Alexey Kardashevskiy
2013-02-19 19:53 ` Alex Williamson
2013-02-19 7:38 ` David Gibson
2013-02-19 20:11 ` Alex Williamson
2013-02-20 2:31 ` Alexey Kardashevskiy
2013-02-20 3:47 ` Alex Williamson
2013-02-20 4:20 ` Alexey Kardashevskiy
2013-02-20 4:33 ` Alex Williamson
2013-03-18 3:53 ` Alexey Kardashevskiy
2013-03-19 2:40 ` Alex Williamson
2013-03-19 7:08 ` [PATCH] vfio powerpc: implement IOMMU driver for VFIO Alexey Kardashevskiy
2013-03-20 20:45 ` Alex Williamson
2013-03-21 0:57 ` Alexey Kardashevskiy
2013-03-21 1:29 ` Alex Williamson
2013-03-21 1:55 ` David Gibson
2013-03-21 3:16 ` Alex Williamson
2013-03-25 2:12 ` David Gibson
2013-02-22 0:04 ` [PATCH] iommu: making IOMMU sysfs nodes API public David Gibson
2013-02-22 4:11 ` Alex Williamson
2013-02-25 0:03 ` David Gibson [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=20130225000322.GN30946@truffula.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=joerg.roedel@amd.com \
--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).