On Tue, Sep 25, 2012 at 01:43:46PM -0600, Alex Williamson wrote:
Joerg, any thoughts on a quirk for this? Unfortunately we can't just
skip IOMMU groups when an alias is broken because it puts the other
IOMMU groups at risk that might not actually be isolated from this
device. It looks like
On Wed, 2012-09-26 at 15:20 +0200, Roedel, Joerg wrote:
On Tue, Sep 25, 2012 at 01:43:46PM -0600, Alex Williamson wrote:
Joerg, any thoughts on a quirk for this? Unfortunately we can't just
skip IOMMU groups when an alias is broken because it puts the other
IOMMU groups at risk that might
Florian,
On Wed, Sep 26, 2012 at 01:01:54AM +0200, Florian Dazinger wrote:
you're right, either amd_iommu=off or removing the audio card makes
the failure disappear. I will test the new BIOS rev. tomorrow.
Can you please test this diff and report if it fixes the problem for
you?
Thanks.
diff
On Wed, 2012-09-26 at 17:04 +0200, Roedel, Joerg wrote:
On Wed, Sep 26, 2012 at 08:52:01AM -0600, Alex Williamson wrote:
Assuming this works, it may be ok as a 3.7 fix, but if there was
actually more than one device behind the alias we'd expose them as
separate iommu groups. I don't think
On Wed, 2012-09-26 at 17:10 +0200, Roedel, Joerg wrote:
On Wed, Sep 26, 2012 at 08:35:59AM -0600, Alex Williamson wrote:
Hmm, that throws a kink in iommu groups. So perhaps we need to make an
alias interface to iommu groups. Seems like this could just be an extra
parameter to
Am Wed, 26 Sep 2012 17:04:07 +0200
schrieb Roedel, Joerg joerg.roe...@amd.com:
On Wed, Sep 26, 2012 at 08:52:01AM -0600, Alex Williamson wrote:
Assuming this works, it may be ok as a 3.7 fix, but if there was
actually more than one device behind the alias we'd expose them as
separate iommu
