From: Alexander Sverdlin <asv@sysgo.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, alexander.sverdlin.ext@nsn.com
Subject: Re: Possible race in request_irq() (__setup_irq())
Date: Mon, 21 May 2012 09:47:29 +0200 [thread overview]
Message-ID: <4FB9F311.9000004@sysgo.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1205161512270.3231@ionos>
Hello Thomas,
On 05/16/2012 03:44 PM, Thomas Gleixner wrote:
> I don't know what your archaeologic kernel version is doing there, but
> the current cavium code only uses handle_percpu_irq flow handler for a
> handful special interrupts which are handled and setup by the cavium
> core code correctly.
>
> So nothing to fix here.
Thanks for clarification!
I'll clean-up all our IRQ code, remove unnecessary PER_CPU flags and drop a note, how it helped.
--
Best regards,
Alexander Sverdlin.
next prev parent reply other threads:[~2012-05-21 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 12:34 Possible race in request_irq() (__setup_irq()) Alexander Sverdlin
2012-05-16 13:44 ` Thomas Gleixner
2012-05-21 7:47 ` Alexander Sverdlin [this message]
2012-05-25 14:01 ` Alexander Sverdlin
2012-05-25 14:22 ` Thomas Gleixner
2012-05-25 16:24 ` David Daney
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=4FB9F311.9000004@sysgo.com \
--to=asv@sysgo.com \
--cc=alexander.sverdlin.ext@nsn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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