From: Joerg Roedel <joerg.roedel@amd.com>
To: <iommu@lists.linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Alex Williamson <alex.williamson@redhat.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Yinghai Lu <yinghai@kernel.org>
Subject: [RFC PATCH 0/9] Introduce irq_remap_ops to x86
Date: Thu, 15 Mar 2012 18:39:42 +0100 [thread overview]
Message-ID: <1331833191-25779-1-git-send-email-joerg.roedel@amd.com> (raw)
Hi,
in order to implement interrupt remapping using the AMD IOMMU I did some
refactoring of the current Intel-specific interrupt remapping code. The
result is posted for comments in this patch-set.
The patch-set basically removes the Intel-specific calls from the X86
apic and io-apic code and replaces all of them with helper functions
that use the irq_remap_ops to hook into an implementation specific
implementation.
I have done basic testing on this patch-set on a VT-d machine with
interrupt remapping and found no regression so far. But as usual this
doesn't mean that there is none ;-)
Anyway, since I am on vacation soon I sent out these patches to receive
all kinds of comments so that I can start over to add the AMD part when
I am back.
Thanks,
Joerg
Diffstat:
arch/ia64/include/asm/intr_remapping.h | 4 +
arch/x86/include/asm/intr_remapping.h | 101 +++
arch/x86/include/asm/irq_remapping.h | 45 --
arch/x86/kernel/apic/apic.c | 20 +-
arch/x86/kernel/apic/io_apic.c | 276 ++-------
drivers/iommu/Makefile | 2 +-
drivers/iommu/amd_iommu_init.c | 123 +++--
drivers/iommu/dmar.c | 1 +
drivers/iommu/intel-iommu.c | 1 +
drivers/iommu/intel_intr_remapping.c | 1065 ++++++++++++++++++++++++++++++++
drivers/iommu/intr_remapping.c | 810 +++----------------------
drivers/iommu/intr_remapping.h | 97 +++-
include/linux/amd-iommu.h | 2 +-
include/linux/dmar.h | 85 ---
14 files changed, 1469 insertions(+), 1163 deletions(-)
next reply other threads:[~2012-03-15 17:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 17:39 Joerg Roedel [this message]
2012-03-15 17:39 ` [PATCH 1/9] iommu/amd: Split amd_iommu_init function Joerg Roedel
2012-03-15 17:39 ` [PATCH 2/9] iommu: Rename intr_remapping files to intel_intr_remapping Joerg Roedel
2012-03-15 17:39 ` [PATCH 3/9] iommu/vt-d: Make intr-remapping initialization generic Joerg Roedel
2012-03-15 17:39 ` [PATCH 4/9] iommu/vt-d: Convert missing apic.c intr-remapping call to remap_ops Joerg Roedel
2012-03-15 17:39 ` [PATCH 5/9] iommu/vt-d: Convert IR ioapic-setup to use remap_ops Joerg Roedel
2012-03-15 17:39 ` [PATCH 6/9] iommu/vt-d: Convert IR set_affinity function to remap_ops Joerg Roedel
2012-03-15 17:39 ` [PATCH 7/9] iommu/vt-d: Convert free_irte into a remap_ops callback Joerg Roedel
2012-03-15 17:39 ` [PATCH 8/9] iommu/vt-d: Convert MSI remapping setup to remap_ops Joerg Roedel
2012-03-15 17:39 ` [PATCH 9/9] x86, iommu/vt-d: Clean up interfaces for interrupt remapping Joerg Roedel
2012-03-15 18:04 ` [RFC PATCH 0/9] Introduce irq_remap_ops to x86 Yinghai Lu
2012-03-15 19:52 ` Joerg Roedel
2012-03-16 0:51 ` Yinghai Lu
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=1331833191-25779-1-git-send-email-joerg.roedel@amd.com \
--to=joerg.roedel@amd.com \
--cc=alex.williamson@redhat.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=yinghai@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
Powered by JetHome