From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, alex.williamson@redhat.com,
izumi.taku@jp.fujitsu.com, mst@redhat.com
Subject: [Qemu-devel] [PATCH v3 0/2] PCI-e device multi-function hot-add support
Date: Tue, 13 Oct 2015 16:41:33 +0800 [thread overview]
Message-ID: <1444725695-27517-1-git-send-email-caoj.fnst@cn.fujitsu.com> (raw)
Support PCI-e device hot-add multi-function via device_add, just ensure
add the function 0 is added last. While allow user to roll back in the
middle via device_del, in case user regret.
changelog:
1. Flag device as unexposed when func 0 doesn`t exist, via return 0xFF
in case of gratuitous pci bus scan.
2. Since device is unexposed to guest, can remove function individually,
without interaction with the guest.
Cao jin (2):
enable multi-function hot-add
remove function during multi-function hot-add
hw/pci/pci.c | 10 ++++++++++
hw/pci/pci_host.c | 6 +++++-
hw/pci/pcie.c | 38 +++++++++++++++++++++++++-------------
3 files changed, 40 insertions(+), 14 deletions(-)
--
2.1.0
next reply other threads:[~2015-10-13 8:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 8:41 Cao jin [this message]
2015-10-13 8:41 ` [Qemu-devel] [PATCH v3 1/2] enable multi-function hot-add Cao jin
2015-10-13 8:41 ` [Qemu-devel] [PATCH v3 2/2] remove function during " Cao jin
2015-10-13 8:48 ` [Qemu-devel] [PATCH RFC] hw/virtio: Add PCIe capability to virtio devices Michael S. Tsirkin
2015-10-13 12:19 ` Cao jin
2015-10-13 8:51 ` [Qemu-devel] [PATCH v3 2/2] remove function during multi-function hot-add Michael S. Tsirkin
2015-10-13 9:54 ` Cao jin
2015-10-13 10:21 ` Michael S. Tsirkin
2015-10-13 15:27 ` Alex Williamson
2015-10-14 5:46 ` Cao jin
2015-10-13 8:49 ` [Qemu-devel] [PATCH v3 0/2] PCI-e device multi-function hot-add support Michael S. Tsirkin
2015-10-13 11:54 ` Cao jin
2015-10-13 13:10 ` Michael S. Tsirkin
2015-10-14 5:48 ` Cao jin
2015-10-21 8:32 ` Cao jin
2015-10-21 9:11 ` Michael S. Tsirkin
2015-10-13 8:50 ` Michael S. Tsirkin
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=1444725695-27517-1-git-send-email-caoj.fnst@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=alex.williamson@redhat.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=mst@redhat.com \
--cc=pbonzini@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 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.