From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: suravee.suthikulpanit-5C7GfCeVMHo@public.gmane.org
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/3] iommu/amd: IOMMU Error Reporting/Handling/Filtering
Date: Fri, 21 Jun 2013 17:15:00 +0200 [thread overview]
Message-ID: <20130621151459.GK11309@8bytes.org> (raw)
In-Reply-To: <1369250155-12226-1-git-send-email-suravee.suthikulpanit-5C7GfCeVMHo@public.gmane.org>
On Wed, May 22, 2013 at 02:15:52PM -0500, Suthikulpanit, Suravee wrote:
> From: Suravee Suthikulpanit <suravee.suthikulpanit-5C7GfCeVMHo@public.gmane.org>
>
> This patch set implements framework for handling errors reported via IOMMU
> event log. It also implements mechanism to filter/suppress error messages when
> IOMMU hardware generates large amount event logs, which is often caused by
> devices performing invalid operations or from misconfiguring IOMMU hardware
> (e.g. IO_PAGE_FAULT and INVALID_DEVICE_QEQUEST").
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.
An exception is of course still the flags decoding in this patch-set.
This alone would be pretty compelling as long as there is no integration
into EDAC.
Joerg
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: suravee.suthikulpanit@amd.com
Cc: 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
Date: Fri, 21 Jun 2013 17:15:00 +0200 [thread overview]
Message-ID: <20130621151459.GK11309@8bytes.org> (raw)
In-Reply-To: <1369250155-12226-1-git-send-email-suravee.suthikulpanit@amd.com>
On Wed, May 22, 2013 at 02:15:52PM -0500, Suthikulpanit, Suravee wrote:
> From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
>
> This patch set implements framework for handling errors reported via IOMMU
> event log. It also implements mechanism to filter/suppress error messages when
> IOMMU hardware generates large amount event logs, which is often caused by
> devices performing invalid operations or from misconfiguring IOMMU hardware
> (e.g. IO_PAGE_FAULT and INVALID_DEVICE_QEQUEST").
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.
An exception is of course still the flags decoding in this patch-set.
This alone would be pretty compelling as long as there is no integration
into EDAC.
Joerg
next prev parent reply other threads:[~2013-06-21 15:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 19:15 [PATCH 0/3] iommu/amd: IOMMU Error Reporting/Handling/Filtering suravee.suthikulpanit-5C7GfCeVMHo
2013-05-22 19:15 ` suravee.suthikulpanit
2013-05-22 19:15 ` [PATCH 1/3] iommu/amd: Adding amd_iommu_log cmdline option suravee.suthikulpanit
2013-05-22 19:15 ` suravee.suthikulpanit
[not found] ` <1369250155-12226-1-git-send-email-suravee.suthikulpanit-5C7GfCeVMHo@public.gmane.org>
2013-05-22 19:15 ` [PATCH 2/3] iommu/amd: Add error handling/reporting/filtering logic suravee.suthikulpanit-5C7GfCeVMHo
2013-05-22 19:15 ` suravee.suthikulpanit
2013-05-22 19:15 ` [PATCH 3/3] iommu/amd: Remove old event printing logic suravee.suthikulpanit-5C7GfCeVMHo
2013-05-22 19:15 ` suravee.suthikulpanit
2013-06-04 5:27 ` [PATCH 0/3] iommu/amd: IOMMU Error Reporting/Handling/Filtering Suravee Suthikulpanit
2013-06-04 5:27 ` Suravee Suthikulpanit
2013-06-21 15:15 ` Joerg Roedel [this message]
2013-06-21 15:15 ` Joerg Roedel
[not found] ` <20130621151459.GK11309-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2013-06-21 15:59 ` Borislav Petkov
2013-06-21 15:59 ` Borislav Petkov
[not found] ` <20130621155933.GA24385-fF5Pk5pvG8Y@public.gmane.org>
2013-06-21 16:24 ` Joerg Roedel
2013-06-21 16:24 ` Joerg Roedel
[not found] ` <20130621162455.GN11309-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2013-06-21 16:44 ` Shuah Khan
2013-06-21 16:44 ` Shuah Khan
2013-06-21 17:36 ` Borislav Petkov
2013-06-21 17:36 ` Borislav Petkov
[not found] ` <20130621173625.GH22006-fF5Pk5pvG8Y@public.gmane.org>
2013-06-24 7:26 ` Joerg Roedel
2013-06-24 7:26 ` Joerg Roedel
[not found] ` <20130624072648.GQ11309-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2013-06-24 7:41 ` Borislav Petkov
2013-06-24 7:41 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130621151459.GK11309@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=suravee.suthikulpanit-5C7GfCeVMHo@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.