From: anurupvasu@gmail.com (Anurup M)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 08/11] drivers: perf: hisi: use poll method to avoid L3C counter overflow
Date: Tue, 21 Feb 2017 12:37:33 +0530 [thread overview]
Message-ID: <58ABE735.2010708@gmail.com> (raw)
In-Reply-To: <20170220110942.GF9003@leverpostej>
Adding Marc.
On Monday 20 February 2017 04:39 PM, Mark Rutland wrote:
> On Sun, Feb 19, 2017 at 01:51:03PM -0500, Anurup M wrote:
>> The L3 cache PMU use N-N SPI interrupt which has no support
>> in kernel mainline.
> Could you elaborate on what you mean by this?
>
> I don't understand what is meant here. How exactly are the interrupts
> wired up in HW, and what exactly is not supported by Linux?
In HW the L3C overflow IRQ is wired as SPI which use N-N model.
But according to ARM GIC V2 specification, the peripheral(hardware)
interrupts should use 1-N model.
N-N model is used by SGIs. In GIC V3 spec I could not find any
description of N-N model.
So I think the N-N model for SPI will not be supported.
Hi Marc,
Does ARM GIC support N-N module for SPI? Please share your comments.
>> So use hrtimer to poll and update event
>> counter to avoid overflow condition for L3 cache PMU.
>> A interval of 10 seconds is used for the hrtimer.
>> The time interval can be configured in the sysfs.
> I'm not too keen on giving userspace the ability to control this, since
> it gives an awful lot of rope for userspace to tie around itself.
I thought of giving facility to system user to decide the interval based
on the system usage.
If we do not provide this facility, then we always set the worst case
overflow interval?
I am trying to understand it better.
Thanks,
Anurup
> Thanks,
> Mark.
next prev parent reply other threads:[~2017-02-21 7:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 18:51 [PATCH v4 08/11] drivers: perf: hisi: use poll method to avoid L3C counter overflow Anurup M
2017-02-20 11:09 ` Mark Rutland
2017-02-21 7:07 ` Anurup M [this message]
2017-02-21 9:43 ` Marc Zyngier
2017-02-21 12:09 ` Will Deacon
2017-02-24 3:11 ` Anurup M
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=58ABE735.2010708@gmail.com \
--to=anurupvasu@gmail.com \
--cc=linux-arm-kernel@lists.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).