* [PATCH 0/3] iommu/amd: Improve IOMMU Event Log Interrupt Handling
@ 2013-03-27 23:50 suravee.suthikulpanit
0 siblings, 0 replies; only message in thread
From: suravee.suthikulpanit @ 2013-03-27 23:50 UTC (permalink / raw)
To: iommu, joro; +Cc: linux-kernel, Suravee Suthikulpanit
From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Typically, IOMMU events are logged into the event log. Current driver processes each event
in the log when the hardware generate an MSI interrupt. It reports event type, device ID,
raw status flag, and etc. in the kernel log (dmesg)
1. The first patch improve event reporting by using the type of event and status flag to
decode event information and provide more detail in the report. This should also be useful
when debugging IOMMU issues.
2. The second patch provide interface for testing the event decoding logic using the debugfs.
3. Fix IOMMU event log interrupt handling which currently does not re-enable the event interrupt.
drivers/iommu/Kconfig | 9 ++
drivers/iommu/Makefile | 1 +
drivers/iommu/amd_iommu.c | 167 ++++++++++++++++++++++++++++++++------
drivers/iommu/amd_iommu_inject.c | 99 ++++++++++++++++++++++
drivers/iommu/amd_iommu_proto.h | 9 ++
drivers/iommu/amd_iommu_types.h | 1 +
6 files changed, 259 insertions(+), 27 deletions(-)
create mode 100644 drivers/iommu/amd_iommu_inject.c
--
1.7.10.4
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-03-27 23:50 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-03-27 23:50 [PATCH 0/3] iommu/amd: Improve IOMMU Event Log Interrupt Handling suravee.suthikulpanit
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®