lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <1364428215-2513-1-git-send-email-suravee.suthikulpanit@amd.com>
Date:	Wed, 27 Mar 2013 18:50:15 -0500
From:	<suravee.suthikulpanit@....com>
To:	<iommu@...ts.linux-foundation.org>, <joro@...tes.org>
CC:	<linux-kernel@...r.kernel.org>,
	Suravee Suthikulpanit <suravee.suthikulpanit@....com>
Subject: [PATCH 0/3] iommu/amd: Improve IOMMU Event Log Interrupt Handling

From: Suravee Suthikulpanit <suravee.suthikulpanit@....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


--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ