From: "Michael S. Tsirkin" <mst@redhat.com>
To: Heyi Guo <guoheyi@huawei.com>
Cc: qemu-devel@nongnu.org,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
wanghaibin 00208455 <wanghaibin.wang@huawei.com>
Subject: Re: [Qemu-devel] Question: can we hot plug a PCIe switch on machine "virt"
Date: Wed, 3 Apr 2019 14:50:27 -0400 [thread overview]
Message-ID: <20190403144550-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <f3a469aa-4a18-a8be-3a37-8989401e2db7@huawei.com>
On Wed, Apr 03, 2019 at 03:32:09PM +0800, Heyi Guo wrote:
> Hi folks,
>
> In physical world, a PCIe switch including one upstream port and several downstream ports is a single physical device, however we treat each port as a device in qemu world. In qemu docs/pcie.txt, we have below statements:
>
> Line 230: Be aware that PCI Express Downstream Ports can't be hot-plugged into
> Line 231: an existing PCI Express Upstream Port.
>
> To my understanding, it implies PCIe downstream ports *can* be hot-plugged into something which is not an existing upstream port. If it is true, how can we do that? AFAIK monitor command device_add can only add one device at a time.
>
> Please help to show the truth.
>
> Thanks,
>
> Heyi
>
afaik they can only be plugged into upstearm ports with or without hotplug.
--
mst
next prev parent reply other threads:[~2019-04-03 18:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 7:32 [Qemu-devel] Question: can we hot plug a PCIe switch on machine "virt" Heyi Guo
2019-04-03 18:50 ` Michael S. Tsirkin [this message]
2019-04-04 7:39 ` Auger Eric
2019-04-07 1:59 ` Heyi Guo
2019-04-11 11:30 ` Heyi Guo
2019-04-11 12:19 ` Auger Eric
2019-04-12 2:02 ` Heyi Guo
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=20190403144550-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=guoheyi@huawei.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=wanghaibin.wang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.