From: Don Dutile <ddutile@redhat.com>
To: "Benoît Canet" <benoit.canet@irqsave.net>
Cc: linux-pci@vger.kernel.org, iommu@lists.linux-foundation.org,
alex.williamson@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] SR-IOV PF reset and QEMU VFs VFIO passthrough
Date: Mon, 03 Jun 2013 16:55:13 -0400 [thread overview]
Message-ID: <51AD02B1.8070503@redhat.com> (raw)
In-Reply-To: <20130603192958.GB31044@irqsave.net>
On 06/03/2013 03:29 PM, Benoît Canet wrote:
>>> 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 was asking this because the PF driver should reset the PF while the VF are
> used by VFIO/QEMU when the PF doesn't respond anymore.
>
What your VF does while your PF is being reset is PF (& VF) dependent.
A 'good design' would not impact the VF operation, other than to stall it until
the PF completed reset. My experience, though, is that the PF has to be brought
up to some level of functionality to share the physical resources with the VFs.
>> 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.... :-/
>
> Happy to read that thanks for the answer.
>
> Best regards
>
> Benoît Canet
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-06-03 20:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 12:13 [Qemu-devel] SR-IOV PF reset and QEMU VFs VFIO passthrough Benoît Canet
2013-06-02 14:11 ` Alex Williamson
2013-06-02 15:13 ` Benoît Canet
2013-06-03 18:41 ` Don Dutile
2013-06-03 19:29 ` Benoît Canet
2013-06-03 20:55 ` Don Dutile [this message]
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=51AD02B1.8070503@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).