linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: <linux-kernel@vger.kernel.org>,
	<iommu@lists.linux-foundation.org>, <joro@8bytes.org>,
	<peterz@infradead.org>, <mingo@redhat.com>
Subject: Re: [PATCH v7 7/7] perf/amd/iommu: Enable support for multiple IOMMUs
Date: Sat, 14 Jan 2017 09:58:29 +0700	[thread overview]
Message-ID: <46834d61-d8b2-201f-99dd-5727994281a5@amd.com> (raw)
In-Reply-To: <20170113114925.x6f4r5qcidksnfes@pd.tnic>



On 1/13/17 18:49, Borislav Petkov wrote:
> On Fri, Jan 13, 2017 at 05:24:01PM +0700, Suravee Suthikulpanit wrote:
>> IIUC, Perf tools looks at the /sys/devices/xxxxx to identify
>> availalble PMUs. Are you planning to have perf tools look at
>> /sys/devices/system/iommu/xxx instead?
>
> No, I'm planning to understand what do you mean exactly. Because the
> PMUs are, as I'm being pointed to, here:
>
> #define EVENT_SOURCE_DEVICE_PATH "/bus/event_source/devices/"
>
> Do you mean that, per chance?
>

Ah, okay. I can see the following directory path:

# ls -l  /sys/devices/
drwxr-xr-x  5 root root 0 Jan 13 20:36 amd_iommu_0

# ls -l /sys/bus/event_source/devices/
lrwxrwxrwx 1 root root 0 Jan 13 20:33 amd_iommu_0 -> ../../../devices/amd_iommu_0

I'll update the commit log to mention /bus/event_source/devices/amd_iommu_X instead.

Thanks,
S

  reply	other threads:[~2017-01-14  2:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10  3:33 [PATCH v7 0/7] perf/amd/iommu: Enable multi-IOMMU support Suravee Suthikulpanit
2017-01-10  3:33 ` [PATCH v7 1/7] perf/amd/iommu: Misc fix up perf_iommu_read Suravee Suthikulpanit
2017-01-11 10:32   ` Borislav Petkov
2017-01-11 11:57   ` Peter Zijlstra
2017-01-15  2:36     ` Suravee Suthikulpanit
2017-01-19 10:14       ` Peter Zijlstra
2017-01-10  3:33 ` [PATCH v7 2/7] perf/amd/iommu: Modify functions to query max banks and counters Suravee Suthikulpanit
2017-01-10 14:43   ` Joerg Roedel
2017-01-11  3:03     ` Suravee Suthikulpanit
2017-01-11  8:13       ` Boris Petkov
2017-01-11  9:14         ` Suravee Suthikulpanit
2017-01-10  3:33 ` [PATCH v7 3/7] perf/amd/iommu: Modify IOMMU API to allow specifying IOMMU index Suravee Suthikulpanit
2017-01-11 17:23   ` Borislav Petkov
2017-01-10  3:33 ` [PATCH v7 4/7] perf/amd/iommu: Declare pr_fmt and remove unnecessary pr_debug Suravee Suthikulpanit
2017-01-12 10:19   ` Borislav Petkov
2017-01-14 10:13     ` Suravee Suthikulpanit
2017-01-10  3:33 ` [PATCH v7 5/7] perf/amd/iommu: Clean up perf_iommu_enable_event Suravee Suthikulpanit
2017-01-12 14:14   ` Borislav Petkov
2017-01-10  3:33 ` [PATCH v7 6/7] iommu/amd: Introduce amd_iommu_get_num_iommus() Suravee Suthikulpanit
2017-01-12 14:21   ` Borislav Petkov
2017-01-10  3:33 ` [PATCH v7 7/7] perf/amd/iommu: Enable support for multiple IOMMUs Suravee Suthikulpanit
2017-01-12 17:52   ` Borislav Petkov
2017-01-13 10:24     ` Suravee Suthikulpanit
2017-01-13 11:49       ` Borislav Petkov
2017-01-14  2:58         ` Suravee Suthikulpanit [this message]
2017-01-14 10:29           ` Borislav Petkov

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=46834d61-d8b2-201f-99dd-5727994281a5@amd.com \
    --to=suravee.suthikulpanit@amd.com \
    --cc=bp@alien8.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).