Ben Widawsky writes:
> On Mon, Jan 13, 2014 at 11:41:11PM -0800, Eric Anholt wrote:
>> Kenneth Graunke writes:
>>
>> > The existing 'offset' field is unfortunately typed as 'unsigned long',
>> > which is unfortunately only 4 bytes with a 32-bit userspace.
>> >
>> > Traditionally, the hardware h
On Mon, Jan 13, 2014 at 11:41:11PM -0800, Eric Anholt wrote:
> Kenneth Graunke writes:
>
> > The existing 'offset' field is unfortunately typed as 'unsigned long',
> > which is unfortunately only 4 bytes with a 32-bit userspace.
> >
> > Traditionally, the hardware has only supported 32-bit virtua
Kenneth Graunke writes:
> The existing 'offset' field is unfortunately typed as 'unsigned long',
> which is unfortunately only 4 bytes with a 32-bit userspace.
>
> Traditionally, the hardware has only supported 32-bit virtual addresses,
> so even though the kernel uses a __u64, the value would al
On 01/13/2014 03:56 PM, Kenneth Graunke wrote:
> The existing 'offset' field is unfortunately typed as 'unsigned long',
> which is unfortunately only 4 bytes with a 32-bit userspace.
>
> Traditionally, the hardware has only supported 32-bit virtual addresses,
> so even though the kernel uses a __u
The existing 'offset' field is unfortunately typed as 'unsigned long',
which is unfortunately only 4 bytes with a 32-bit userspace.
Traditionally, the hardware has only supported 32-bit virtual addresses,
so even though the kernel uses a __u64, the value would always fit.
However, Broadwell suppo
