lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 23 May 2009 00:41:13 +0800
From:	Weidong Han <weidong.han@...el.com>
To:	mingo@...e.hu, dwmw2@...radead.org, suresh.b.siddha@...el.com
Cc:	linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org,
	kvm@...r.kernel.org, ebiederm@...ssion.com,
	Weidong Han <weidong.han@...el.com>
Subject: [PATCH v3 0/2] Intel-IOMMU: source-id checking for interrupt remapping

Support source-id checking for interrupt remapping, and then
isolates interrupts for guests/VMs with assigned devices.

Eric raised pci rebalance issue with VT-d. Yes, it's an issue now.
Linux needs to handle pci rebalance changes to DRHD scopes. It's
tricky to support it. This patch just supports source-id for
interrupt remapping, won't touch that.

The patchset can be applied on linux-2.6-tip tree.

v2 -> v3 changelog:
	As Ingo suggested, restructured some code and fixed some code
style issues. 	

v1 -> v2 changelog:
        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   |  160 +++++++++++++++++++++++++++++++++++----
 drivers/pci/intr_remapping.h   |    2 +
 include/linux/dmar.h           |   11 +++
 4 files changed, 162 insertions(+), 17 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ