[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1322775151.3729.25.camel@pasglop>
Date: Fri, 02 Dec 2011 08:32:31 +1100
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Alex Williamson <alex.williamson@...hat.com>
Cc: David Gibson <dwg@....ibm.com>, joerg.roedel@....com,
dwmw2@...radead.org, iommu@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org, chrisw@...hat.com, agraf@...e.de,
scottwood@...escale.com, B08248@...escale.com
Subject: Re: [PATCH 1/4] iommu: Add iommu_device_group callback and
iommu_group sysfs entry
On Wed, 2011-11-30 at 23:48 -0700, Alex Williamson wrote:
> See bus_set_iommu(struct bus_type *bus, struct iommu_ops *ops). It
> wasn't long ago that we had a global iommu_ops.
Right now, the dma_ops are per-device but the iommu populate/depopulate
hooks are system global, installed by the platform code at boot time, on
powerpc. We could try to "fit in" an iommu "driver" at that point.
In theory, you can connect separate IO chips on POWER server and in fact
it happens on high end boxes, tho they tend to have a similar "PE#"
mechanism, but with different constraints and resources capacities.
However we aren't concerned with that initially for KVM as we are
targetting only lower end machines with only one p7ioc for now.
But I can see more heterogenous setup showing up in embedded space..
> Are heterogeneous
> iommus using different drivers on the same bus_type really a possibility
> on your system, or are we dealing with hypothetical situations? You'd
> currently need to multiplex iommu_ops callbacks between the drivers
> yourself.
We could.
Ben.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists