On Thu, 2014-06-19 at 11:53 +1000, Alexey Kardashevskiy wrote:
> On 06/19/2014 10:42 AM, Alexey Kardashevskiy wrote:
> > On 06/19/2014 04:57 AM, Alex Williamson wrote:
> >> On Wed, 2014-06-18 at 21:35 +1000, Alexey Kardashevskiy wrote:
> >>> Slow BAR access path is used when VFIO fails to mmap() BA
On 06/19/2014 10:42 AM, Alexey Kardashevskiy wrote:
> On 06/19/2014 04:57 AM, Alex Williamson wrote:
>> On Wed, 2014-06-18 at 21:35 +1000, Alexey Kardashevskiy wrote:
>>> Slow BAR access path is used when VFIO fails to mmap() BAR or TCG is used.
>>
>> TCG can use the mmap too
>
> Oh, right.
I'll
On 06/19/2014 04:57 AM, Alex Williamson wrote:
> On Wed, 2014-06-18 at 21:35 +1000, Alexey Kardashevskiy wrote:
>> Slow BAR access path is used when VFIO fails to mmap() BAR or TCG is used.
>
> TCG can use the mmap too
Oh, right.
>
>> Since this is just a transport between the guest and a devi
On Wed, 2014-06-18 at 21:35 +1000, Alexey Kardashevskiy wrote:
> Slow BAR access path is used when VFIO fails to mmap() BAR or TCG is used.
TCG can use the mmap too
> Since this is just a transport between the guest and a device, there is
> no need to do endianness swapping.
>
> This changes BAR
Slow BAR access path is used when VFIO fails to mmap() BAR or TCG is used.
Since this is just a transport between the guest and a device, there is
no need to do endianness swapping.
This changes BARs to use native endianness. Since non-ROM BARs were
doing byte swapping, we need to remove it so doe
