From: Jason Chen <jason.cj.chen@intel.com>
To: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, x86@kernel.org
Cc: linux-kernel@vger.kernel.org, Jason Chen <jason.cj.chen@intel.com>
Subject: [RFC PATCH 0/1] add apic_irqs bitmap to identify irqs from apic
Date: Mon, 21 Apr 2014 09:18:26 +0800 [thread overview]
Message-ID: <cover.1397838739.git.jason.cj.chen@intel.com> (raw)
During irq migration, irq_force_complete_move() will consider all irqs coming from apic kind of
irq chip, but they may also coming from other irq chip, such kind of irqs should be filtered out.
Jason Chen (1):
x86/apic: add apic_irqs bitmap to identify irqs from apic
arch/x86/kernel/apic/io_apic.c | 21 ++++++++++++++++++++-
include/linux/irqdesc.h | 6 ++++++
kernel/irq/internals.h | 6 ------
3 files changed, 26 insertions(+), 7 deletions(-)
--
1.8.1.2
next reply other threads:[~2014-04-21 1:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 1:18 Jason Chen [this message]
2014-04-21 1:18 ` [RFC PATCH 1/1] x86/apic: add apic_irqs bitmap to identify irqs from apic Jason Chen
2014-04-24 7:22 ` Ingo Molnar
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=cover.1397838739.git.jason.cj.chen@intel.com \
--to=jason.cj.chen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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