From: Thomas Gleixner <tglx@linutronix.de>
To: Sundar Iyer <sundar.iyer@intel.com>
Cc: linux-kernel@vger.kernel.org, arjan.van.de.ven@intel.com,
german.monroy@intel.com
Subject: Re: [PATCH v1] x86/irq: handle chained interrupts during IRQ migration
Date: Thu, 31 May 2012 09:30:52 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1205310930030.3231@ionos> (raw)
In-Reply-To: <1338298808-2265-1-git-send-email-sundar.iyer@intel.com>
On Tue, 29 May 2012, 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 IRQ_NOREQUEST flag being set for such interrupts. fixup_irq()
> can then handle such interrupts and not skip them over.
No, we need a separate flag for those. IRQ_NORREQUEST is not a
reliable indicator.
Thanks,
tglx
next prev parent reply other threads:[~2012-05-31 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 13:40 [PATCH v1] x86/irq: handle chained interrupts during IRQ migration Sundar Iyer
2012-05-30 2:55 ` Paul Mundt
2012-05-31 7:30 ` Thomas Gleixner [this message]
2012-05-31 7:36 ` Iyer, Sundar
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=alpine.LFD.2.02.1205310930030.3231@ionos \
--to=tglx@linutronix.de \
--cc=arjan.van.de.ven@intel.com \
--cc=german.monroy@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sundar.iyer@intel.com \
/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