[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191015151112.17225-1-volchkov@amazon.de>
Date: Tue, 15 Oct 2019 17:11:10 +0200
From: Yuri Volchkov <volchkov@...zon.de>
To: <iommu@...ts.linux-foundation.org>, <linux-kernel@...r.kernel.org>,
<linux-pci@...r.kernel.org>
CC: <joro@...tes.org>, <bhelgaas@...gle.com>, <dwmw2@...radead.org>,
<neugebar@...zon.co.uk>, Yuri Volchkov <volchkov@...zon.de>
Subject: [PATCH 0/2] iommu/dmar: expose fault counters via sysfs
For health monitoring, it can be useful to know if iommu is behaving as
expected. DMAR faults can be an indicator that a device:
- has been misconfigured, or
- has experienced a hardware hiccup and replacement should
be considered, or
- has been issuing faults due to malicious activity
Currently the only way to check if there were any DMAR faults on the
host is to scan the dmesg output. However this approach is not very
elegant. The information we are looking for can be wrapped out of the
buffer, or masked (since it is a rate-limited print) by another
device.
The series adds counters for DMAR faults and exposes them via sysfs.
Yuri Volchkov (2):
iommu/dmar: collect fault statistics
iommu/dmar: catch early fault occurrences
drivers/iommu/dmar.c | 182 ++++++++++++++++++++++++++++++++----
drivers/iommu/intel-iommu.c | 1 +
drivers/pci/pci-sysfs.c | 20 ++++
include/linux/intel-iommu.h | 4 +
include/linux/pci.h | 11 +++
5 files changed, 201 insertions(+), 17 deletions(-)
--
2.23.0
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Ralf Herbrich
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
Powered by blists - more mailing lists