qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 v9 09/18] vfio: add ref for group to support own affected groups
Date: Tue, 09 Jun 2015 15:23:08 -0600	[thread overview]
Message-ID: <1433884988.4927.144.camel@redhat.com> (raw)
In-Reply-To: <271aa9f9c26213c43241c44273a18109af505223.1433812962.git.chen.fan.fnst@cn.fujitsu.com>

On Tue, 2015-06-09 at 11:37 +0800, Chen Fan wrote:
> Signed-off-by: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
> ---
>  hw/vfio/common.c              | 12 ++++++++++++
>  include/hw/vfio/vfio-common.h |  1 +
>  2 files changed, 13 insertions(+)
> 
> diff --git a/hw/vfio/common.c b/hw/vfio/common.c
> index 4230f83..eff1930 100644
> --- a/hw/vfio/common.c
> +++ b/hw/vfio/common.c
> @@ -832,6 +832,7 @@ VFIOGroup *vfio_get_group(int groupid, AddressSpace *as)
>          goto close_fd_exit;
>      }
>  
> +    group->ref = 0;
>      group->groupid = groupid;
>      QLIST_INIT(&group->device_list);
>  
> @@ -865,6 +866,15 @@ void vfio_put_group(VFIOGroup *group)
>          return;
>      }
>  
> +    if (group->ref) {
> +        if (QLIST_EMPTY(&group->device_list)) {
> +            if (group->container) {
> +                vfio_disconnect_container(group);
> +            }
> +        }
> +        return;
> +    }

Once we disconnect the container, our file descriptor for the group
isn't sufficient for a bus reset.

> +
>      vfio_kvm_device_del_group(group);
>      if (group->container) {
>          vfio_disconnect_container(group);
> @@ -901,6 +911,7 @@ int vfio_get_device(VFIOGroup *group, const char *name,
>          return ret;
>      }
>  
> +    group->ref++;
>      vbasedev->fd = fd;
>      vbasedev->group = group;
>      QLIST_INSERT_HEAD(&group->device_list, vbasedev, next);
> @@ -921,6 +932,7 @@ void vfio_put_base_device(VFIODevice *vbasedev)
>      if (!vbasedev->group) {
>          return;
>      }
> +    vbasedev->group->ref--;
>      QLIST_REMOVE(vbasedev, next);
>      vbasedev->group = NULL;
>      trace_vfio_put_base_device(vbasedev->fd);
> diff --git a/include/hw/vfio/vfio-common.h b/include/hw/vfio/vfio-common.h
> index 0d1fb80..3eb042e 100644
> --- a/include/hw/vfio/vfio-common.h
> +++ b/include/hw/vfio/vfio-common.h
> @@ -117,6 +117,7 @@ struct VFIODeviceOps {
>  typedef struct VFIOGroup {
>      int fd;
>      int groupid;
> +    int ref;
>      VFIOContainer *container;
>      QLIST_HEAD(, VFIODevice) device_list;
>      QLIST_ENTRY(VFIOGroup) next;

  reply	other threads:[~2015-06-09 21:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09  3:37 [Qemu-devel] [RFC v9 00/18] vfio-pci: pass the aer error to guest Chen Fan
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 01/18] vfio: extract vfio_get_hot_reset_info as a single function Chen Fan
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 02/18] vfio: squeeze out vfio_pci_do_hot_reset for support bus reset Chen Fan
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 03/18] pcie: modify the capability size assert Chen Fan
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 04/18] vfio: make the 4 bytes aligned for capability size Chen Fan
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 05/18] vfio: add pcie extanded capability support Chen Fan
2015-06-09 21:22   ` Alex Williamson
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 06/18] aer: impove pcie_aer_init to support vfio device Chen Fan
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 07/18] vfio: add aer support for " Chen Fan
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 08/18] vfio: improve vfio_get_group to support adding group without devices Chen Fan
2015-06-09 21:23   ` Alex Williamson
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 09/18] vfio: add ref for group to support own affected groups Chen Fan
2015-06-09 21:23   ` Alex Williamson [this message]
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 10/18] get all affected groups for each device support aer Chen Fan
2015-06-09 21:22   ` Alex Williamson
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 11/18] vfio: add check host bus reset is support or not Chen Fan
2015-06-09 21:23   ` Alex Williamson
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 12/18] pci: add bus reset_notifiers callbacks for host bus reset Chen Fan
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 13/18] vfio: add sec_bus_reset notifier to notify physical bus reset is needed Chen Fan
2015-06-09 21:23   ` Alex Williamson
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 14/18] vfio: improve vfio_pci_hot_reset to support more case Chen Fan
2015-06-09 21:24   ` Alex Williamson
2015-06-16  8:10     ` Chen Fan
2015-06-16 14:08       ` Alex Williamson
2015-06-17  6:28         ` Chen Fan
2015-06-17 15:23           ` Alex Williamson
2015-06-18 10:27             ` Chen Fan
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 15/18] vfio: do hot bus reset when do virtual secondary bus reset Chen Fan
2015-06-09 21:23   ` Alex Williamson
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 16/18] pcie_aer: expose pcie_aer_msg() interface Chen Fan
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 17/18] vfio-pci: pass the aer error to guest Chen Fan
2015-06-09  3:37 ` [Qemu-devel] [RFC v9 18/18] 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=1433884988.4927.144.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).