On 03/14/2016 10:23 AM, Laszlo Ersek wrote:
On 03/14/16 09:07, Marcel Apfelbaum wrote:
On 03/14/2016 03:42 AM, Laszlo Ersek wrote:
In build_crs(), the calculation & merging of the ranges already
happens in
64-bit, but the entry boundaries are silently truncated to 32-bit in the
call to aml_dwor
On 03/14/16 09:07, Marcel Apfelbaum wrote:
> On 03/14/2016 03:42 AM, Laszlo Ersek wrote:
>> In build_crs(), the calculation & merging of the ranges already
>> happens in
>> 64-bit, but the entry boundaries are silently truncated to 32-bit in the
>> call to aml_dword_memory(). Use aml_qword_memory()
On 03/14/2016 03:42 AM, Laszlo Ersek wrote:
In build_crs(), the calculation & merging of the ranges already happens in
64-bit, but the entry boundaries are silently truncated to 32-bit in the
call to aml_dword_memory(). Use aml_qword_memory() when necessary -- this
fixes 64-bit BARs behind PXBs.
In build_crs(), the calculation & merging of the ranges already happens in
64-bit, but the entry boundaries are silently truncated to 32-bit in the
call to aml_dword_memory(). Use aml_qword_memory() when necessary -- this
fixes 64-bit BARs behind PXBs.
Cc: Marcel Apfelbaum
Cc: Michael S. Tsirkin