From: Paul Mundt <lethal@linux-sh.org>
To: Sundar Iyer <sundar.iyer@intel.com>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
arjan@linux.intel.com, german.monroy@intel.com
Subject: Re: [PATCH v3 1/1] x86/irq: handle chained interrupts during IRQ migration
Date: Mon, 25 Jun 2012 14:31:57 +0900 [thread overview]
Message-ID: <20120625053156.GB24033@linux-sh.org> (raw)
In-Reply-To: <1340596507-12702-1-git-send-email-sundar.iyer@intel.com>
On Mon, Jun 25, 2012 at 09:25:07AM +0530, Sundar Iyer wrote:
> Chained interrupt handlers dont have an irqaction and hence are not
> handled during migrating interrupts when some cores go offline.
>
> Handle this by introducing a irq_is_chained() check which is based
> on the the CHAINED flag being set for such interrupts. fixup_irq()
> can then handle such interrupts and not skip them over.
>
> Signed-off-by: Sundar Iyer <sundar.iyer@intel.com>
> Reviewed-by: Yang, Fei <fei.yang@intel.com>
> Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Looks better to me.
next prev parent reply other threads:[~2012-06-25 5:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 3:55 [PATCH v3 1/1] x86/irq: handle chained interrupts during IRQ migration Sundar Iyer
2012-06-25 5:31 ` Paul Mundt [this message]
2012-07-02 4:22 ` Iyer, Sundar
2012-07-02 9:02 ` Thomas Gleixner
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=20120625053156.GB24033@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=arjan@linux.intel.com \
--cc=german.monroy@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sundar.iyer@intel.com \
--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