[Intel-gfx] [RFC] drm/i195: Add flag to enable virtual mappings above 4Gb

Tvrtko Ursulin tvrtko.ursulin at linux.intel.com
Wed Mar 18 10:08:23 PDT 2015


On 03/18/2015 04:57 PM, Nick Hoath wrote:
> Wa32bitGeneralStateOffset & Wa32bitInstructionBaseOffset hardware
> workarounds require that GeneralStateOffset & InstructionBaseOffset
> are restricted to a 32 bit address space.
>
> This is a preparatory patch prior to supporting 64bit virtual memory
> allocations.
>
> Allow the user space to flag that a mapping can occur beyond
> the 32bit limit. This allows backward compatibility and user space
> drivers that haven't been enhanced to support these workarounds to
> function.

Just on the naming..

Maybe the whole thing would better be named "full mem", "full range" or 
something like that?

"Hi mem", especially since the name is used in the userspace API has so 
much historical baggage meaning it needs to be _only_ in the special 
high memory range.

Regards,

Tvrtko


More information about the Intel-gfx mailing list