public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Bandan Das <bsd@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] vfio: Set PCI_DEV_FLAGS_ASSIGNED when assigning device to guest
Date: Thu, 30 Jan 2014 10:33:45 -0700	[thread overview]
Message-ID: <1391103225.6959.71.camel@bling.home> (raw)
In-Reply-To: <jpgeh3ppelz.fsf@redhat.com>

On Thu, 2014-01-30 at 22:54 +0530, Bandan Das wrote:
> Some drivers such as ixgbe rely on pci_vfs_assigned() to prevent
> disabling sr-iov when vfs are still assigned during hotplug
> event or module removal. Set and unset PCI_DEV_FLAGS_ASSIGNED
> appropriately

This flag has always felt like a band-aide for KVM device assignment
because a device could be used without an actual driver attached to the
device.  vfio-pci is an actual driver, so why should it matter whether
the device is assigned or in use by ixgbevf or in use by pci-vfio?  It
seems like sr-iov shouldn't be disabled so long as either a driver or
this (needs to be deprecated) flag are set.  Thanks,

Alex

> ---
>  drivers/vfio/pci/vfio_pci.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/vfio/pci/vfio_pci.c b/drivers/vfio/pci/vfio_pci.c
> index 7ba0424..7cc7ed6 100644
> --- a/drivers/vfio/pci/vfio_pci.c
> +++ b/drivers/vfio/pci/vfio_pci.c
> @@ -90,6 +90,7 @@ static int vfio_pci_enable(struct vfio_pci_device *vdev)
>  		vdev->has_vga = true;
>  #endif
>  
> +	pdev->dev_flags |= PCI_DEV_FLAGS_ASSIGNED;
>  	return 0;
>  }
>  
> @@ -149,6 +150,7 @@ static void vfio_pci_disable(struct vfio_pci_device *vdev)
>  				__func__, dev_name(&pdev->dev), ret);
>  	}
>  
> +	pdev->dev_flags &= ~PCI_DEV_FLAGS_ASSIGNED;
>  	pci_restore_state(pdev);
>  }
>  




  reply	other threads:[~2014-01-30 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 17:24 [PATCH] vfio: Set PCI_DEV_FLAGS_ASSIGNED when assigning device to guest Bandan Das
2014-01-30 17:33 ` Alex Williamson [this message]
2014-01-30 17:36   ` Alex Williamson
2014-01-30 18:06     ` Bandan Das
2014-01-30 18:38       ` Alex Williamson
2014-01-30 20:10         ` Bandan Das

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=1391103225.6959.71.camel@bling.home \
    --to=alex.williamson@redhat.com \
    --cc=bsd@redhat.com \
    --cc=kvm@vger.kernel.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