From: Michael Roth <mdroth@linux.vnet.ibm.com>
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>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v2] pci: allow 0 address for PCI IO/MEM regions
Date: Thu, 23 Jul 2015 16:38:19 -0500 [thread overview]
Message-ID: <20150723213819.15254.14516@loki> (raw)
In-Reply-To: <CAFEAcA9xX7ra65s06tBs_LH1eOYWj5wxvnrMKP2fYCGuJF5u-A@mail.gmail.com>
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
>
next prev parent reply other threads:[~2015-07-23 21:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1437566099-10004-1-git-send-email-lvivier@redhat.com>
2015-07-23 18:24 ` [Qemu-devel] [PATCH v2] pci: allow 0 address for PCI IO/MEM regions Laurent Vivier
2015-07-23 18:30 ` Michael S. Tsirkin
2015-07-23 20:48 ` [Qemu-devel] [Qemu-ppc] " Benjamin Herrenschmidt
2015-07-23 21:18 ` Michael S. Tsirkin
2015-07-23 20:46 ` Benjamin Herrenschmidt
2015-07-23 21:00 ` Peter Maydell
2015-07-23 21:10 ` Michael S. Tsirkin
2015-07-23 21:19 ` Peter Maydell
2015-07-23 21:24 ` Peter Maydell
2015-07-23 21:38 ` Michael Roth [this message]
2015-07-23 21:49 ` Michael Roth
2015-07-24 8:46 ` Peter Maydell
2015-07-24 8:58 ` Laurent Vivier
2015-07-23 21:46 ` Benjamin Herrenschmidt
2015-07-23 22:42 ` Michael S. Tsirkin
2015-07-24 8:35 ` [Qemu-devel] [PATCH v3] " Laurent Vivier
2015-07-27 8:19 ` [Qemu-devel] [Qemu-ppc] " Laurent Vivier
2015-08-06 8:08 ` Laurent Vivier
2015-08-11 8:50 ` Alexander Graf
2015-08-11 9:04 ` Laurent Vivier
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=20150723213819.15254.14516@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.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).