public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <shuah.kh@samsung.com>
To: joro@8bytes.org, alex.williamson@redhat.com,
	Varun.Sethi@freescale.com, udknight@gmail.com, aik@ozlabs.ru,
	rostedt@goodmis.org, fweisbec@gmail.com, mingo@redhat.com
Cc: Shuah Khan <shuah.kh@samsung.com>,
	linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	shuahkhan@gmail.com
Subject: [PATCH 0/2] iommu: Add iommu_fault class event to iommu trace
Date: Fri, 16 Aug 2013 11:20:15 -0600	[thread overview]
Message-ID: <cover.1376672275.git.shuah.kh@samsung.com> (raw)

This patch set adds iommu_fault class event to iommu trace. iommu_fault class
event can be enabled to trigger when an iommu fault occurs. This trace event
is intended to be called to report the fault information. Trace information
includes driver name, device name, iova, and flags.

iommu_fault:report_fault

This patch set depends on the previous patch set that added iommu tracing
feature. Reference:

http://www.kernelhub.org/?msg=313155&p=2
http://www.kernelhub.org/?msg=313156&p=2

Shuah Khan (2):
  iommu: Add iommu_fault class event to iommu trace
  iommu: Change iommu driver to call report_fault trace event

 drivers/iommu/iommu-traces.c |    3 +++
 include/linux/iommu.h        |    2 ++
 include/trace/events/iommu.h |   33 +++++++++++++++++++++++++++++++++
 3 files changed, 38 insertions(+)

-- 
1.7.10.4


             reply	other threads:[~2013-08-16 17:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16 17:20 Shuah Khan [this message]
2013-08-16 17:20 ` [PATCH 1/2] iommu: Add iommu_fault class event to iommu trace Shuah Khan
2013-09-24 10:48   ` Joerg Roedel
2013-09-24 12:39     ` Shuah Khan
2013-08-16 17:20 ` [PATCH 2/2] iommu: Change iommu driver to call report_fault trace event Shuah Khan

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=cover.1376672275.git.shuah.kh@samsung.com \
    --to=shuah.kh@samsung.com \
    --cc=Varun.Sethi@freescale.com \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=shuahkhan@gmail.com \
    --cc=udknight@gmail.com \
    /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