From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Akihiko Odaki" <akihiko.odaki@daynix.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Cédric Le Goater" <clg@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Sriram Yagnaraman" <sriram.yagnaraman@ericsson.com>,
"Jason Wang" <jasowang@redhat.com>,
"Keith Busch" <kbusch@kernel.org>,
"Klaus Jensen" <its@irrelevant.dk>,
"Markus Armbruster" <armbru@redhat.com>,
"Matthew Rosato" <mjrosato@linux.ibm.com>,
"Eric Farman" <farman@linux.ibm.com>,
"Harsh Prateek Bora" <harshpb@linux.ibm.com>,
"Shivaprasad G Bhat" <sbhat@linux.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, devel@daynix.com
Subject: Re: [PATCH v20 06/11] pcie_sriov: Do not manually unrealize
Date: Sun, 16 Feb 2025 19:39:21 +0100 [thread overview]
Message-ID: <249ee391-5e18-43f7-a836-c8ba974f0421@linaro.org> (raw)
In-Reply-To: <20250116-reuse-v20-6-7cb370606368@daynix.com>
On 16/1/25 10:00, Akihiko Odaki wrote:
> A device gets automatically unrealized when being unparented.
Correct, so:
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
However this is totally undocumented, I was not even aware of that...
> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> ---
> hw/pci/pcie_sriov.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/hw/pci/pcie_sriov.c b/hw/pci/pcie_sriov.c
> index e9b23221d713..499becd5273f 100644
> --- a/hw/pci/pcie_sriov.c
> +++ b/hw/pci/pcie_sriov.c
> @@ -204,11 +204,7 @@ static void unregister_vfs(PCIDevice *dev)
> trace_sriov_unregister_vfs(dev->name, PCI_SLOT(dev->devfn),
> PCI_FUNC(dev->devfn), num_vfs);
> for (i = 0; i < num_vfs; i++) {
> - Error *err = NULL;
> PCIDevice *vf = dev->exp.sriov_pf.vf[i];
> - if (!object_property_set_bool(OBJECT(vf), "realized", false, &err)) {
> - error_reportf_err(err, "Failed to unplug: ");
> - }
> object_unparent(OBJECT(vf));
> object_unref(OBJECT(vf));
> }
>
next prev parent reply other threads:[~2025-02-16 18:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 9:00 [PATCH v20 00/11] hw/pci: SR-IOV related fixes and improvements Akihiko Odaki
2025-01-16 9:00 ` [PATCH v20 01/11] hw/ppc/spapr_pci: Do not create DT for disabled PCI device Akihiko Odaki
2025-01-16 9:00 ` [PATCH v20 02/11] hw/ppc/spapr_pci: Do not reject VFs created after a PF Akihiko Odaki
2025-01-16 9:00 ` [PATCH v20 03/11] s390x/pci: Avoid creating zpci for VFs Akihiko Odaki
2025-01-16 9:00 ` [PATCH v20 04/11] s390x/pci: Allow plugging SR-IOV devices Akihiko Odaki
2025-01-16 9:00 ` [PATCH v20 05/11] s390x/pci: Check for multifunction after device realization Akihiko Odaki
2025-01-16 9:00 ` [PATCH v20 06/11] pcie_sriov: Do not manually unrealize Akihiko Odaki
2025-02-16 18:39 ` Philippe Mathieu-Daudé [this message]
2025-01-16 9:00 ` [PATCH v20 07/11] pcie_sriov: Ensure VF addr does not overflow Akihiko Odaki
2025-01-16 9:00 ` [PATCH v20 08/11] pcie_sriov: Reuse SR-IOV VF device instances Akihiko Odaki
2025-01-16 9:01 ` [PATCH v20 09/11] pcie_sriov: Release VFs failed to realize Akihiko Odaki
2025-01-16 9:01 ` [PATCH v20 10/11] pcie_sriov: Remove num_vfs from PCIESriovPF Akihiko Odaki
2025-01-16 9:01 ` [PATCH v20 11/11] pcie_sriov: Register VFs after migration Akihiko Odaki
2025-02-15 6:25 ` [PATCH v20 00/11] hw/pci: SR-IOV related fixes and improvements Akihiko Odaki
2025-02-16 12:26 ` 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=249ee391-5e18-43f7-a836-c8ba974f0421@linaro.org \
--to=philmd@linaro.org \
--cc=akihiko.odaki@daynix.com \
--cc=alex.williamson@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=clg@redhat.com \
--cc=devel@daynix.com \
--cc=eduardo@habkost.net \
--cc=farman@linux.ibm.com \
--cc=harshpb@linux.ibm.com \
--cc=its@irrelevant.dk \
--cc=jasowang@redhat.com \
--cc=kbusch@kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mjrosato@linux.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sbhat@linux.ibm.com \
--cc=sriram.yagnaraman@ericsson.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 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).