Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757382AbaAIAlf (ORCPT ); Wed, 8 Jan 2014 19:41:35 -0500 Received: from mga14.intel.com ([143.182.124.37]:25766 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756485AbaAIAlc (ORCPT ); Wed, 8 Jan 2014 19:41:32 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.95,627,1384329600"; d="scan'208";a="455779242" Message-ID: <52CDF037.2070806@linux.intel.com> Date: Thu, 09 Jan 2014 08:41:27 +0800 From: Jiang Liu Organization: Intel User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Yinghai Lu CC: Joerg Roedel , David Woodhouse , Bjorn Helgaas , Dan Williams , Vinod Koul , Ashok Raj , Yijing Wang , Tony Luck , iommu , "linux-pci@vger.kernel.org" , Linux Kernel Mailing List , dmaengine@vger.kernel.org Subject: Re: [Patch Part2 V1 00/14] Enhance DMAR drivers to handle PCI/memory hotplug events References: <1389085234-22296-1-git-send-email-jiang.liu@linux.intel.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2014/1/9 4:43, Yinghai Lu wrote: > On Tue, Jan 7, 2014 at 1:00 AM, Jiang Liu 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/