On 09/26/2017 02:43 AM, Juergen Gross wrote:
> On 25/09/17 10:01, Jan Beulich wrote:
>> Just like done in d2bd05d88d ("xen-pciback: return proper values during
>> BAR sizing") for the ROM BAR, ordinary ones also shouldn't compare the
>> written value directly against ~0, but consider the r/o bits a
On 25/09/17 10:01, Jan Beulich wrote:
> Just like done in d2bd05d88d ("xen-pciback: return proper values during
> BAR sizing") for the ROM BAR, ordinary ones also shouldn't compare the
> written value directly against ~0, but consider the r/o bits at the
> bottom (if any).
>
> Signed-off-by: Jan B
On Mon, Sep 25, 2017 at 08:01:01AM +, Jan Beulich wrote:
> Just like done in d2bd05d88d ("xen-pciback: return proper values during
> BAR sizing") for the ROM BAR, ordinary ones also shouldn't compare the
> written value directly against ~0, but consider the r/o bits at the
> bottom (if any).
>
Just like done in d2bd05d88d ("xen-pciback: return proper values during
BAR sizing") for the ROM BAR, ordinary ones also shouldn't compare the
written value directly against ~0, but consider the r/o bits at the
bottom (if any).
Signed-off-by: Jan Beulich
---
drivers/xen/xen-pciback/conf_space_he
