Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [PATCH v11 8/8] perf: ARM DynamIQ Shared Unit PMU support
To:     Saravana Kannan <skannan@codeaurora.org>,
        Mark Rutland <mark.rutland@arm.com>
Cc:     robh@kernel.org, mathieu.poirier@linaro.org, peterz@infradead.org,
        sudeep.holla@arm.com, will.deacon@arm.com,
        linux-kernel@vger.kernel.org, marc.zyngier@arm.com,
        jonathan.cameron@huawei.com, frowand.list@gmail.com,
        leo.yan@linaro.org, linux-arm-kernel@lists.infradead.org
References: <20180102112533.13640-1-suzuki.poulose@arm.com>
 <20180102112533.13640-9-suzuki.poulose@arm.com>
 <5A90B77E.8040105@codeaurora.org> <20180225143653.peb4quk3ha5h3t5x@salmiak>
 <5A972A7D.9020301@codeaurora.org>
 <20180301114911.fundyuqxtj5klk4e@lakrids.cambridge.arm.com>
 <5A986425.9080007@codeaurora.org>
 <20180302104223.7tpsyhsum7nej237@lakrids.cambridge.arm.com>
 <5A99A3DC.9020400@codeaurora.org>
 <20180305105925.4cjiqejfid7rswe6@lakrids.cambridge.arm.com>
 <5A9DC03B.8020201@codeaurora.org>
From:   Suzuki K Poulose <Suzuki.Poulose@arm.com>
Message-ID: <f340190f-8286-bd3c-c743-79a3d48cc33d@arm.com>
Date:   Wed, 7 Mar 2018 14:59:34 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <5A9DC03B.8020201@codeaurora.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


Hi Saravana,

Sorry for the late response, I was out on vacation.

On 05/03/18 22:10, Saravana Kannan wrote:
> On 03/05/2018 02:59 AM, Mark Rutland wrote:
>> On Fri, Mar 02, 2018 at 11:19:56AM -0800, Saravana Kannan wrote:
>>> On 03/02/2018 02:42 AM, Mark Rutland wrote:
>>>> It's important to note that the DSU PMU's event_init() ensures events
>>>> are affine to a single CPU, and the perf core code serializes operations
>>>> on those events via the context lock.
>>>
>>> Ah, I see that now. Thanks!
>>>
>>>> Therefore, two CPUs *won't* try to access the registers simultaneously.
>>>
>>> Right, and this driver seems to be going through a lot of work to make sure
>>> all events are read in one CPU.
>>>
>>> Do you even have an upstream target where there are multiple DSU's in a
>>> system?
>>
>> I have no idea, though I do beleive that it's possible for a system to
>> have multiple DSUs.
>>
>>> If not, we can simplify a ton of this code (no hotplug notifiers, no
>>> migrating PMUs, no SMP calls, etc) by just adding a spinlock and letting any
>>> CPU read these DSU counters.
>>
>> Regardless of whether we allow arbitrary CPUs to read the counters,
>> other logic still needs to be CPU affine, and we'll still need hotplug
>> notifiers and event migration.
> 
> If you have to support multiple DSUs in a system, then the need is obvious. But if you don't have to support multiple DSU, it's not obvious to me on why you still need CPU affining or hotplug notifiers. Could you please provide me pointers for general understanding?
> 

We need to support multiple DSUs as such configurations are possible.

> 
>> I am not necessarily opposed to allowing read() calls from associated
>> CPUs, but as before, I'll leave that to Suzuki.

I am fine with reading the registers from any of the associated CPUs.

> 
> Can you make sure this thread is on Suzuki's radar?
> 
> Suzuki,
> 
> Could please respond? IPI for DSUs are definitely a pain for us.

Thanks
Suzuki