From: Alex Williamson <alex.williamson@redhat.com>
To: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
Cc: izumi.taku@jp.fujitsu.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC v8.1 01/13] vfio: extract vfio_get_hot_reset_info as a single function
Date: Wed, 27 May 2015 15:31:34 -0600 [thread overview]
Message-ID: <1432762294.24271.90.camel@redhat.com> (raw)
In-Reply-To: <b469c4d6b2d55d0724f90a4b40bab0390678ca0b.1432694455.git.chen.fan.fnst@cn.fujitsu.com>
On Wed, 2015-05-27 at 10:46 +0800, Chen Fan wrote:
> the function is used to get affected devices by bus reset.
> so here extract it, and can used for aer soon.
>
> Signed-off-by: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
> ---
> hw/vfio/pci.c | 67 +++++++++++++++++++++++++++++++++++++++++++----------------
> 1 file changed, 49 insertions(+), 18 deletions(-)
>
> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
> index e0e339a..9c05304 100644
> --- a/hw/vfio/pci.c
> +++ b/hw/vfio/pci.c
> @@ -2641,6 +2641,50 @@ static void vfio_check_af_flr(VFIOPCIDevice *vdev, uint8_t pos)
> }
> }
>
> +/*
> + * return negative with errno, return 0 on success.
> + * if success, the point of ret_info fill with the affected device reset info.
> + *
> + */
> +static int vfio_get_hot_reset_info(VFIOPCIDevice *vdev,
> + struct vfio_pci_hot_reset_info **ret_info)
> +{
> + struct vfio_pci_hot_reset_info *info;
> + int ret, count;
> +
> + *ret_info = NULL;
> +
> + info = g_malloc0(sizeof(*info));
> + info->argsz = sizeof(*info);
> +
> + ret = ioctl(vdev->vbasedev.fd, VFIO_DEVICE_GET_PCI_HOT_RESET_INFO, info);
> + if (ret && errno != ENOSPC) {
> + ret = -errno;
> + goto error;
> + }
> +
> + count = info->count;
> +
> + info = g_realloc(info, sizeof(*info) +
> + (count * sizeof(struct vfio_pci_dependent_device)));
> + info->argsz = sizeof(*info) +
> + (count * sizeof(struct vfio_pci_dependent_device));
> +
> + ret = ioctl(vdev->vbasedev.fd, VFIO_DEVICE_GET_PCI_HOT_RESET_INFO, info);
> + if (ret) {
> + ret = -errno;
> + goto error;
> + }
> +
> + *ret_info = info;
> + info = NULL;
> +
> + ret = 0;
Just return 0 here.
> +error:
> + g_free(info);
> + return ret;
> +}
> +
> static int vfio_add_std_cap(VFIOPCIDevice *vdev, uint8_t pos)
> {
> PCIDevice *pdev = &vdev->pdev;
> @@ -2780,7 +2824,7 @@ static bool vfio_pci_host_match(PCIHostDeviceAddress *host1,
> static int vfio_pci_hot_reset(VFIOPCIDevice *vdev, bool single)
> {
> VFIOGroup *group;
> - struct vfio_pci_hot_reset_info *info;
> + struct vfio_pci_hot_reset_info *info = NULL;
> struct vfio_pci_dependent_device *devices;
> struct vfio_pci_hot_reset *reset;
> int32_t *fds;
> @@ -2792,32 +2836,19 @@ static int vfio_pci_hot_reset(VFIOPCIDevice *vdev, bool single)
> vfio_pci_pre_reset(vdev);
> vdev->vbasedev.needs_reset = false;
>
> - info = g_malloc0(sizeof(*info));
> - info->argsz = sizeof(*info);
> -
> - ret = ioctl(vdev->vbasedev.fd, VFIO_DEVICE_GET_PCI_HOT_RESET_INFO, info);
> - if (ret && errno != ENOSPC) {
> - ret = -errno;
> + ret = vfio_get_hot_reset_info(vdev, &info);
> + if (ret) {
> if (!vdev->has_pm_reset) {
> error_report("vfio: Cannot reset device %04x:%02x:%02x.%x, "
> "no available reset mechanism.", vdev->host.domain,
> vdev->host.bus, vdev->host.slot, vdev->host.function);
> + } else {
> + error_report("vfio: hot reset info failed: %m");
What if we pass through a root complex device where we can't do a bus
reset. With this change, we get this useless error_report every time we
come through this path. There are cases where this is not an error and
should not be reported to the user.
> }
> goto out_single;
> }
>
> - count = info->count;
> - info = g_realloc(info, sizeof(*info) + (count * sizeof(*devices)));
> - info->argsz = sizeof(*info) + (count * sizeof(*devices));
> devices = &info->devices[0];
> -
> - ret = ioctl(vdev->vbasedev.fd, VFIO_DEVICE_GET_PCI_HOT_RESET_INFO, info);
> - if (ret) {
> - ret = -errno;
> - error_report("vfio: hot reset info failed: %m");
> - goto out_single;
> - }
> -
> trace_vfio_pci_hot_reset_has_dep_devices(vdev->vbasedev.name);
>
> /* Verify that we have all the groups required */
next prev parent reply other threads:[~2015-05-27 21:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 2:46 [Qemu-devel] [RFC v8.1 00/13] vfio-pci: pass the aer error to guest Chen Fan
2015-05-27 2:46 ` [Qemu-devel] [RFC v8.1 01/13] vfio: extract vfio_get_hot_reset_info as a single function Chen Fan
2015-05-27 21:31 ` Alex Williamson [this message]
2015-05-27 2:46 ` [Qemu-devel] [RFC v8.1 03/13] vfio: add pcie extanded capability support Chen Fan
2015-05-27 21:31 ` Alex Williamson
2015-05-27 2:46 ` [Qemu-devel] [RFC v8.1 04/13] aer: impove pcie_aer_init to support vfio device Chen Fan
2015-05-27 2:46 ` [Qemu-devel] [RFC v8.1 05/13] vfio: add aer support for " Chen Fan
2015-05-27 21:32 ` Alex Williamson
2015-05-27 2:46 ` [Qemu-devel] [RFC v8.1 06/13] vfio: add check host bus reset is support or not Chen Fan
2015-05-27 21:32 ` Alex Williamson
2015-06-02 7:54 ` Chen Fan
2015-06-02 16:47 ` Alex Williamson
2015-06-03 0:52 ` Chen Fan
2015-06-04 15:59 ` Alex Williamson
2015-06-09 3:43 ` Chen Fan
2015-05-27 2:46 ` [Qemu-devel] [RFC v8.1 07/13] vfio: add check for vfio devices which enable aer should support bus reset Chen Fan
2015-05-27 21:32 ` Alex Williamson
2015-05-27 2:46 ` [Qemu-devel] [RFC v8.1 08/13] pci: add bus reset_notifiers callbacks for host " Chen Fan
2015-05-27 2:46 ` [Qemu-devel] [RFC v8.1 09/13] vfio: add sec_bus_reset notifier to notify physical bus reset is needed Chen Fan
2015-05-27 21:32 ` Alex Williamson
2015-05-27 2:46 ` [Qemu-devel] [RFC v8.1 10/13] vfio: do hot bus reset when do virtual secondary bus reset Chen Fan
2015-05-27 21:33 ` Alex Williamson
[not found] ` <557020F1.7070705@cn.fujitsu.com>
2015-06-04 16:06 ` Alex Williamson
2015-05-27 2:46 ` [Qemu-devel] [RFC v8.1 11/13] pcie_aer: expose pcie_aer_msg() interface Chen Fan
2015-05-27 2:46 ` [Qemu-devel] [RFC v8.1 12/13] vfio-pci: pass the aer error to guest Chen Fan
2015-05-27 21:33 ` Alex Williamson
2015-05-27 2:46 ` [Qemu-devel] [RFC v8.1 13/13] vfio: add 'aer' property to expose aercap Chen Fan
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=1432762294.24271.90.camel@redhat.com \
--to=alex.williamson@redhat.com \
--cc=chen.fan.fnst@cn.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.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).