From: Markus Armbruster <armbru@redhat.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: qemu-devel@nongnu.org, paul@codesourcery.com,
mtosatti@redhat.com, Avi Kivity <avi@redhat.com>,
mst@redhat.com
Subject: Re: [Qemu-devel] Re: [PATCH 7/7] [RFC] pci bus: preliminary for multi pci bus support.
Date: Tue, 02 Jun 2009 15:03:59 +0200 [thread overview]
Message-ID: <871vq2bxds.fsf@pike.pond.sub.org> (raw)
In-Reply-To: <20090602074600.GG9176%yamahata@valinux.co.jp> (Isaku Yamahata's message of "Tue\, 2 Jun 2009 16\:46\:00 +0900")
Isaku Yamahata <yamahata@valinux.co.jp> writes:
> On Tue, Jun 02, 2009 at 10:13:19AM +0300, Avi Kivity wrote:
>> Isaku Yamahata wrote:
>> >This patch is preliminary for multi pci bus support to
>> >add -pci option.
>> >
>>
>> What is the motivation for this work?
>
> -pci might be too generic. -pci_bridge or something else might be
> better. I think, eventually they would be replaced with config file work.
> So this option isn't so important.
To make use of this code, we need a way to create PCI bridges. If we
can't have an option, maybe we could create bridges as needed, just like
we create SCSI controllers. But I don't like that at all.
I wouldn't advise waiting for completion of the config file stuff.
> The short term motivation is 128+ pci slot support.
Sorely needed, in my opinion.
> I know Markus has tried on kvm before and was rejected because
> of scalability. As he also wants it, I'm willing to collaborate with him.
>
> The long term motivation is to support MMCFG and PCIe port emulator,
> then eventually PCIe native direct attach support including
> PCIe native functionality like AER.
> This requires more newer chipset emulation than piix and more.
Good stuff.
next prev parent reply other threads:[~2009-06-02 13:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 6:42 [Qemu-devel] [PATCH 0/7] pci bridge clean up and multiple pci bus support v2 Isaku Yamahata
2009-06-02 6:42 ` [Qemu-devel] [PATCH 1/7] vmware_vga: clean up Isaku Yamahata
2009-06-10 15:08 ` [Qemu-devel] " Michael S. Tsirkin
2009-06-02 6:42 ` [Qemu-devel] [PATCH 2/7] qemu: make default_write_config use mask table Isaku Yamahata
2009-06-02 6:42 ` [Qemu-devel] [PATCH 3/7] pci: pci_default_config_write() clean up Isaku Yamahata
2009-06-02 10:01 ` [Qemu-devel] " Michael S. Tsirkin
2009-06-03 2:31 ` Isaku Yamahata
2009-06-03 7:22 ` Michael S. Tsirkin
2009-06-03 12:25 ` Isaku Yamahata
2009-06-05 10:43 ` Michael S. Tsirkin
2009-06-10 15:48 ` Michael S. Tsirkin
2009-06-15 9:12 ` Isaku Yamahata
2009-06-15 10:42 ` Michael S. Tsirkin
2009-06-02 6:42 ` [Qemu-devel] [PATCH 4/7] pci/config: convert pci configuration space handler to use callback Isaku Yamahata
2009-06-10 15:16 ` [Qemu-devel] " Michael S. Tsirkin
2009-06-02 6:42 ` [Qemu-devel] [PATCH 5/7] pci: PCIBus clean up Isaku Yamahata
2009-06-02 6:42 ` [Qemu-devel] [PATCH 6/7] pci/brdige qdevfy Isaku Yamahata
2009-06-02 6:42 ` [Qemu-devel] [PATCH 7/7] [RFC] pci bus: preliminary for multi pci bus support Isaku Yamahata
2009-06-02 7:13 ` [Qemu-devel] " Avi Kivity
2009-06-02 7:46 ` Isaku Yamahata
2009-06-02 8:51 ` Avi Kivity
2009-06-02 13:03 ` Markus Armbruster [this message]
2009-06-02 12:56 ` [Qemu-devel] " Markus Armbruster
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=871vq2bxds.fsf@pike.pond.sub.org \
--to=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/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).