From: David Vrabel <david.vrabel@citrix.com>
To: <linux-pci@vger.kernel.org>
Cc: David Vrabel <david.vrabel@citrix.com>,
Bjorn Helgaas <bhelgaas@google.com>,
<xen-devel@lists.xenproject.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: [PATCHv1 0/2] xen-pciback: allow device reset to work more often
Date: Thu, 10 Jul 2014 14:03:12 +0100 [thread overview]
Message-ID: <1404997394-15715-1-git-send-email-david.vrabel@citrix.com> (raw)
When a PCI device is passed through to a different domain, it must be
reset to ensure it works correctly in the new domain. Usually the
toolstack will request a device reset via the "reset" sysfs file. But
this file is not present if a function reset is not available.
A common use case is a GPU device and its associated audio function.
In the case where these two devices are simultaneously co-assigned to
the same domain, it is safe to reset them with an SBR.
Patch #1 export pci_probe_reset_function() so pciback can know if an
alternate reset mechanism needs to be proved.
Patch #2 adds a "reset" file to devices bound to pciback that performs
the SBR if it is safe to do so.
David
next reply other threads:[~2014-07-10 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 13:03 David Vrabel [this message]
2014-07-10 13:03 ` [PATCH 1/2] pci: export pci_probe_reset_function() David Vrabel
2014-07-10 13:03 ` [PATCH 2/2] xen-pciback: provide a "reset" sysfs file to try harder at an SBR David Vrabel
2014-07-10 23:14 ` Alex Williamson
2014-07-11 9:53 ` David Vrabel
2014-07-11 13:45 ` Konrad Rzeszutek Wilk
2014-07-11 14:29 ` Alex Williamson
2014-07-10 16:25 ` [PATCHv1 0/2] xen-pciback: allow device reset to work more often Bjorn Helgaas
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=1404997394-15715-1-git-send-email-david.vrabel@citrix.com \
--to=david.vrabel@citrix.com \
--cc=bhelgaas@google.com \
--cc=boris.ostrovsky@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-pci@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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).