summaryrefslogtreecommitdiff
path: root/firmware
diff options
context:
space:
mode:
authorSheng Yang <sheng@linux.intel.com>2008-10-31 07:37:41 +0300
committerAvi Kivity <avi@redhat.com>2008-12-31 17:51:49 +0300
commit6eb55818c043b097c83828da8430fcb9a02fdb89 (patch)
tree8bdd77fa9fb110e50905093c746c3f70e62cb2ba /firmware
parent853dafb62b386a3a75808483a120998e734eb6e1 (diff)
downloadlinux-6eb55818c043b097c83828da8430fcb9a02fdb89.tar.xz
KVM: Enable Function Level Reset for assigned device
Ideally, every assigned device should in a clear condition before and after assignment, so that the former state of device won't affect later work. Some devices provide a mechanism named Function Level Reset, which is defined in PCI/PCI-e document. We should execute it before and after device assignment. (But sadly, the feature is new, and most device on the market now don't support it. We are considering using D0/D3hot transmit to emulate it later, but not that elegant and reliable as FLR itself.) [Update: Reminded by Xiantao, execute FLR after we ensure that the device can be assigned to the guest.] Signed-off-by: Sheng Yang <sheng@linux.intel.com> Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions