From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: pbonzini@redhat.com, alex.williamson@redhat.com,
qemu-devel@nongnu.org, izumi.taku@jp.fujitsu.com
Subject: Re: [Qemu-devel] [PATCH v3 2/2] remove function during multi-function hot-add
Date: Tue, 13 Oct 2015 17:54:34 +0800 [thread overview]
Message-ID: <561CD4DA.20001@cn.fujitsu.com> (raw)
In-Reply-To: <20151013115045-mutt-send-email-mst@redhat.com>
Hi Michael
On 10/13/2015 04:51 PM, Michael S. Tsirkin wrote:
> On Tue, Oct 13, 2015 at 04:41:35PM +0800, Cao jin wrote:
>> In case user regret when hot-adding multi-function, should roll back,
>> device_del the function added but not exposed to the guest.
>>
>> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
>
> I think this patch should come first, before we enable the
> functionality that depends on it.
>
Do you mean, the function should be removed individually in any
condition? Because as you know, device_del pci_dev will remove all the
functions in the slot that are fulled exposed to the guest, Alex also
mentioned this limitation before.
>
>> ---
>> hw/pci/pci_host.c | 6 +++++-
>> hw/pci/pcie.c | 22 +++++++++++++++++-----
>> 2 files changed, 22 insertions(+), 6 deletions(-)
>>
>> diff --git a/hw/pci/pci_host.c b/hw/pci/pci_host.c
>> index 3e26f92..35e5cf3 100644
>> --- a/hw/pci/pci_host.c
>> +++ b/hw/pci/pci_host.c
>> @@ -20,6 +20,7 @@
>>
>> #include "hw/pci/pci.h"
>> #include "hw/pci/pci_host.h"
>> +#include "hw/pci/pci_bus.h"
>> #include "trace.h"
>>
>> /* debug PCI */
>> @@ -88,10 +89,13 @@ void pci_data_write(PCIBus *s, uint32_t addr, uint32_t val, int len)
>> uint32_t pci_data_read(PCIBus *s, uint32_t addr, int len)
>> {
>> PCIDevice *pci_dev = pci_dev_find_by_addr(s, addr);
>> + PCIDevice *f0 = NULL;
>> uint32_t config_addr = addr & (PCI_CONFIG_SPACE_SIZE - 1);
>> uint32_t val;
>> + uint8_t slot = (addr >> 11) & 0x1F;
>>
>> - if (!pci_dev) {
>> + f0 = s->devices[PCI_DEVFN(slot, 0)];
>> + if (!pci_dev || (!f0 && pci_dev)) {
>> return ~0x0;
>> }
>>
>> diff --git a/hw/pci/pcie.c b/hw/pci/pcie.c
>> index 89bf61b..58d2153 100644
>> --- a/hw/pci/pcie.c
>> +++ b/hw/pci/pcie.c
>> @@ -261,13 +261,30 @@ void pcie_cap_slot_hotplug_cb(HotplugHandler *hotplug_dev, DeviceState *dev,
>> }
>> }
>>
>> +static void pcie_unplug_device(PCIBus *bus, PCIDevice *dev, void *opaque)
>> +{
>> + object_unparent(OBJECT(dev));
>> +}
>> +
>> void pcie_cap_slot_hot_unplug_request_cb(HotplugHandler *hotplug_dev,
>> DeviceState *dev, Error **errp)
>> {
>> uint8_t *exp_cap;
>> + PCIDevice *pci_dev = PCI_DEVICE(dev);
>> + PCIBus *bus = pci_dev->bus;
>>
>> pcie_cap_slot_hotplug_common(PCI_DEVICE(hotplug_dev), dev, &exp_cap, errp);
>>
>> + /* In case user regret when hot-adding multi function, remove the function
>> + * that is unexposed to guest individually, without interaction with guest.
>> + */
>> + if (PCI_FUNC(pci_dev->devfn) > 0 &&
>> + bus->devices[PCI_DEVFN(PCI_SLOT(pci_dev->devfn), 0)] == NULL) {
>> + pcie_unplug_device(bus, pci_dev, NULL);
>> +
>> + return;
>> + }
>> +
>> pcie_cap_slot_push_attention_button(PCI_DEVICE(hotplug_dev));
>> }
>>
>> @@ -378,11 +395,6 @@ void pcie_cap_slot_reset(PCIDevice *dev)
>> hotplug_event_update_event_status(dev);
>> }
>>
>> -static void pcie_unplug_device(PCIBus *bus, PCIDevice *dev, void *opaque)
>> -{
>> - object_unparent(OBJECT(dev));
>> -}
>> -
>> void pcie_cap_slot_write_config(PCIDevice *dev,
>> uint32_t addr, uint32_t val, int len)
>> {
>> --
>> 2.1.0
> .
>
--
Yours Sincerely,
Cao Jin
next prev parent reply other threads:[~2015-10-13 9:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 8:41 [Qemu-devel] [PATCH v3 0/2] PCI-e device multi-function hot-add support Cao jin
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 [this message]
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=561CD4DA.20001@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 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).