qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
To: Cao jin <caoj.fnst@cn.fujitsu.com>,
	Marcel Apfelbaum <marcel@redhat.com>,
	qemu-devel@nongnu.org
Cc: ehabkost@redhat.com, laine@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH V4] hw/pxb: add chassis_nr property
Date: Thu, 24 Mar 2016 17:34:28 +0200	[thread overview]
Message-ID: <56F40904.7080208@gmail.com> (raw)
In-Reply-To: <56EA80A5.50101@cn.fujitsu.com>

On 03/17/2016 12:02 PM, Cao jin wrote:
> hi
>
> On 03/15/2016 07:44 PM, Marcel Apfelbaum wrote:
>> On 03/15/2016 10:00 AM, Cao jin wrote:
>
>>>
>>> And I have another personal question: In qemu design, it seems every
>>> pci bridge reside in a separate chassis, what`s benefit?  why don`t
>>> put them all in the main chassis?
>>
>> Please have a look on pci-to-pci bridge specification, chapter 13, slot
>> numbering.
>>
>
> thanks for the hint.
> I still have a question: in docs/pci_expander_bridge.txt, it says: create a TYPE_PCI_BRIDGE_DEV to enable hotplug support.
> But I didn`t see it can hotplug as following step:
>
> 1: ./qemu-system-x86_64 -device pxb,id=br,bus=pci.0,bus_nr=2 -hda linux.img -smp 2 --enable-kvm -m 1024 -monitor stdio
>
> 2: in monitor, type: device_add e1000,bus=br
> result: no message output to monitor, and don`t see e1000 nic in guest
>
> Is is a bug or I test it in a wrong way?

Hi,

You used hot-plug correctly, it doesn't work yet since I am still working on this feature.
The bridge gives us the basics environment for hot-plug, what is missing is ACPI "bsel" mechanism.

Thanks,
Marcel

>

  reply	other threads:[~2016-03-24 15:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 14:18 [Qemu-devel] [PATCH V4] hw/pxb: add chassis_nr property Marcel Apfelbaum
2016-03-14 15:21 ` Marcel Apfelbaum
2016-03-15  8:00 ` Cao jin
2016-03-15 11:44   ` Marcel Apfelbaum
2016-03-17 10:02     ` Cao jin
2016-03-24 15:34       ` Marcel Apfelbaum [this message]
2016-03-25  6:28         ` Cao jin

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=56F40904.7080208@gmail.com \
    --to=marcel.apfelbaum@gmail.com \
    --cc=caoj.fnst@cn.fujitsu.com \
    --cc=ehabkost@redhat.com \
    --cc=laine@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).