From: Claudio Fontana <claudio.fontana@huawei.com>
To: David Gibson <david@gibson.dropbear.id.au>,
Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: peter.maydell@linaro.org, mst@redhat.com, aik@ozlabs.ru,
qemu-devel@nongnu.org, agraf@suse.de, qemu-ppc@nongnu.org,
hw.claudio@gmail.com
Subject: Re: [Qemu-devel] [PATCH 0/1] pci: allow 0 address for PCI IO/MEM regions
Date: Tue, 13 Jan 2015 10:05:53 +0100 [thread overview]
Message-ID: <54B4DFF1.1030002@huawei.com> (raw)
In-Reply-To: <20150113054655.GK3654@voom.BigPond>
On 13.01.2015 06:46, David Gibson wrote:
> On Mon, Jan 12, 2015 at 07:24:06AM -0600, Michael Roth wrote:
>> Quoting Michael Roth (2014-12-23 13:33:35)
>>> This patch enables the programming of address 0 for IO/MMIO BARs for
>>> PCI devices.
>>>
>>> It was originally included as part of a series implementing PCI
>>> hotplug for pseries guests, where it is needed due to the fact
>>> that pseries guests access IO space via MMIO, and that IO
>>> space is dedicated to PCI devices, with RTAS calls being used in
>>> place of common/legacy IO ports such as config-data/config-address.
>>>
>>> Thus, the entire range is unhindered by legacy IO ports, and
>>> pseries guest kernels may attempt to program an IO BAR to address 0
>>> as a result.
>>>
>>> This has led to a conflict with the existing PCI config space
>>> emulation code, where it has been assumed that 0 address are always
>>> invalid.
>>>
>>> Some background from discussions can be viewed here:
>>>
>>> https://lists.nongnu.org/archive/html/qemu-devel/2014-08/msg03063.html
>>>
>>> The general summary from that discussion seems to be that 0-addresses are
>>> not (at least, are no longer) prohibited by current versions of the PCI
>>> spec, and that the same should apply for MMIO addresses (where allowing
>>> 0-addresses are also needed for some ARM-based PCI controllers).
>>>
>>> This patch includes support for 0-address MMIO BARs based on that
>>> discussion.
>>>
>>> One still-lingering concern is whether this change will impact
>>> compatibility with guests where 0-addresses are invalid. There was
>>> some discussion on whether this issue could be addressed using
>>> memory region priorities, but I think that's still an open question
>>> that we can hopefully address here.
>>
>> Ping
>
> Sorry, I just got back from vacation.
>
> It looks same to me.
>
> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
>
Can you guys take a look also at this:
http://lists.nongnu.org/archive/html/qemu-devel/2015-01/msg01048.html
I really think we should give diagnostics under PCI_DEBUG when trying to set new BAR addresses fails for any reason.
Ciao,
Claudio
next prev parent reply other threads:[~2015-01-13 9:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 19:33 [Qemu-devel] [PATCH 0/1] pci: allow 0 address for PCI IO/MEM regions Michael Roth
2014-12-23 19:33 ` [Qemu-devel] [PATCH] " Michael Roth
2015-01-12 13:24 ` [Qemu-devel] [PATCH 0/1] " Michael Roth
2015-01-13 5:46 ` David Gibson
2015-01-13 9:05 ` Claudio Fontana [this message]
2015-01-13 10:12 ` Michael S. Tsirkin
2015-01-13 15:34 ` Michael Roth
2015-01-13 15:54 ` Michael S. Tsirkin
2015-01-13 16:17 ` Michael S. Tsirkin
2015-01-13 17:01 ` Alexander Graf
2015-01-13 18:42 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54B4DFF1.1030002@huawei.com \
--to=claudio.fontana@huawei.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=hw.claudio@gmail.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).