linux-kernel - Re: [PATCH 0/3] iommu/amd: IOMMU Error Reporting/Handling/Filtering

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130621155933.GA24385@pd.tnic>
Date:	Fri, 21 Jun 2013 17:59:33 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Joerg Roedel <joro@...tes.org>
Cc:	suravee.suthikulpanit@....com, iommu@...ts.linux-foundation.org,
	ddutile@...hat.com, alex.williamson@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] iommu/amd: IOMMU Error Reporting/Handling/Filtering

On Fri, Jun 21, 2013 at 05:15:00PM +0200, Joerg Roedel wrote:
> Instead of extending this bad scaling dmesg error-reporting mechanism,
> I would very much like to see an integration of IOMMU error handling
> into the EDAC framework.

Wouldn't just adding a tracepoint and collecting the logs in debugfs be
enough? This would at least avoid spamming syslog with the messages.

More sophisticated error handling can be done later...

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/