mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Shuah Khan <shuah.kh@samsung.com>
Cc: joro@8bytes.org, alex.williamson@redhat.com,
	Varun.Sethi@freescale.com, aik@ozlabs.ru, 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: Mon, 29 Jul 2013 18:29:28 -0700	[thread overview]
Message-ID: <1375147768.2075.91.camel@joe-AO722> (raw)
In-Reply-To: <1375147366-2922-1-git-send-email-shuah.kh@samsung.com>

On Mon, 2013-07-29 at 19:22 -0600, Shuah Khan wrote:
> Add tracing feature to iommu to report various iommu events. Classes
> iommu_group, iommu_device, iommu_map_unmap, and iommu_amd_event are defined.

Hi again Shuah

> diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c
[]
> @@ -2159,6 +2160,15 @@ static int iommu_prepare_identity_map(struct pci_dev *pdev,
>  	printk(KERN_INFO
>  	       "IOMMU: Setting identity map for device %s [0x%Lx - 0x%Lx]\n",
>  	       pci_name(pdev), start, end);
> +
> +	{
> +		trace_amd_event("Event", 0x1, pdev->devfn, 0, start, 2);
> +		trace_remove_device_from_group(0, &pdev->dev);
> +		trace_attach_device_to_domain(&pdev->dev);
> +		trace_detach_device_from_domain(&pdev->dev);
> +		trace_map(start, end, 1024);
> +		trace_unmap(start, end, 1024);
> +	}

Aren't these parentheses superfluous and
so the indent too deep too?



  parent reply	other threads:[~2013-07-30  1:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30  1:22 Shuah Khan
2013-07-30  1:24 ` Shuah Khan
2013-07-30  1:29 ` Joe Perches [this message]
2013-07-30 14:18   ` Shuah Khan
2013-07-30 14:57 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

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=1375147768.2075.91.camel@joe-AO722 \
    --to=joe@perches.com \
    --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=joro@8bytes.org \
    --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

all inboxes | Powered by JetHome®