From: David Cohen <dacohen@gmail.com>
To: Hiroshi.DOYU@nokia.com
Cc: linux-omap@vger.kernel.org, David Cohen <dacohen@gmail.com>
Subject: [RFC/PATCH 0/3] IOMMU fault callback support
Date: Sat, 12 Feb 2011 12:42:50 +0200 [thread overview]
Message-ID: <1297507373-1520-1-git-send-email-dacohen@gmail.com> (raw)
Hi,
These are RFC patches. They're intended to add fault callback support so
IOMMU users can debug or react when a fault happens.
IOMMU faults might be very difficult to reproduce and then to figure out
the source of the problem. Currently IOMMU driver prints not so useful
debug message and does not notice user about such issue.
With a fault callback, IOMMU user may debug much more useful information
and/or react to go back to a valid state or, in worse cases, to leave device
in a state where it's still possible to use it and proceed with some
investigation.
Comments are welcome.
Br,
David
---
David Cohen (3):
OMAP: IOMMU: Add generic IOMMU errors code
OMAP2+: IOMMU: change OMAP2+ error message to dev_dbg()
OMAP: IOMMU: add support to callback during fault handling
arch/arm/mach-omap2/iommu2.c | 23 ++++++++++++++---
arch/arm/plat-omap/include/plat/iommu.h | 15 ++++++++++-
arch/arm/plat-omap/iommu.c | 41 ++++++++++++++++++++++++++++---
3 files changed, 70 insertions(+), 9 deletions(-)
next reply other threads:[~2011-02-12 10:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 10:42 David Cohen [this message]
2011-02-12 10:42 ` [RFC/PATCH 1/3] OMAP: IOMMU: Add generic IOMMU errors code David Cohen
2011-02-13 22:33 ` Varadarajan, Charulatha
2011-02-14 11:28 ` David Cohen
2011-02-12 10:42 ` [RFC/PATCH 2/3] OMAP2+: IOMMU: change OMAP2+ error message to dev_dbg() David Cohen
2011-02-12 10:42 ` [RFC/PATCH 3/3] OMAP: IOMMU: add support to callback during fault handling David Cohen
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=1297507373-1520-1-git-send-email-dacohen@gmail.com \
--to=dacohen@gmail.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox