| commit | befe5176ef7a0004ba23517c97c804e292273635 | |
| author | Alex Williamson <alex.williamson@redhat.com> | |
| Wed, 2 Oct 2013 18:52:38 +0000 (2 12:52 -0600) | ||
| committer | Alex Williamson <alex.williamson@redhat.com> | |
| Wed, 2 Oct 2013 18:52:38 +0000 (2 12:52 -0600) | ||
| tree | f5852694a2875241ec395cf95ff0a3adee21ea10 | treesnapshot (tar.gz zip) |
| parent | c7679d450ee021eb0826be65e4e018884443643a | commitdiff |
vfio-pci: Test device reset capabilities
Not all resets are created equal. PM reset is not very reliable,
especially for GPUs, so we might want to opt for a bus reset if a
standard reset will only do a D3hot->D0 transition. We can also
use this to tell if the standard reset will do a bus reset (if
neither has_pm_reset or has_flr is probed, but the device still
supports reset).
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Not all resets are created equal. PM reset is not very reliable,
especially for GPUs, so we might want to opt for a bus reset if a
standard reset will only do a D3hot->D0 transition. We can also
use this to tell if the standard reset will do a bus reset (if
neither has_pm_reset or has_flr is probed, but the device still
supports reset).
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
| hw/misc/vfio.c | diffblobblamehistory |