On Tue, Apr 02, 2013 at 07:06:50PM -0500, Suthikulpanit, Suravee wrote:
From: Suravee Suthikulpanit suravee.suthikulpa...@amd.com
Add logic to decode AMD IOMMU event flag based on information from AMD IOMMU
specification.
This should simplify debugging IOMMU errors. Also, dump DTE
On 4/9/2013 4:41 AM, Joerg Roedel wrote:
On Tue, Apr 02, 2013 at 07:06:50PM -0500, Suthikulpanit, Suravee wrote:
From: Suravee Suthikulpanit suravee.suthikulpa...@amd.com
Add logic to decode AMD IOMMU event flag based on information from AMD IOMMU
specification.
This should simplify debugging
On Tue, Apr 09, 2013 at 10:12:13AM -0500, Suthikulpanit, Suravee wrote:
These messages are not high volumn. What I am trying to achieve
is for users to be able to just send the errors to developers once
they are encountered without having to tell them to go back and
reboot with the
:06 PM
To: iommu@lists.linux-foundation.org; j...@8bytes.org
Cc: linux-ker...@vger.kernel.org; Suthikulpanit, Suravee
Subject: [PATCH V3] iommu/amd: Add logic to decode AMD IOMMU event flag
From: Suravee Suthikulpanit suravee.suthikulpa...@amd.com
Add logic to decode AMD IOMMU event flag
On 4/8/2013 9:50 AM, Borislav Petkov wrote:
Independent from Joerg's feedback on this, I have only one question:
you're not seriously considering on dumping this Note:... line above
on*every* IO-PF, right?
Boris,
If you think that is obvious, I can get rid of this also.
Suravee
From: Suravee Suthikulpanit suravee.suthikulpa...@amd.com
Add logic to decode AMD IOMMU event flag based on information from AMD IOMMU
specification.
This should simplify debugging IOMMU errors. Also, dump DTE information in
additional cases.
This is an example:
AMD-Vi: Event logged
