mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <suravee.suthikulpanit@amd.com>
To: <iommu@lists.linux-foundation.org>, <joro@8bytes.org>
Cc: <linux-kernel@vger.kernel.org>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: [PATCH 0/3] iommu/amd: Improve IOMMU Event Log Interrupt Handling
Date: Wed, 27 Mar 2013 18:50:15 -0500	[thread overview]
Message-ID: <1364428215-2513-1-git-send-email-suravee.suthikulpanit@amd.com> (raw)

From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>

Typically, IOMMU events are logged into the event log.  Current driver processes each event
in the log when the hardware generate an MSI interrupt. It reports event type, device ID, 
raw status flag, and etc. in the kernel log (dmesg)

1. The first patch improve event reporting by using the type of event and status flag to 
decode event information and provide more detail in the report. This should also be useful 
when debugging IOMMU issues.

2. The second patch provide interface for testing the event decoding logic using the debugfs.

3. Fix IOMMU event log interrupt handling which currently does not re-enable the event interrupt.

 drivers/iommu/Kconfig            |    9 ++
 drivers/iommu/Makefile           |    1 +
 drivers/iommu/amd_iommu.c        |  167 ++++++++++++++++++++++++++++++++------
 drivers/iommu/amd_iommu_inject.c |   99 ++++++++++++++++++++++
 drivers/iommu/amd_iommu_proto.h  |    9 ++
 drivers/iommu/amd_iommu_types.h  |    1 +
 6 files changed, 259 insertions(+), 27 deletions(-)
 create mode 100644 drivers/iommu/amd_iommu_inject.c

-- 
1.7.10.4



                 reply	other threads:[~2013-03-27 23:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1364428215-2513-1-git-send-email-suravee.suthikulpanit@amd.com \
    --to=suravee.suthikulpanit@amd.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®