| commit | 0bb316db4116e8d59c226333e62e088ba190c252 | |
| author | Sheng Yang <sheng@linux.intel.com> | |
| Thu, 9 Apr 2009 01:40:59 +0000 (9 09:40 +0800) | ||
| committer | Avi Kivity <avi@redhat.com> | |
| Tue, 21 Apr 2009 10:10:00 +0000 (21 13:10 +0300) | ||
| tree | 834f28284d19677998d34d3f5326beba540fc239 | treesnapshot (tar.gz zip) |
| parent | ce56ff2ed0f924d65606f147fd9578597c40c393 | commitdiff |
kvm: qemu: don't check per-vector mask bit before enable MSI-X
Some guest drivers (e.g. bnx2) do the following to enable MSI-X:
1. Mask all vectors.
2. Write the msg data and address.
3. Enable MSI-X
4. Unmask all the vectors.
For this, check per-vector mask bit before enable MSI-X would cause device
fail to enable MSI-X. So now we only determine the availability of vector
by if msg_data is zero.
Signed-off-by: Sheng Yang <sheng@linux.intel.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
Some guest drivers (e.g. bnx2) do the following to enable MSI-X:
1. Mask all vectors.
2. Write the msg data and address.
3. Enable MSI-X
4. Unmask all the vectors.
For this, check per-vector mask bit before enable MSI-X would cause device
fail to enable MSI-X. So now we only determine the availability of vector
by if msg_data is zero.
Signed-off-by: Sheng Yang <sheng@linux.intel.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
| qemu/hw/device-assignment.c | diffblobblamehistory |