From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45818)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mdroth@linux.vnet.ibm.com>) id 1ZIOCG-000727-DY
	for qemu-devel@nongnu.org; Thu, 23 Jul 2015 17:38:33 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mdroth@linux.vnet.ibm.com>) id 1ZIOCD-0007gg-56
	for qemu-devel@nongnu.org; Thu, 23 Jul 2015 17:38:32 -0400
Received: from e37.co.us.ibm.com ([32.97.110.158]:57922)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mdroth@linux.vnet.ibm.com>) id 1ZIOCC-0007fW-Sk
	for qemu-devel@nongnu.org; Thu, 23 Jul 2015 17:38:29 -0400
Received: from /spool/local
	by e37.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only!
	Violators will be prosecuted
	for <qemu-devel@nongnu.org> from <mdroth@linux.vnet.ibm.com>;
	Thu, 23 Jul 2015 15:38:28 -0600
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
From: Michael Roth <mdroth@linux.vnet.ibm.com>
In-Reply-To: <CAFEAcA9xX7ra65s06tBs_LH1eOYWj5wxvnrMKP2fYCGuJF5u-A@mail.gmail.com>
References: <1437566099-10004-1-git-send-email-lvivier@redhat.com>
	<1437675858-14070-1-git-send-email-lvivier@redhat.com>
	<1437684406.7562.62.camel@kernel.crashing.org>
	<CAFEAcA-ZY-9EL0PRBFA4oKcND5FH5o6iEGY-VvkcFQSOzukhdg@mail.gmail.com>
	<20150724000923-mutt-send-email-mst@redhat.com>
	<CAFEAcA930MvC+vT3z0uUEixaCMd+e7=F3sCVsf45MTgXKdmamw@mail.gmail.com>
	<CAFEAcA9xX7ra65s06tBs_LH1eOYWj5wxvnrMKP2fYCGuJF5u-A@mail.gmail.com>
Message-ID: <20150723213819.15254.14516@loki>
Date: Thu, 23 Jul 2015 16:38:19 -0500
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v2] pci: allow 0 address for PCI
 IO/MEM regions
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: Peter Maydell <peter.maydell@linaro.org>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: Laurent Vivier <lvivier@redhat.com>, "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>, QEMU Developers <qemu-devel@nongnu.org>, David Gibson <david@gibson.dropbear.id.au>

Quoting Peter Maydell (2015-07-23 16:24:20)
> On 23 July 2015 at 22:19, Peter Maydell <peter.maydell@linaro.org> wrote:
> > On 23 July 2015 at 22:10, Michael S. Tsirkin <mst@redhat.com> wrote:
> >> On Thu, Jul 23, 2015 at 10:00:30PM +0100, Peter Maydell wrote:
> >>> (Also, none of our PCI device models actually try to do
> >>> the "BAR at zero means I won't respond" behaviour, which
> >>> presumably they might do in real life.)
> >
> >> Maybe some devices do this, but I'm guessing not all of them,
> >> since there's no hint in the pci spec that they should.
> >
> > I think this depends on which version of the spec you
> > read.
> =

> Bikeshedding about ancient specs aside, I think it's the
> bugs in the PC model's memory region priorities that
> are the real reason the special case of zero is sticking
> around. If we fixed those we should be able to drop it.

What's the intended fix? That legacy/platform regions
should hide any regions a guest attempts to map over it?

> =

> -- PMM
>=20