From: Alex Williamson <alex.williamson@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-devel@nongnu.org, Alex Graf <agraf@suse.de>,
kvm@vger.kernel.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [RFC PATCH] vfio: add fixup for broken PCI devices
Date: Wed, 06 Jun 2012 17:17:43 -0600 [thread overview]
Message-ID: <1339024663.23475.338.camel@bling.home> (raw)
In-Reply-To: <4FBF3627.3030504@ozlabs.ru>
On Fri, 2012-05-25 at 17:35 +1000, Alexey Kardashevskiy wrote:
> Some adapters (like NEC PCI USB controller) do not flush their config
> on a sioftware reset and remember DMA config, etc.
>
> If we use such an adapter with QEMU, then crash QEMU (stop it with
> ctrl-A ctrl-X), and try to use it in QEMU again, it may start working
> immediately with previous config when pci_enable_device() is called
> on that PCI function.
>
> To eliminate such effect, some quirk should be called. The proposed
> pci_fixup_final does its job well for mentioned NEC PCI USB but not
> sure if it is 100% correct.
>
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> ---
> drivers/vfio/pci/vfio_pci.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/vfio/pci/vfio_pci.c b/drivers/vfio/pci/vfio_pci.c
> index 1e5315c..6e7c12d 100644
> --- a/drivers/vfio/pci/vfio_pci.c
> +++ b/drivers/vfio/pci/vfio_pci.c
> @@ -88,6 +88,8 @@ static void vfio_pci_disable(struct vfio_pci_device *vdev)
> {
> int bar;
>
> + pci_fixup_device(pci_fixup_final, vdev->pdev);
> +
> pci_disable_device(vdev->pdev);
>
> vfio_pci_set_irqs_ioctl(vdev, VFIO_IRQ_SET_DATA_NONE |
Sorry, just taking a look at this again. Do you have any idea what
fixup it is that makes it work? Calling a fixup at this point seems
rather odd. I suspect the problem is that vfio is only calling
pci_load_and_free_saved_state if pci_reset_function reports that it
worked. kvm device assignment doesn't do that and I'm not sure why I
did that. If you unconditionally call pci_load_and_free_saved_state a
bit further down in this function, does it solve the problem? Thanks,
Alex
next prev parent reply other threads:[~2012-06-06 23:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 7:35 [Qemu-devel] [RFC PATCH] vfio: add fixup for broken PCI devices Alexey Kardashevskiy
2012-05-25 8:28 ` Benjamin Herrenschmidt
2012-05-25 12:24 ` Alex Williamson
2012-05-25 12:36 ` Benjamin Herrenschmidt
2012-05-28 12:44 ` Michael S. Tsirkin
2012-05-28 12:48 ` Jan Kiszka
2012-05-28 13:15 ` Michael S. Tsirkin
2012-06-06 23:17 ` Alex Williamson [this message]
2012-06-07 2:52 ` Benjamin Herrenschmidt
2012-06-07 3:56 ` Alex Williamson
2012-06-07 4:37 ` Benjamin Herrenschmidt
2012-06-22 8:16 ` Alexey Kardashevskiy
2012-08-17 14:28 ` Alexey Kardashevskiy
2012-08-21 2:31 ` Alex Williamson
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=1339024663.23475.338.camel@bling.home \
--to=alex.williamson@redhat.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=kvm@vger.kernel.org \
--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).