From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: <linux-kernel@vger.kernel.org>,
<iommu@lists.linux-foundation.org>, <joro@8bytes.org>,
<bp@alien8.de>, <mingo@redhat.com>
Subject: Re: [PATCH v8 9/9] perf/amd/iommu: Enable support for multiple IOMMUs
Date: Tue, 7 Feb 2017 08:57:52 +0700 [thread overview]
Message-ID: <af2bca1a-59a9-d36c-a700-ca5360852543@amd.com> (raw)
In-Reply-To: <20170125094653.GO6515@twins.programming.kicks-ass.net>
Peter,
On 1/25/17 16:46, Peter Zijlstra wrote:
> On Mon, Jan 16, 2017 at 01:23:36AM -0600, Suravee Suthikulpanit wrote:
>
>> + pi = container_of(event->pmu, struct perf_amd_iommu, pmu);
>> + hwc->idx = pi->idx;
>> + hwc->config = event->attr.config;
>> + hwc->extra_reg.config = event->attr.config1;
>
>> static void perf_iommu_enable_event(struct perf_event *ev)
>> {
>> + struct hw_perf_event *hwc = &ev->hw;
>> u8 csource = _GET_CSOURCE(ev);
>> u16 devid = _GET_DEVID(ev);
>> u8 bank = _GET_BANK(ev);
>> @@ -253,30 +248,34 @@ static void perf_iommu_enable_event(struct perf_event *ev)
>> u64 reg = 0ULL;
>>
>> reg = csource;
>> - amd_iommu_pc_set_reg(0, bank, cntr,
>> + amd_iommu_pc_set_reg(hwc->idx, bank, cntr,
>> IOMMU_PC_COUNTER_SRC_REG, ®);
>
> Please explain about this IOMMU crud, this looks like fail.
> hwc->idx should be the counter, not a random pmu index.
Ok, I thought this was not used by the code, so I used it for
holding PMU index. This might not be a good idea.
I will change this part per Boris comment in the reply of this
thread.
> But instead it looks like you get the counter form:
>
> #define _GET_CNTR(ev) ((u8)(ev->hw.extra_reg.reg))
>
> Which is absolutely insane.
>
So, the IOMMU counters are grouped into bank, and there could be
many banks. I use the extra_reg.reg to hold the bank and counter
indices. This will be used to program onto the counter configuration
register. This is handled in get_next_avail_iommu_bnk_cntr() and
clear_avail_iommu_bnk_cntr().
Thanks,
Suravee
next prev parent reply other threads:[~2017-02-07 1:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 7:23 [PATCH v8 0/9] perf/amd/iommu: Enable multi-IOMMU support Suravee Suthikulpanit
2017-01-16 7:23 ` [PATCH v8 1/9] perf/amd/iommu: Declare pr_fmt and remove unnecessary pr_debug Suravee Suthikulpanit
2017-01-16 7:23 ` [PATCH v8 2/9] perf/amd/iommu: Clean up perf_iommu_enable_event Suravee Suthikulpanit
2017-01-18 18:20 ` Borislav Petkov
2017-01-16 7:23 ` [PATCH v8 3/9] perf/amd/iommu: Misc fix up perf_iommu_read Suravee Suthikulpanit
2017-01-19 10:01 ` Borislav Petkov
2017-01-23 12:33 ` Peter Zijlstra
2017-02-07 4:50 ` Suravee Suthikulpanit
2017-01-16 7:23 ` [PATCH v8 4/9] iommu/amd: Introduce amd_iommu_get_num_iommus() Suravee Suthikulpanit
2017-01-19 18:41 ` Borislav Petkov
2017-01-16 7:23 ` [PATCH v8 5/9] perf/amd/iommu: Modify functions to query max banks and counters Suravee Suthikulpanit
2017-01-22 19:53 ` Borislav Petkov
2017-01-16 7:23 ` [PATCH v8 6/9] perf/amd/iommu: Modify amd_iommu_pc_get_set_reg_val() API to allow specifying IOMMU index Suravee Suthikulpanit
2017-01-22 19:53 ` Borislav Petkov
2017-01-16 7:23 ` [PATCH v8 7/9] perf/amd/iommu: Check return value when set and get counter value Suravee Suthikulpanit
2017-01-22 19:53 ` Borislav Petkov
2017-01-23 12:31 ` Peter Zijlstra
2017-01-16 7:23 ` [PATCH v8 8/9] perf/amd/iommu: Fix sysfs perf attribute groups Suravee Suthikulpanit
2017-01-22 19:54 ` Borislav Petkov
2017-01-16 7:23 ` [PATCH v8 9/9] perf/amd/iommu: Enable support for multiple IOMMUs Suravee Suthikulpanit
2017-01-22 19:55 ` Borislav Petkov
2017-02-07 1:42 ` Suravee Suthikulpanit
2017-01-25 9:46 ` Peter Zijlstra
2017-01-25 9:55 ` Borislav Petkov
2017-02-07 1:58 ` Suravee Suthikulpanit
2017-02-07 1:57 ` Suravee Suthikulpanit [this message]
2017-02-14 12:31 ` Peter Zijlstra
2017-02-23 17:43 ` Suravee Suthikulpanit
2017-02-23 18:11 ` Peter Zijlstra
2017-02-23 18:20 ` Suravee Suthikulpanit
2017-01-17 15:36 ` [PATCH v8 0/9] perf/amd/iommu: Enable multi-IOMMU support 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=af2bca1a-59a9-d36c-a700-ca5360852543@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
all inboxes | Powered by JetHome®