Subject: Re: [PATCH] vfio: Add an ioctl to reset the device
From: Alex Williamson <alex.williamson@redhat.com>
To: Chris Wright <chrisw@redhat.com>
Cc: pugs@ieee.org, linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
        qemu-devel@nongnu.org, aafabbri@cisco.com, dwang2@cisco.com,
        benve@cisco.com
In-Reply-To: <20110419220743.GO12133@x200.localdomain>
References: <20110419203234.4254.94914.stgit@s20.home>
	 <20110419220743.GO12133@x200.localdomain>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 19 Apr 2011 16:22:31 -0600
Message-ID: <1303251751.3110.129.camel@x201>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 892
Lines: 21

On Tue, 2011-04-19 at 15:07 -0700, Chris Wright wrote:
> * Alex Williamson (alex.williamson@redhat.com) wrote:
> > When using VFIO to assign a device to a guest, we want to make sure
> > the device is quiesced on VM reset to stop all DMA within the guest
> > mapped memory.  Add an ioctl which just calls pci_reset_function()
> > and returns whether it succeeds.
> 
> Shouldn't there be a reset when binding/unbinding vfio to/from a pci
> device?

There's already one when the /dev/vfioX file is opened, we should add
another on release, and probably add the same PCI save state store/load
that I'm proposing for KVM across those.  Thanks,

Alex

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/