From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: gic: use handle_fasteoi_irq for SPIs
Date: Wed, 16 Feb 2011 13:09:10 -0000 [thread overview]
Message-ID: <000201cbcdda$b36ada00$1a408e00$@deacon@arm.com> (raw)
In-Reply-To: <AANLkTik-0SaVbtiXZ-iefvvgLq=7KqRTGi7XPLPEKx85@mail.gmail.com>
Hi Rabin,
> On Mon, Feb 14, 2011 at 20:56, Will Deacon <will.deacon@arm.com> wrote:
> > Currently, the gic uses handle_level_irq for handling SPIs (Shared
> > Peripheral Interrupts), requiring active interrupts to be masked at
> > the distributor level during IRQ handling.
> >
> > On a virtualised system, only the CPU interfaces are virtualised in
> > hardware. Accesses to the distributor must be trapped by the hypervisor,
> > adding latency to the critical interrupt path in Linux.
> >
> > This patch modifies the GIC code to use handle_fasteoi_irq for handling
> > interrupts, which only requires us to signal EOI to the CPU interface
> > when handling is complete. Cascaded IRQ handling is also updated so that
> > EOI is signalled after handling.
>
> Several of the platforms using the GIC also have GPIO code which uses
> set_irq_chained_handler(). I think you will have to modify all of
> these to call irq_eoi() appropriately and not the other functions.
> Some of these will also likely be used with other interrupt handlers
> than the GIC, though.
Hmm, I had a quick look at some platforms that do this (mach-dove and
plat-spear) and I don't see what the problem is. They use their own irq_chip
structures, with their own function pointers, so this doesn't seem to relate
to the GIC at all. What am I missing?!
Cheers,
Will
next prev parent reply other threads:[~2011-02-16 13:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 15:26 [PATCH] ARM: gic: use handle_fasteoi_irq for SPIs Will Deacon
2011-02-16 11:29 ` Rabin Vincent
2011-02-16 13:09 ` Will Deacon [this message]
[not found] ` <-4413647205110644369@unknownmsgid>
2011-02-16 14:05 ` Rabin Vincent
2011-02-16 16:17 ` Will Deacon
[not found] ` <146267380211262372@unknownmsgid>
2011-02-16 17:35 ` Rabin Vincent
2011-02-16 19:20 ` Thomas Gleixner
2011-02-17 9:17 ` Russell King - ARM Linux
2011-02-17 9:38 ` Thomas Gleixner
2011-02-17 10:19 ` Russell King - ARM Linux
2011-02-17 10:43 ` Thomas Gleixner
2011-02-17 10:56 ` Russell King - ARM Linux
2011-02-17 11:21 ` Thomas Gleixner
2011-02-17 16:26 ` Will Deacon
2011-02-17 17:34 ` Thomas Gleixner
2011-02-17 23:38 ` Abhijeet Dharmapurikar
2011-02-18 11:29 ` Will Deacon
2011-02-18 11:42 ` Thomas Gleixner
2011-02-18 12:09 ` Will Deacon
[not found] ` <-8083923411736601789@unknownmsgid>
2011-02-18 18:30 ` Colin Cross
2011-02-18 18:36 ` Santosh Shilimkar
2011-02-18 18:57 ` Will Deacon
-- strict thread matches above, loose matches on Subject: below --
2011-02-10 12:29 Will Deacon
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='000201cbcdda$b36ada00$1a408e00$@deacon@arm.com' \
--to=will.deacon@arm.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).