linux-kernel - Re: [Patch Part2 V1 00/14] Enhance DMAR drivers to handle PCI/memory hotplug events

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <52CDF037.2070806@linux.intel.com>
Date:	Thu, 09 Jan 2014 08:41:27 +0800
From:	Jiang Liu <jiang.liu@...ux.intel.com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	Joerg Roedel <joro@...tes.org>,
	David Woodhouse <dwmw2@...radead.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Dan Williams <dan.j.williams@...el.com>,
	Vinod Koul <vinod.koul@...el.com>,
	Ashok Raj <ashok.raj@...el.com>,
	Yijing Wang <wangyijing@...wei.com>,
	Tony Luck <tony.luck@...el.com>,
	iommu <iommu@...ts.linux-foundation.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	dmaengine@...r.kernel.org
Subject: Re: [Patch Part2 V1 00/14] Enhance DMAR drivers to handle PCI/memory
 hotplug events



On 2014/1/9 4:43, Yinghai Lu wrote:
> On Tue, Jan 7, 2014 at 1:00 AM, Jiang Liu <jiang.liu@...ux.intel.com> wrote:
>> Intel DMA/interrupt remapping drivers scan available PCI/memory devices
>> at startup and cache discovered hardware topologies. They don't update
>> cached information if PCI/memory hotplug event happens at runtime, then
>> the stale information may break DMA/interrupt remapping logic.
>>
>> This patchset first (Patch 1-8) tries to introduces some helper
>> functions and fixes several bugs, then (Patch 9,10) uses a global
>> rwsem and RCU to protect global DMA/interrupt remapping data
>> structures, and finally (Patch 11-14) hook PCI/memory hotplug events
>> to update cached information.
>>
>> It's also a preparation for supporting of DMA/interrupt remapping
>> hotplug.
>>
>> Jiang Liu (14):
>>   iommu/vt-d: factor out dmar_alloc_dev_scope() for later reuse
>>   iommu/vt-d: move private structures and variables into intel-iommu.c
>>   iommu/vt-d: simplify function get_domain_for_dev()
>>   iommu/vt-d: free resources if failed to create domain for PCIe
>>     endpoint
>>   iommu/vt-d: create device_domain_info structure for intermediate P2P
>>     bridges
>>   iommu/vt-d: fix incorrect iommu_count for si_domain
>>   iommu/vt-d: fix error in detect ATS capability
>>   iommu/vt-d: introduce macro for_each_dev_scope() to walk device scope
>>     entries
>>   iommu/vt-d: introduce a rwsem to protect global data structures
>>   iommu/vt-d: use RCU to protect global resources in interrupt context
>>   iommu/vt-d, PCI: update DRHD/RMRR/ATSR device scope caches when PCI
>>     hotplug happens
>>   iommu/vt-d, PCI: unify the way to process DMAR device scope array
>>   iommu/vt-d: update device to static identity domain mapping for PCI
>>     hotplug
>>   iommu/vt-d: update IOMMU state when memory hotplug happens
>>
>>  drivers/iommu/dmar.c                |  412 +++++++++++++++++--------
>>  drivers/iommu/intel-iommu.c         |  583 +++++++++++++++++++++--------------
>>  drivers/iommu/intel_irq_remapping.c |  108 ++++---
>>  include/linux/dmar.h                |   75 +++--
>>  4 files changed, 753 insertions(+), 425 deletions(-)
> 
> 
> Hi, Jiang,
> 
> What is relationship between your two patchset with my iommu hotplug patchset?
> 
> https://lkml.org/lkml/2014/1/2/527
> 
> or yours will just replace mine?
Hi Yinghai,
	I have reviewed your v2 patch set, I think we are doing the
same task. If you agree, I will try to combine our two versions.

Thanks!
Gerry
> 
> Thanks
> 
> Yinghai
> 
--
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/