From: Weidong Han <weidong.han@intel.com>
To: mingo@elte.hu, dwmw2@infradead.org, suresh.b.siddha@intel.com
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
kvm@vger.kernel.org, Weidong Han <weidong.han@intel.com>
Subject: [PATCH v2 0/2] Intel-IOMMU: source-id checking for interrupt remapping
Date: Wed, 20 May 2009 02:31:50 +0800 [thread overview]
Message-ID: <1242757912-6041-1-git-send-email-weidong.han@intel.com> (raw)
Support source-id checking for interrupt remapping, and then
isolates interrupts for guests/VMs with assigned devices.
v1 -> v2 change log:
Access PCI directly (read_pci_config_byte) to parse IOAPIC,
instead of PCI related discovery, because PCI subsystem is not
initialized at that time.
Weidong Han (2):
Intel-IOMMU, intr-remap: set the whole 128bits of irte when
modify/free it
Intel-IOMMU, intr-remap: source-id checking
arch/x86/kernel/apic/io_apic.c | 6 ++
drivers/pci/intr_remapping.c | 100 +++++++++++++++++++++++++++++++++++++--
drivers/pci/intr_remapping.h | 2 +
include/linux/dmar.h | 11 ++++
4 files changed, 113 insertions(+), 6 deletions(-)
next reply other threads:[~2009-05-19 10:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 18:31 Weidong Han [this message]
2009-05-19 18:31 ` [PATCH v2 1/2] Intel-IOMMU, intr-remap: set the whole 128bits of irte when modify/free it Weidong Han
2009-05-19 12:14 ` Ingo Molnar
2009-05-19 14:15 ` Han, Weidong
2009-05-19 18:31 ` [PATCH v2 2/2] Intel-IOMMU, intr-remap: source-id checking Weidong Han
2009-05-19 11:50 ` Ingo Molnar
2009-05-19 14:12 ` Han, Weidong
2009-05-19 19:28 ` Eric W. Biederman
2009-05-20 8:21 ` Ingo Molnar
2009-05-20 8:38 ` Han, Weidong
2009-05-20 12:13 ` Eric W. Biederman
2009-05-20 9:43 ` Joerg Roedel
2009-05-20 12:02 ` Eric W. Biederman
2009-05-20 12:24 ` Eric W. Biederman
2009-05-21 9:00 ` Han, Weidong
2009-05-21 10:04 ` Eric W. Biederman
2009-05-21 13:37 ` Han, Weidong
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=1242757912-6041-1-git-send-email-weidong.han@intel.com \
--to=weidong.han@intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@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;
as well as URLs for NNTP newsgroup(s).