On 01/08/2015 04:23 AM, Alex Williamson wrote:
> We use an unsigned int when working with the PCI BAR size, which can
> obviously overflow if the BAR is 4GB or larger. This needs to change
> to a fixed length uint64_t. A similar issue is possible, though even
> more unlikely, when mapping the reg
On 01/07/15 12:23, Alex Williamson wrote:
> We use an unsigned int when working with the PCI BAR size, which can
> obviously overflow if the BAR is 4GB or larger. This needs to change
> to a fixed length uint64_t. A similar issue is possible, though even
> more unlikely, when mapping the region a
We use an unsigned int when working with the PCI BAR size, which can
obviously overflow if the BAR is 4GB or larger. This needs to change
to a fixed length uint64_t. A similar issue is possible, though even
more unlikely, when mapping the region above an MSI-X table. The
start of the MSI-X vecto
