From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] irqchip: irq-gic: forward SGI to itself for cortex-a7 single core
Date: Tue, 9 Aug 2016 10:30:26 +0100 [thread overview]
Message-ID: <20160809093026.GI1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20160808105026.GA12649@leverpostej>
On Mon, Aug 08, 2016 at 11:50:26AM +0100, Mark Rutland wrote:
> As Russell pointed out in [2], this is a generic infrastructure problem,
> and there are other systems where HW might not have a self-IPI. I note
> that core code already handles that in some cases, e.g. in
> generic_exec_single where we just disable interrupts and run the work
> locally rather than sending a self-IPI.
>
> How/where exactly is this self-IPI raised? Can we follow the example of
> generic_exec_single there?
irq_work_queue_on() calls arch_send_call_function_single_ipi() with
no checks.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-08-09 9:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 7:49 [PATCH 1/1] irqchip: irq-gic: forward SGI to itself for cortex-a7 single core Peter Chen
2016-08-08 10:50 ` Mark Rutland
2016-08-08 12:00 ` Peter Chen
2016-08-08 13:07 ` Mark Rutland
2016-08-08 13:28 ` Peter Chen
2016-08-08 13:48 ` Mark Rutland
2016-08-08 13:59 ` Marc Zyngier
2016-08-09 3:46 ` Peter Chen
2016-08-09 5:34 ` Marc Zyngier
2016-08-09 5:57 ` Peter Chen
2016-08-09 6:59 ` Marc Zyngier
2016-08-09 7:18 ` Peter Chen
2016-08-09 8:54 ` Marc Zyngier
2016-08-09 9:39 ` Peter Chen
2016-08-09 10:08 ` Marc Zyngier
2016-08-09 11:50 ` Peter Chen
2016-08-09 13:03 ` Fabio Estevam
2016-08-16 16:29 ` Fabio Estevam
2016-08-16 16:48 ` Marc Zyngier
2016-08-16 17:03 ` Fabio Estevam
2016-08-16 18:09 ` Fabio Estevam
2016-08-09 9:30 ` Russell King - ARM Linux [this message]
2016-08-08 13:39 ` Marc Zyngier
2016-08-09 3:16 ` Peter Chen
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=20160809093026.GI1041@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--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).