From: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
To: Kevin O'Connor <kevin@koconnor.net>, Gerd Hoffmann <kraxel@redhat.com>
Cc: seabios@seabios.org, qemu-devel@nongnu.org,
Zihan Yang <whois.zihan.yang@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [SeaBIOS] [RFC v2 0/3] Support multiple pci domains in pci_device
Date: Tue, 28 Aug 2018 20:17:19 +0300 [thread overview]
Message-ID: <ab62fe25-77f4-23d7-74d9-accda67e7a30@gmail.com> (raw)
In-Reply-To: <20180828170203.GA1018@morn.lan>
Hi Kevin,
On 08/28/2018 08:02 PM, Kevin O'Connor wrote:
> On Tue, Aug 28, 2018 at 12:14:58PM +0200, Gerd Hoffmann wrote:
>> Hi,
>>
>>>> Where is the pxb-pcie device? 0000:$somewhere? Or $domain:00:00.0?
>>> 0000:$somewhere (On PCI domain 0)
>> Cool, so we don't have an chicken-and-egg issue.
>>
>>>> If we can access pxb-pcie registers before configuring MMCFG then yes,
>>>> we should use pxb-pcie registers for that.
>>> Yes, we can.
>> Ok, so we can configure mmcfg as hidden pci bar, simliar to the q35
>> mmcfg. Any configuration hints can be passed as pci vendor capability
>> (simliar to the bridge window size hints), if needed.
> Just so I understand, the proposal is to have SeaBIOS search for
> pxb-pcie devices on the main PCI bus and allocate address space for
> each. (These devices would not be considered pci buses in the
> traditional sense.) Then SeaBIOS will traverse that address space
> (MMCFG) and allocate BARs (both address space and io space) for the
> PCI devices found in that address space. Finally, QEMU will take all
> those allocations and use it when generating the ACPI tables.
>
> Did I get that right?
Yes, the pxb-pcie exposes a new PCI root bus, but we want it
in a different PCI domain. This is done in order to remove the
256 PCI Express devices limitation on a PCI Express machine.
Does the plan sounds sane?
Thanks,
Marcel
>
> -Kevin
next prev parent reply other threads:[~2018-08-28 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1533793434-7614-1-git-send-email-whois.zihan.yang@gmail.com>
[not found] ` <ece2a3ff-678d-00b6-3fd6-660972c5beca@gmail.com>
[not found] ` <20180827070406.t525gr43qpu7wpsj@sirius.home.kraxel.org>
2018-08-28 4:12 ` [Qemu-devel] [SeaBIOS] [RFC v2 0/3] Support multiple pci domains in pci_device Zihan Yang
2018-08-28 5:30 ` Gerd Hoffmann
2018-08-28 5:37 ` Marcel Apfelbaum
2018-08-28 6:07 ` Gerd Hoffmann
2018-08-28 6:53 ` Marcel Apfelbaum
2018-08-28 10:14 ` Gerd Hoffmann
2018-08-28 17:02 ` Kevin O'Connor
2018-08-28 17:17 ` Marcel Apfelbaum [this message]
2018-08-28 17:45 ` Kevin O'Connor
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=ab62fe25-77f4-23d7-74d9-accda67e7a30@gmail.com \
--to=marcel.apfelbaum@gmail.com \
--cc=kevin@koconnor.net \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.org \
--cc=whois.zihan.yang@gmail.com \
/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).