qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wei Xu <wexu2@cisco.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>,
	Anjali Kulkarni <anjali@juniper.net>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] Re: Hitting 29 NIC limit
Date: Wed, 17 Nov 2010 21:41:03 -0800	[thread overview]
Message-ID: <C909FC6F.1A54C%wexu2@cisco.com> (raw)
In-Reply-To: <20101118030918.GA18102@valinux.co.jp>

Isaku,

Could you explain more on irq routing in dsdt and related code in qemu? I
encountered a problem: emulated user networking (-net nic -net user) cannot
work in my qemu-kvm+q35+pcie code. Your original q35 (pure qemu) works fine.

Thanks!
Wei


On 11/17/10 7:09 PM, "Isaku Yamahata" <yamahata@valinux.co.jp> wrote:

> Right now, qemu is internally ready to handle pci-to-pci bridge emulators
> and it's quite easy to add a new simple p2p bridge emulator.
> Just a single function to initialize vid/did and a single PCIDevinceInfo.
> 
> But it's difficult to use multi pci buses at the moment
> because other part isn't ready. It's only for developers
> who are interested in this area.
> 
> BTW, how many pci buses/slots/functions do you want at most?
> 
> 
> What we have in the upstream repository is
> - various fixes for p2p bridge support
> - the library for p2p bridge support
> - pcie root/upstream/downstream port emulators which is p2p bridges
>   ioh3420/xio3130_upstream/xio3130_downstream
> 
> What is missing for multiple pci buses is
> - a new PC machine description which has multiple pci buses
>   My Q35 chipset patch will provide this.
> - a simple P2P bridge emulator for pc architecture
> - seabios support
>   - DSDT for a new machine which has multi pci buses(IRQ routing)
>   - pv pci bus numbering
>     this isn't a must, I suppose
>   I have those patches locally.
> 
> thanks,
> 
> On Wed, Nov 17, 2010 at 12:58:43PM +0200, Michael S. Tsirkin wrote:
>> On Tue, Nov 16, 2010 at 11:20:52AM -0800, Anjali Kulkarni wrote:
>>> Hi,
>>> 
>>> Can you elaborate what you mean by bridge support? I would really like to go
>>> to 256 interfaces.
>>> 
>>> Anjali
>> 
>> Isaku Yamahata wrote most of it, I'll let him comment.
>> 
>> -- 
>> MST
>> 

  reply	other threads:[~2010-11-18  5:41 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1286290127.19619.1398473465@webmail.messagingengine.com>
2010-10-05 15:24 ` [Qemu-devel] Re: 8 NIC limit Dustin Kirkland
     [not found]   ` <1286294888.11462.1398488135@webmail.messagingengine.com>
     [not found]     ` <1286295603.7731.28.camel@x200>
2010-10-06  5:46       ` [Qemu-devel] Re: 8 NIC limit - patch - places limit at 32 linux_kvm
2010-10-06 12:54         ` Anthony Liguori
2010-10-13 22:18         ` [Qemu-devel] Hitting 29 NIC limit (was Re: 8 NIC limit - patch - places limit at 32) Anjali Kulkarni
2010-10-13 22:32           ` [Qemu-devel] Hitting 29 NIC limit Anjali Kulkarni
2010-10-13 22:54             ` Anthony Liguori
2010-10-14 12:07               ` Avi Kivity
2010-10-14 12:10                 ` Daniel P. Berrange
2010-10-14 12:57                   ` Anthony Liguori
2010-10-18 20:07                     ` H. Peter Anvin
2010-10-14 21:42                   ` Richard W.M. Jones
2010-10-14 21:57                     ` Anthony Liguori
2010-10-14 22:00                       ` Anjali Kulkarni
2010-10-14 22:09                         ` Anthony Liguori
2010-10-14 22:12                           ` Anjali Kulkarni
2010-10-14 22:17                             ` Anthony Liguori
2010-11-16 17:23                               ` [Qemu-devel] " Michael S. Tsirkin
2010-11-16 19:00                                 ` Anthony Liguori
2010-10-14 22:08                       ` [Qemu-devel] " Richard W.M. Jones
2010-10-14 12:36                 ` Markus Armbruster
2010-10-14 12:59                   ` Anthony Liguori
2010-10-15  9:11                     ` Markus Armbruster
2010-10-15 18:49                       ` [Qemu-devel] Passing in additional info to guest OS and e1000 test suite? Anjali Kulkarni
2010-10-15 20:02                         ` [Qemu-devel] " Anthony Liguori
2010-10-14 12:54                 ` [Qemu-devel] Hitting 29 NIC limit Anthony Liguori
2010-10-14 13:23                   ` Avi Kivity
2010-10-14 14:11                     ` Anthony Liguori
2010-10-14 14:53                       ` Avi Kivity
2010-11-16 17:21                 ` [Qemu-devel] " Michael S. Tsirkin
     [not found]                   ` <C9081994.3517C%anjali@juniper.net>
     [not found]                     ` <20101117105843.GB10168@redhat.com>
2010-11-18  3:09                       ` Isaku Yamahata
2010-11-18  5:41                         ` Wei Xu [this message]
2010-11-18  6:31                           ` Isaku Yamahata
2010-11-18  6:46                         ` Michael S. Tsirkin
2010-11-18  7:09                           ` Isaku Yamahata
2010-11-18  7:15                             ` Michael S. Tsirkin
2010-11-18  7:27                               ` Isaku Yamahata
2010-11-18 11:54                         ` Gerd Hoffmann
2010-11-18 23:55                           ` Isaku Yamahata

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=C909FC6F.1A54C%wexu2@cisco.com \
    --to=wexu2@cisco.com \
    --cc=anjali@juniper.net \
    --cc=mst@redhat.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).