From: David Gibson <david@gibson.dropbear.id.au>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, aik@ozlabs.ru, qemu-devel@nongnu.org,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
joerg.roedel@amd.com, dwmw2@infradead.org
Subject: Re: [Qemu-devel] [PATCH 1/2] Isolation groups
Date: Fri, 30 Mar 2012 15:19:46 +1100 [thread overview]
Message-ID: <20120330041946.GA21161@truffala.fritz.box> (raw)
In-Reply-To: <1332876883.29722.143.camel@bling.home>
On Tue, Mar 27, 2012 at 01:34:43PM -0600, Alex Williamson wrote:
[snip]
> > > > this case, it gets a bit complex. When the FooBus isolation provider
> > > > is active, the FooBus devices would be in their own groups, not the
> > > > group of the FooBridge and its sibling. When the FooBus isolation
> > > > provider is removed, it would have to configure the FooBus IOMMU to a
> > > > passthrough mode, and revert the FooBus devices to the parent's
> > > > group. Hm. Complicated.
> > >
> > > Yep. I think we're arriving at the same point. Groups are
> > > hierarchical, but ownership via a manager cannot be nested. So to
> > > manage a group, we need to walk the entire tree of devices below each
> > > device checking that none of the groups are managed and all the devices
> > > are using the right driver, then walk up from the group to verify no
> > > group of a parent device is managed. Thanks,
> >
> > Blargh. I really, really hope we can come up with a simpler model
> > than that.
>
> Yep, I'm pretty well at the end of this experiment. Honestly, I think
> isolation groups are the wrong approach. We're trying to wrap too many
> concepts together and it's completely unmanageable. I cannot see adding
> the complexity we're talking about here to the core device model for
> such a niche usage. I think we're better off going back to the
> iommu_device_group() and building that out into something more complete,
> starting with group based iommu ops and a dma quirk infrastructure.
> >From there we can add some basic facilities to toggle driver autoprobe,
> maybe setup notifications for the group, and hopefully include a way to
> share iommu mappings between groups. Anything much beyond that we
> should probably leave for something like the vfio driver. Thanks,
Yes, well, I was hoping for a simpler model that didn't involve simply
sweeping all the issues under a rug.
--
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
next prev parent reply other threads:[~2012-03-30 4:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 22:32 [Qemu-devel] [PATCH 0/2] RFC Isolation API Alex Williamson
2012-03-12 22:32 ` [Qemu-devel] [PATCH 1/2] Isolation groups Alex Williamson
2012-03-13 14:33 ` David Gibson
2012-03-13 16:49 ` Alex Williamson
2012-03-14 9:58 ` David Gibson
2012-03-15 20:15 ` Alex Williamson
2012-03-16 3:45 ` David Gibson
2012-03-16 19:31 ` Alex Williamson
2012-03-17 4:57 ` David Gibson
2012-03-21 21:12 ` Alex Williamson
2012-03-27 5:14 ` David Gibson
2012-03-27 19:34 ` Alex Williamson
2012-03-30 4:19 ` David Gibson [this message]
2012-03-12 22:33 ` [Qemu-devel] [PATCH 2/2] intel-iommu: Basic isolation group provider support Alex Williamson
2012-03-13 13:57 ` [Qemu-devel] [PATCH 0/2] RFC Isolation API David Gibson
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=20120330041946.GA21161@truffala.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.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).