From: Don Dutile <ddutile@redhat.com>
To: "Benoît Canet" <benoit.canet@irqsave.net>
Cc: linux-pci@vger.kernel.org, qemu-devel@nongnu.org,
iommu@lists.linux-foundation.org, alex.williamson@redhat.com
Subject: Re: [Qemu-devel] SR-IOV PF reset and QEMU VFs VFIO passthrough
Date: Mon, 03 Jun 2013 14:41:04 -0400 [thread overview]
Message-ID: <51ACE340.1030406@redhat.com> (raw)
In-Reply-To: <20130601121320.GC5157@irqsave.net>
On 06/01/2013 08:13 AM, Benoît Canet wrote:
>
> Hello,
>
> I may have soon the PF driver of an SR-IOV card to code and make work with
> QEMU/KVM so I have the following questions.
>
> In an AMD64 setup where QEMU use VFIO to passthrough the VFs of an SR-IOV card
> to a guest will the consequences of a PF FLR be handled fine by QEMU and the
> guest ?
>
the reset occurs long before the device is passed to the guest.
> I read that pci_reset_function would call pci_restore_state restoring the SR-IOV
> configuration after the reset of the PF.
>
correct.
> The ways the hardware work means that the VFs would disappear and reappear in a
> short lapse of time.
>
Not sure your definitiion of 'disappear'. If you mean: if I had another thread
poking at the device, the device would appear to be removed, then come back (if os
poking hasn't crashed from the device's lack of response).
If you mean the VF gets entirely removed from the PCI tree, then no.
A pci reset != hot unplug/plug. The device remains in the device tree.
> Will these events be handled by the kernel pci hotplug code ?
>
'these events' ??? -- which events....
FLR is currently done by libvirt & qemu/vfio to ensure assigned devices are quiesced
as they are switched from host->guest domain, and guest->(back-to-)host domain.
> Given that the PF driver restore the PF config space after the reset will /sys
The PF driver doesn't do the config space restore -- it's done in PCI core code.
> files used by QEMU disappear and reappear messing the QEMU VFIO passthrough or
As stated above, the devices don't disappear from the device tree, so they don't
get removed/added to the /sys(/bus/pci/...) files.
> will it goes smoothly ?
>
it goes smoothly today.... :-/
> Best regards
>
> Benoît Canet
>
next prev parent reply other threads:[~2013-06-03 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 12:13 SR-IOV PF reset and QEMU VFs VFIO passthrough Benoît Canet
2013-06-02 14:11 ` Alex Williamson
2013-06-02 15:13 ` [Qemu-devel] " Benoît Canet
2013-06-03 18:41 ` Don Dutile [this message]
2013-06-03 19:29 ` Benoît Canet
2013-06-03 20:55 ` Don Dutile
2013-06-03 21:27 ` Benoît Canet
2013-06-03 21:42 ` Don Dutile
2013-06-03 21:58 ` Benoît Canet
2013-06-03 22:03 ` Don Dutile
2013-06-04 15:54 ` Benoît Canet
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=51ACE340.1030406@redhat.com \
--to=ddutile@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=benoit.canet@irqsave.net \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-pci@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).