From: Joerg Roedel <joro@8bytes.org>
To: Shuah Khan <shuah.kh@samsung.com>
Cc: alex.williamson@redhat.com, Varun.Sethi@freescale.com,
aik@ozlabs.ru, joe@perches.com, rostedt@goodmis.org,
fweisbec@gmail.com, mingo@redhat.com, tony@atomide.com,
ohad@wizery.com, andreas.herrmann@calxeda.com,
will.deacon@arm.com, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, shuahkhan@gmail.com
Subject: Re: [PATCH v2] iommu: Add event tracing feature to iommu
Date: Wed, 14 Aug 2013 18:17:58 +0200 [thread overview]
Message-ID: <20130814161758.GQ28811@8bytes.org> (raw)
In-Reply-To: <520BAAF0.8000509@samsung.com>
On Wed, Aug 14, 2013 at 10:06:08AM -0600, Shuah Khan wrote:
> Is this what you have in mind or does my original patch set minus
> the amd_event and drivers/iommu/amd_iommu.c change?
>
> Patch 1:
> drivers/iommu/Makefile
> drivers/iommu/iommu-traces.c
> include/trace/events/iommu.h
>
> One patch for each of the following events?
>
> iommu:add_device_to_group
> iommu:remove_device_from_group
> iommu:attach_device_to_domain
> iommu:detach_device_from_domain
> iommu:unmap
> iommu:map
Right, please do a seperate patch for each event.
> I see what you are saying. Adding event to report_iommu_fault()
> would cover all IOMMUs. I would like to work on adding an event
> unless you already have it in works.
I don't, so feel free to add one too.
Joerg
next prev parent reply other threads:[~2013-08-14 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 14:57 [PATCH v2] iommu: Add event tracing feature to iommu Shuah Khan
2013-08-09 16:41 ` Shuah Khan
2013-08-14 14:17 ` Joerg Roedel
2013-08-14 16:06 ` Shuah Khan
2013-08-14 16:17 ` Joerg Roedel [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-30 1:22 Shuah Khan
2013-07-30 1:24 ` Shuah Khan
2013-07-30 1:29 ` Joe Perches
2013-07-30 14:18 ` 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=20130814161758.GQ28811@8bytes.org \
--to=joro@8bytes.org \
--cc=Varun.Sethi@freescale.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=andreas.herrmann@calxeda.com \
--cc=fweisbec@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ohad@wizery.com \
--cc=rostedt@goodmis.org \
--cc=shuah.kh@samsung.com \
--cc=shuahkhan@gmail.com \
--cc=tony@atomide.com \
--cc=will.deacon@arm.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