From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55206) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VqWLD-0004xG-AF for qemu-devel@nongnu.org; Tue, 10 Dec 2013 18:03:52 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VqWL6-0008IP-Ii for qemu-devel@nongnu.org; Tue, 10 Dec 2013 18:03:46 -0500 Message-ID: <1386716601.32037.83.camel@pasglop> From: Benjamin Herrenschmidt Date: Wed, 11 Dec 2013 10:03:21 +1100 In-Reply-To: References: <1386282785-466-1-git-send-email-mdroth@linux.vnet.ibm.com> <1386282785-466-11-git-send-email-mdroth@linux.vnet.ibm.com> <20131210214239.11040.11449@loki> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v2 10/14] pci: allow 0 address for PCI IO regions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Michael Roth , QEMU Developers , Mike Day , Paul Mackerras , tyreld@linux.vnet.ibm.com, nfont@linux.vnet.ibm.com, "qemu-ppc@nongnu.org" On Tue, 2013-12-10 at 22:14 +0000, Peter Maydell wrote: > Googling again brought up this mailing list thread: > > http://www.pcisig.com/reflector/msg00459.html > > which includes what is supposedly a quote from the PCI 2.1 spec: > > # "Note: A Base Address register does not contain a valid > # address when it is equal to "0"" > > (I don't have access to the 2.1 version to check.) > > This text seems to have been removed from the 2.2 spec. I have seen practical cases of both: - Systems where the FW sets up a BAR to 0 and considers it valid - Adapters that treat a BAR set to 0 as disabled There's no win here. However it makes sense for qemu not to treat 0 as a special value, it's not necessary. Cheers, Ben.