diff options
author | Jan Beulich <JBeulich@suse.com> | 2016-06-24 03:13:34 -0600 |
---|---|---|
committer | David Vrabel <david.vrabel@citrix.com> | 2016-06-24 10:53:03 +0100 |
commit | d2bd05d88d245c13b64c3bf9c8927a1c56453d8c (patch) | |
tree | 49b0a103f90f6d553a7bc69d5177f0784bda68e2 /drivers/xen/xenbus | |
parent | d6b186c1e2d852a92c43f090d0d8fad4704d51ef (diff) | |
download | linux-d2bd05d88d245c13b64c3bf9c8927a1c56453d8c.tar.gz linux-d2bd05d88d245c13b64c3bf9c8927a1c56453d8c.tar.bz2 linux-d2bd05d88d245c13b64c3bf9c8927a1c56453d8c.zip |
xen-pciback: return proper values during BAR sizing
Reads following writes with all address bits set to 1 should return all
changeable address bits as one, not the BAR size (nor, as was the case
for the upper half of 64-bit BARs, the high half of the region's end
address). Presumably this didn't cause any problems so far because
consumers use the value to calculate the size (usually via val & -val),
and do nothing else with it.
But also consider the exception here: Unimplemented BARs should always
return all zeroes.
And finally, the check for whether to return the sizing address on read
for the ROM BAR should ignore all non-address bits, not just the ROM
Enable one.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Signed-off-by: David Vrabel <david.vrabel@citrix.com>
Diffstat (limited to 'drivers/xen/xenbus')
0 files changed, 0 insertions, 0 deletions