From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Noam Camus <noamca@mellanox.com>, Peter Zijlstra <peterz@infradead.org>
Cc: "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
arcml <linux-snps-arc@lists.infradead.org>
Subject: Re: Interesting csd deadlock on ARC
Date: Wed, 24 Feb 2016 10:15:34 +0530 [thread overview]
Message-ID: <56CD356E.3010704@synopsys.com> (raw)
In-Reply-To: <HE1PR05MB162584392E880F4306659593AAA40@HE1PR05MB1625.eurprd05.prod.outlook.com>
On Tuesday 23 February 2016 04:28 PM, Noam Camus wrote:
>> From: Peter Zijlstra [mailto:peterz@infradead.org]
>> Sent: Tuesday, February 23, 2016 12:40 PM
>
>> The only requirement for irq_work is that it runs after the NMI completes and runs from regular IRQ context. >There are no strict interrupt priority requirements, only that it happens.
>
> We here already use self IPI and irq_work on ARC (with no NMI concerns).
> Please see patch at:
> https://github.com/EZchip/linux/commit/e42556738e610295f917c79dae166373cd11de88
So this relies on 2nd level intc providing the IPI.
For UP we still need the software triggered interrupt provided by core intc.
WARNING: multiple messages have this Message-ID (diff)
From: Vineet.Gupta1@synopsys.com (Vineet Gupta)
To: linux-snps-arc@lists.infradead.org
Subject: Interesting csd deadlock on ARC
Date: Wed, 24 Feb 2016 10:15:34 +0530 [thread overview]
Message-ID: <56CD356E.3010704@synopsys.com> (raw)
In-Reply-To: <HE1PR05MB162584392E880F4306659593AAA40@HE1PR05MB1625.eurprd05.prod.outlook.com>
On Tuesday 23 February 2016 04:28 PM, Noam Camus wrote:
>> From: Peter Zijlstra [mailto:peterz at infradead.org]
>> Sent: Tuesday, February 23, 2016 12:40 PM
>
>> The only requirement for irq_work is that it runs after the NMI completes and runs from regular IRQ context. >There are no strict interrupt priority requirements, only that it happens.
>
> We here already use self IPI and irq_work on ARC (with no NMI concerns).
> Please see patch at:
> https://github.com/EZchip/linux/commit/e42556738e610295f917c79dae166373cd11de88
So this relies on 2nd level intc providing the IPI.
For UP we still need the software triggered interrupt provided by core intc.
next prev parent reply other threads:[~2016-02-24 4:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 6:47 Interesting csd deadlock on ARC Vineet Gupta
2016-02-19 6:47 ` Vineet Gupta
2016-02-23 5:21 ` Vineet Gupta
2016-02-23 5:21 ` Vineet Gupta
2016-02-23 9:58 ` Peter Zijlstra
2016-02-23 9:58 ` Peter Zijlstra
2016-02-23 9:58 ` Peter Zijlstra
2016-02-23 10:21 ` Vineet Gupta
2016-02-23 10:21 ` Vineet Gupta
2016-02-23 10:39 ` Peter Zijlstra
2016-02-23 10:39 ` Peter Zijlstra
2016-02-23 10:58 ` Noam Camus
2016-02-23 10:58 ` Noam Camus
2016-02-23 10:58 ` Noam Camus
2016-02-24 4:45 ` Vineet Gupta [this message]
2016-02-24 4:45 ` Vineet Gupta
2016-02-24 4:51 ` Vineet Gupta
2016-02-24 4:51 ` Vineet Gupta
2016-02-25 14:06 ` Peter Zijlstra
2016-02-25 14:06 ` Peter Zijlstra
2016-02-25 14:06 ` Peter Zijlstra
2016-02-25 14:23 ` Vineet Gupta
2016-02-25 14:23 ` Vineet Gupta
2016-02-25 14:30 ` Russell King - ARM Linux
2016-02-25 14:30 ` Russell King - ARM Linux
2016-02-25 15:58 ` Vineet Gupta
2016-02-25 15:58 ` Vineet Gupta
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=56CD356E.3010704@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=fweisbec@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=noamca@mellanox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.