From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:36332)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1YxBvD-0001Nl-Ih
	for qemu-devel@nongnu.org; Tue, 26 May 2015 06:17:20 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1YxBvC-0006Dn-Mp
	for qemu-devel@nongnu.org; Tue, 26 May 2015 06:17:19 -0400
Message-ID: <55644819.3000003@redhat.com>
Date: Tue, 26 May 2015 12:16:57 +0200
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <1429964684-23872-1-git-send-email-aik@ozlabs.ru>
	<1429964684-23872-7-git-send-email-aik@ozlabs.ru>
	<55633A54.8080807@ozlabs.ru>
	<20150526024628.GA30620@voom.redhat.com>
	<5564359A.2070009@redhat.com> <556447BB.9000802@ozlabs.ru>
In-Reply-To: <556447BB.9000802@ozlabs.ru>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH qemu v7 06/14] spapr_iommu: Introduce
 "enabled" state for TCE table
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, David Gibson <david@gibson.dropbear.id.au>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>, Alex Williamson <alex.williamson@redhat.com>, qemu-ppc@nongnu.org, qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>



On 26/05/2015 12:15, Alexey Kardashevskiy wrote:
> There was a "[RFC PATCH 00/15] spapr: add support for PHB hotplug"
> patchset from Mike, this patch added "unrealize" for spapr_phb:
> 
> [RFC PATCH 05/15] spapr_pci: add PHB unrealize
> 
> I believe I am dealing with the fixed version of this patch so I'll ask
> Mike to respin it.
> 
> 
>>
>>> So, the sentences after that one note an exception for alias and
>>> container regions.  I think iommu regions should behave similarly
>>> - in a sense they're just a procedurally generated collection of
>>> alias regions.
>>
>> The difference is that containers and aliases are resolved at the time
>> the memory region tree is flattened, while IOMMU regions are resolved
>> at run time.
> 
> So they are not parts of flattened view and I should be able to
> add/remove these IOMMU subregions any time I like?

Yes.

Paolo