From: Weidong Han <weidong.han@intel.com>
To: mingo@elte.hu, dwmw2@infradead.org, allen.m.kay@intel.com,
fenghua.yu@intel.com
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
Weidong Han <weidong.han@intel.com>
Subject: [PATCH 0/5] fix bugs of x2apic/intr-remap
Date: Fri, 17 Apr 2009 16:42:11 +0800 [thread overview]
Message-ID: <1239957736-6161-1-git-send-email-weidong.han@intel.com> (raw)
interupt remapping was decoupled from x2apic already, but there are still
some issues, such as doesn't ack remapped interrupts correctly, and doesn't
remap ioapic interrupt when x2apic is not enabled.
This patchset fixes the ack for remapped interrupts, and alwasys enables
interrupt remapping before ioapic setup to guarantee ioapic interrupts are
remapped, adjusts the dependency of x2apic and interrupt remapping in
lapic_resume. In addition, add option "nointremap" to disable interrupt
remapping.
The patchset can be applied on linux head. Thanks.
Weidong Han (5):
docs: add nox2apic back to kernel-parameters.txt
x86,intr-remap: fix ack for interrupt remapping
x86, intr-remap: enable interrupt remapping early
x86, intr-remap: add option to disable interrupt remapping
x86: fix x2apic/intr-remap resume
Documentation/kernel-parameters.txt | 5 ++
arch/x86/include/asm/apic.h | 15 +-----
arch/x86/kernel/apic/apic.c | 91 +++++++++++++++++------------------
arch/x86/kernel/apic/io_apic.c | 32 ++----------
drivers/pci/intel-iommu.c | 9 ----
drivers/pci/intr_remapping.c | 39 ++++++++++-----
include/linux/dmar.h | 1 +
7 files changed, 84 insertions(+), 108 deletions(-)
next reply other threads:[~2009-04-17 8:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 8:42 Weidong Han [this message]
2009-04-17 8:42 ` [PATCH 1/5] docs: add nox2apic back to kernel-parameters.txt Weidong Han
2009-04-17 13:51 ` Ingo Molnar
2009-04-17 14:48 ` [tip:x86/apic] docs, x86: " tip-bot for Weidong Han
2009-04-18 7:31 ` [tip:x86/urgent] " tip-bot for Weidong Han
2009-04-19 8:24 ` [tip:x86/apic] " tip-bot for Weidong Han
2009-04-17 8:42 ` [PATCH 2/5] x86,intr-remap: fix ack for interrupt remapping Weidong Han
2009-04-17 14:49 ` [tip:x86/apic] x86, intr-remap: " tip-bot for Weidong Han
2009-04-19 8:25 ` tip-bot for Weidong Han
2009-04-17 8:42 ` [PATCH 3/5] x86, intr-remap: enable interrupt remapping early Weidong Han
2009-04-17 14:13 ` Ingo Molnar
2009-04-17 23:42 ` Suresh Siddha
2009-04-18 7:24 ` Ingo Molnar
2009-04-17 14:49 ` [tip:x86/apic] " tip-bot for Weidong Han
2009-04-19 8:25 ` tip-bot for Weidong Han
2009-04-17 8:42 ` [PATCH 4/5] x86, intr-remap: add option to disable interrupt remapping Weidong Han
2009-04-17 14:49 ` [tip:x86/apic] " tip-bot for Weidong Han
2009-04-19 8:25 ` tip-bot for Weidong Han
2009-04-17 8:42 ` [PATCH 5/5] x86: fix x2apic/intr-remap resume Weidong Han
2009-04-17 14:15 ` Ingo Molnar
2009-04-17 14:49 ` [tip:x86/apic] x86, intr-remap: " tip-bot for Weidong Han
2009-04-19 8:25 ` tip-bot for Weidong Han
2009-04-17 14:30 ` [PATCH 0/5] fix bugs of x2apic/intr-remap Ingo Molnar
2009-04-17 14:41 ` Ingo Molnar
2009-04-18 3:07 ` Han, Weidong
2009-04-18 6:41 ` Ingo Molnar
2009-04-19 6:32 ` David Woodhouse
2009-04-19 8: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=1239957736-6161-1-git-send-email-weidong.han@intel.com \
--to=weidong.han@intel.com \
--cc=allen.m.kay@intel.com \
--cc=dwmw2@infradead.org \
--cc=fenghua.yu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome