From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: <linux-snps-arc@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] ARCv2: entry: Reduce perf intr return path
Date: Tue, 21 Nov 2017 15:26:32 -0800 [thread overview]
Message-ID: <64e093da-1778-f1ea-9eae-a1c2ce29556d@synopsys.com> (raw)
In-Reply-To: <4a28d9dc-b322-1a79-b1d1-c13db2f01ee7@synopsys.com>
On 11/17/2017 03:42 PM, Vineet Gupta wrote:
>>>> What do you (on ARC) do about irq_work ?
>>>
>
>> So the reason I'm asking is that some architectures that don't have NMIs
>> call irq_work_run() at the very end of their perf-interrupt handler (ARM
>> does this for instance).
>
> But on ARC, we don't call irq_work_run() in perf intr return path and that seem to
> imply it is broken - as in latency to service a perf induced preemption.
[snip...]
>>> Although I'm sure it is, can you please explain how irq_work is relevant in
>>> the context of this patch.
>>
>> Since the perf interrupt (in general) cannot call a whole lot of things
>> for it needs to assume running from NMI context, it needs to defer
>> things to a more regular context. It does this with irq_work.
So given my understanding of this topic, ARC (or any non NMI based perf intr
system) is potentially broken without irq_work_run() ?
I can follow up with a patch for ARC, or does this need to addressed for others
too - say irq_exit_perf() or some such ?
next prev parent reply other threads:[~2017-11-21 23:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 22:13 [PATCH 0/4] ARC perf updates Vineet Gupta
2017-11-07 22:13 ` [PATCH 1/4] ARCv2: perf: tweak overflow interrupt Vineet Gupta
2017-11-07 22:13 ` [PATCH 2/4] ARCv2: perf: optimize given that num counters <= 32 Vineet Gupta
2017-11-07 22:13 ` [PATCH 3/4] ARC: perf: avoid vmalloc backed mmap Vineet Gupta
2017-11-07 22:13 ` [PATCH 4/4] ARCv2: entry: Reduce perf intr return path Vineet Gupta
2017-11-14 10:28 ` Peter Zijlstra
2017-11-14 23:01 ` Vineet Gupta
2017-11-15 10:18 ` Peter Zijlstra
2017-11-17 23:42 ` Vineet Gupta
2017-11-21 23:26 ` Vineet Gupta [this message]
2017-11-13 21:30 ` [PATCH 0/4] ARC perf updates Vineet Gupta
2017-11-21 22:09 ` Vineet Gupta
2017-11-21 23:13 ` Peter Zijlstra
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=64e093da-1778-f1ea-9eae-a1c2ce29556d@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--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