From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: [PATCH 0/3] iommu/amd: IOMMU Error Reporting/Handling/Filtering Date: Mon, 24 Jun 2013 09:26:48 +0200 Message-ID: <20130624072648.GQ11309@8bytes.org> References: <1369250155-12226-1-git-send-email-suravee.suthikulpanit@amd.com> <20130621151459.GK11309@8bytes.org> <20130621155933.GA24385@pd.tnic> <20130621162455.GN11309@8bytes.org> <20130621173625.GH22006@pd.tnic> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20130621173625.GH22006-fF5Pk5pvG8Y@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Borislav Petkov Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: iommu@lists.linux-foundation.org On Fri, Jun 21, 2013 at 07:36:25PM +0200, Borislav Petkov wrote: > IOW, what specific functionality in EDAC are you actually thinking of? Okay, my believe until yesterday was that EDAC provides a consistent way to report hardware errors to userspace. That seems to be wrong. This in mind I think having a trace-point for that makes sense. But this trace-point must not be specific to a single IOMMU driver, I want it generic enough so that it can be used by all common IOMMU drivers to report hardware misbehaviors to userspace. Thanks, Joerg From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752934Ab3FXH0w (ORCPT ); Mon, 24 Jun 2013 03:26:52 -0400 Received: from 8bytes.org ([85.214.48.195]:38882 "EHLO mail.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752908Ab3FXH0v (ORCPT ); Mon, 24 Jun 2013 03:26:51 -0400 Date: Mon, 24 Jun 2013 09:26:48 +0200 From: Joerg Roedel To: Borislav Petkov Cc: suravee.suthikulpanit@amd.com, iommu@lists.linux-foundation.org, ddutile@redhat.com, alex.williamson@redhat.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/3] iommu/amd: IOMMU Error Reporting/Handling/Filtering Message-ID: <20130624072648.GQ11309@8bytes.org> References: <1369250155-12226-1-git-send-email-suravee.suthikulpanit@amd.com> <20130621151459.GK11309@8bytes.org> <20130621155933.GA24385@pd.tnic> <20130621162455.GN11309@8bytes.org> <20130621173625.GH22006@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130621173625.GH22006@pd.tnic> User-Agent: Mutt/1.5.21 (2010-09-15) X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Mon Jun 24 09:26:50 2013 X-DSPAM-Confidence: 0.9988 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 51c7f4ba20866720514722 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 21, 2013 at 07:36:25PM +0200, Borislav Petkov wrote: > IOW, what specific functionality in EDAC are you actually thinking of? Okay, my believe until yesterday was that EDAC provides a consistent way to report hardware errors to userspace. That seems to be wrong. This in mind I think having a trace-point for that makes sense. But this trace-point must not be specific to a single IOMMU driver, I want it generic enough so that it can be used by all common IOMMU drivers to report hardware misbehaviors to userspace. Thanks, Joerg