From: Laszlo Ersek <lersek@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] q35: fix mmconfig and PCI0._CRS
Date: Mon, 3 Jun 2019 18:23:49 +0200 [thread overview]
Message-ID: <337774a9-e5df-73d8-cf2a-8a173af41157@redhat.com> (raw)
In-Reply-To: <20190603142433.eydpb7vhdj7o7r26@sirius.home.kraxel.org>
On 06/03/19 16:24, Gerd Hoffmann wrote:
> Hi,
>
>> One question: are we sure all guest OSes we care about can deal with
>> discontiguous 32-bit PCI MMIO aperture(s)? Personally, I've got no clue.
>> Is a "naïve" OS imaginable that looks only at the first suitable range
>> in the _CRS?
>
> Well, I know there is physical hardware doing the same thing,
> my work station for example:
>
> [ ... ]
> c8000000-f7ffffff : PCI Bus 0000:00
> c8000000-c81fffff : PCI Bus 0000:01
> e0000000-efffffff : 0000:00:02.0
> e0000000-e02fffff : BOOTFB
> [ ... ]
> f8000000-fbffffff : PCI MMCONFIG 0000 [bus 00-3f]
> f8000000-fbffffff : Reserved
> f8000000-fbffffff : pnp 00:06
> fd000000-fe7fffff : PCI Bus 0000:00
> fd000000-fdabffff : pnp 00:07
> [ ... ]
>
> Which of course is no guarantee that no naïve OS exists, but I think the
> chances that we'll run into trouble with this are rather small.
OK. Thank you.
Laszlo
prev parent reply other threads:[~2019-06-03 16:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 20:43 [Qemu-devel] [PATCH] q35: fix mmconfig and PCI0._CRS Gerd Hoffmann
2019-05-29 4:48 ` Marcel Apfelbaum
2019-05-29 5:01 ` Gerd Hoffmann
2019-05-29 5:11 ` Marcel Apfelbaum
2019-05-29 9:38 ` Paolo Bonzini
2019-05-29 11:16 ` Igor Mammedov
2019-05-29 13:20 ` Gerd Hoffmann
2019-05-29 22:05 ` Michael S. Tsirkin
2019-06-06 13:59 ` Michael S. Tsirkin
2019-05-30 8:58 ` Igor Mammedov
2019-06-03 10:43 ` Laszlo Ersek
2019-06-03 14:24 ` Gerd Hoffmann
2019-06-03 16:23 ` Laszlo Ersek [this message]
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=337774a9-e5df-73d8-cf2a-8a173af41157@redhat.com \
--to=lersek@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.