From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:57891)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jan.kiszka@siemens.com>) id 1R491b-00034O-Bh
	for qemu-devel@nongnu.org; Thu, 15 Sep 2011 06:18:32 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jan.kiszka@siemens.com>) id 1R491a-0001AO-9e
	for qemu-devel@nongnu.org; Thu, 15 Sep 2011 06:18:31 -0400
Received: from goliath.siemens.de ([192.35.17.28]:28565)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jan.kiszka@siemens.com>) id 1R491Z-000188-Ts
	for qemu-devel@nongnu.org; Thu, 15 Sep 2011 06:18:30 -0400
Message-ID: <4E71D0F1.9020805@siemens.com>
Date: Thu, 15 Sep 2011 12:18:25 +0200
From: Jan Kiszka <jan.kiszka@siemens.com>
MIME-Version: 1.0
References: <CAAu8pHvpbYBuOKa6Krsd6R00qidBx+J6ObaqZT40zuYh+SZn9g@mail.gmail.com>
	<4E6DAA09.1050701@twiddle.net> <4E6DCA61.4070009@siemens.com>
	<4E6DCCC4.1050201@redhat.com> <4E6DCE8D.9040602@siemens.com>
	<4E70C402.3090907@twiddle.net> <4E70EB39.4010101@siemens.com>
	<4E70EDFF.4000008@siemens.com> <4E70FF6A.8050401@redhat.com>
	<4E71C5BF.7050409@siemens.com> <4E71CB19.2010605@redhat.com>
In-Reply-To: <4E71CB19.2010605@redhat.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH] memory: simple memory tree printer
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: Avi Kivity <avi@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>, Richard Henderson <rth@twiddle.net>

On 2011-09-15 11:53, Avi Kivity wrote:
>>>   The host pci bridge remaps this as
>>>  0x1000000105-0x1000000106 in the memory address space space.  But
>>>  someone configured a cpu-local region at this address, so the cpu can't
>>>  reach it at all.
>>
>> Mapping PIO into MMIO space is special as it needs an intermediate layer
>> (ie. translation handlers).
> 
> Translation handlers aren't needed - you can simply add the pci pio 
> region as a subregion of the mmio space.

>>From the outer perspective. But internally, there is still
memory_region_iorange_read/write.

The point is that no use case actually justifies memory_region_set_offset.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux