From: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Zihan Yang <whois.zihan.yang@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, seabios@seabios.org
Subject: Re: [Qemu-devel] [SeaBIOS] [RFC v2 0/3] Support multiple pci domains in pci_device
Date: Tue, 28 Aug 2018 09:53:24 +0300 [thread overview]
Message-ID: <8b232ca6-4643-24c7-d93d-589a452d0785@gmail.com> (raw)
In-Reply-To: <20180828060752.mmsd7x7uobqm2gsr@sirius.home.kraxel.org>
Hi Gerd,
On 08/28/2018 09:07 AM, Gerd Hoffmann wrote:
> Hi,
>
>> Since we will not use all 256 buses of an extra PCI domain,
>> I think this space will allow us to support more PCI domains.
> Depends on the use case I guess. If you just need many pcie devices
> this probably doesn't help. If you want them for numa support then yes,
> more domains with less devices each can be useful then.
We already support multiple NUMA nodes. We want more devices.
Still, having 4x number of devices we previously supported is
a good step forward.
>
>> How will the flow look like ?
>>
>> 1. QEMU passes to SeaBIOS information of how many extra
>> PCI domains needs, and how many buses per domain.
>> How it will pass this info? A vendor specific capability,
>> some PCI registers or modifying extra-pci-roots fw_cfg file?
> Where is the pxb-pcie device? 0000:$somewhere? Or $domain:00:00.0?
0000:$somewhere (On PCI domain 0)
>> 2. SeaBIOS assigns the address for each PCI Domain
>> and
>> returns the information to QEMU.
>> How it will do that? Some pxb-pcie registers? Or do we model
>> the MMCFG like a PCI BAR?
> If we can access pxb-pcie registers before configuring MMCFG then yes,
> we should use pxb-pcie registers for that.
Yes, we can.
Thanks Gerd!
Marcel
>
> cheers,
> Gerd
>
next prev parent reply other threads:[~2018-08-28 6:53 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 [this message]
2018-08-28 10:14 ` Gerd Hoffmann
2018-08-28 17:02 ` Kevin O'Connor
2018-08-28 17:17 ` Marcel Apfelbaum
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=8b232ca6-4643-24c7-d93d-589a452d0785@gmail.com \
--to=marcel.apfelbaum@gmail.com \
--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).