From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59784)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <imammedo@redhat.com>) id 1ZKRLD-00061B-HF
	for qemu-devel@nongnu.org; Wed, 29 Jul 2015 09:24:16 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <imammedo@redhat.com>) id 1ZKRL8-0007Tq-Oc
	for qemu-devel@nongnu.org; Wed, 29 Jul 2015 09:24:15 -0400
Received: from mx1.redhat.com ([209.132.183.28]:52220)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <imammedo@redhat.com>) id 1ZKRL8-0007Ti-JH
	for qemu-devel@nongnu.org; Wed, 29 Jul 2015 09:24:10 -0400
Date: Wed, 29 Jul 2015 15:24:06 +0200
From: Igor Mammedov <imammedo@redhat.com>
Message-ID: <20150729152406.13f3608d@nial.brq.redhat.com>
In-Reply-To: <017601d0c9f6$63027e70$29077b50$@samsung.com>
References: <015a01d0c85c$b52b61d0$1f822570$@samsung.com>
	<20150729111055.2bf307ac@nial.brq.redhat.com>
	<00f501d0c9e3$b3d19380$1b74ba80$@samsung.com>
	<20150729135914.0beab8c8@nial.brq.redhat.com>
	<017601d0c9f6$63027e70$29077b50$@samsung.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH v3] hw/arm/virt: Add high MMIO PCI region
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: Pavel Fedin <p.fedin@samsung.com>
Cc: 'Peter Maydell' <peter.maydell@linaro.org>, pbonzini@redhat.com, 'Alexander Graf' <agraf@suse.de>, 'QEMU Developers' <qemu-devel@nongnu.org>

On Wed, 29 Jul 2015 15:02:00 +0300
Pavel Fedin <p.fedin@samsung.com> wrote:

>  Hello!
> 
> > I don't suggest to have something mapped on top of the window,
> > Suggestion was to just use the same value for
> > AddressMaximum and AddressMinimum arguments in aml_qword_memory() call.
> 
>  And this will shrink the region down to zero, right? For what reason? Physical region would still
> be there (here we imagine this is a real HW).
nope, it won't shrink anything. It will prevent OS from potential
relocation of region.

AddressMaximum is a max possible BASE address of range,
I read 'base address' as starting address of range and
it has nothing to do with the size.

See spec, ACPI6.0: 19.6.104 QWordMemory

> 
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia
> 
>