From: Alexander Graf <agraf@suse.de>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: peter.maydell@linaro.org, aik@ozlabs.ru, qemu-devel@nongnu.org,
qemu-ppc@nongnu.org, pbonzini@redhat.com, hw.claudio@gmail.com,
david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH 0/1] pci: allow 0 address for PCI IO/MEM regions
Date: Tue, 13 Jan 2015 18:01:53 +0100 [thread overview]
Message-ID: <54B54F81.1080800@suse.de> (raw)
In-Reply-To: <20150113161756.GA19566@redhat.com>
On 01/13/15 17:17, Michael S. Tsirkin wrote:
> On Tue, Jan 13, 2015 at 05:54:46PM +0200, Michael S. Tsirkin wrote:
>> I think we already do this for PC:
>> commit 83d08f2673504a299194dcac1657a13754b5932a
>> Author: Michael S. Tsirkin <mst@redhat.com>
>> Date: Tue Oct 29 13:57:34 2013 +0100
>>
>> pc: map PCI address space as catchall region for not mapped addresses
>>
>> but we need to find and fix all other targets.
> BTW this is very easy to test.
> Add an unused device (like ivshmem) enable BAR, and set it to 0.
> System should survive, as opposed to hanging.
>
> But the big question is whether this is the right
> thing to do for each platform.
> For PIIX whatever is not system memory, is PCI.
> But other boxes might have a different view of the matter.
Only few platforms have PCI mapped at 0, no? So in most cases you get
windows that simply don't have overlapping at all.
Alex
next prev parent reply other threads:[~2015-01-13 17:02 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
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 [this message]
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=54B54F81.1080800@suse.de \
--to=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=pbonzini@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).