diff options
| author | Jason Ekstrand <[email protected]> | 2017-03-17 17:31:44 -0700 |
|---|---|---|
| committer | Jason Ekstrand <[email protected]> | 2017-04-04 18:33:52 -0700 |
| commit | 651ec926fc10258ddc567da44c231d5303b8740f (patch) | |
| tree | b2a09499f3c7ba382d3c38f2804aef38bc1edcc8 /src/intel/vulkan/anv_intel.c | |
| parent | 439da38d184b5e9dddcfb245a2454879e7632649 (diff) | |
anv: Add support for 48-bit addresses
This commit adds support for using the full 48-bit address space on
Broadwell and newer hardware. Thanks to certain limitations, not all
objects can be placed above the 32-bit boundary. In particular, general
and state base address need to live within 32 bits. (See also
Wa32bitGeneralStateOffset and Wa32bitInstructionBaseOffset.) In order
to handle this, we add a supports_48bit_address field to anv_bo and only
set EXEC_OBJECT_SUPPORTS_48B_ADDRESS if that bit is set. We set the bit
for all client-allocated memory objects but leave it false for
driver-allocated objects. While this is more conservative than needed,
all driver allocations should easily fit in the first 32 bits of address
space and keeps things simple because we don't have to think about
whether or not any given one of our allocation data structures will be
used in a 48-bit-unsafe way.
Reviewed-by: Kristian H. Kristensen <[email protected]>
Diffstat (limited to 'src/intel/vulkan/anv_intel.c')
| -rw-r--r-- | src/intel/vulkan/anv_intel.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/intel/vulkan/anv_intel.c b/src/intel/vulkan/anv_intel.c index c356e848fe0..eda474e62ec 100644 --- a/src/intel/vulkan/anv_intel.c +++ b/src/intel/vulkan/anv_intel.c @@ -59,6 +59,9 @@ VkResult anv_CreateDmaBufImageINTEL( anv_bo_init(&mem->bo, gem_handle, size); + if (device->instance->physicalDevice.supports_48bit_addresses) + mem->bo.flags |= EXEC_OBJECT_SUPPORTS_48B_ADDRESS; + anv_image_create(_device, &(struct anv_image_create_info) { .isl_tiling_flags = ISL_TILING_X_BIT, |