€•~ÝŒsphinx.addnodes”Œdocument”“”)�”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)�”}”(hhh]”(hŒ pending_xref”“”)�”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…”�”}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ*/translations/zh_CN/gpu/rfc/i915_small_bar”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)�”}”(hhh]”hŒChinese (Traditional)”…”�”}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ*/translations/zh_TW/gpu/rfc/i915_small_bar”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒItalian”…”�”}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ*/translations/it_IT/gpu/rfc/i915_small_bar”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒJapanese”…”�”}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ*/translations/ja_JP/gpu/rfc/i915_small_bar”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒKorean”…”�”}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ*/translations/ko_KR/gpu/rfc/i915_small_bar”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒPortuguese (Brazilian)”…”�”}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ*/translations/pt_BR/gpu/rfc/i915_small_bar”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒSpanish”…”�”}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ*/translations/sp_SP/gpu/rfc/i915_small_bar”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒsection”“”)�”}”(hhh]”(hŒtitle”“”)�”}”(hŒI915 Small BAR RFC Section”h]”hŒI915 Small BAR RFC Section”…”�”}”(hh¼h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhh·h²hh³ŒD/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar.rst”h´KubhŒ paragraph”“”)�”}”(hXgStarting from DG2 we will have resizable BAR support for device local-memory(i.e I915_MEMORY_CLASS_DEVICE), but in some cases the final BAR size might still be smaller than the total probed_size. In such cases, only some subset of I915_MEMORY_CLASS_DEVICE will be CPU accessible(for example the first 256M), while the remainder is only accessible via the GPU.”h]”hXgStarting from DG2 we will have resizable BAR support for device local-memory(i.e I915_MEMORY_CLASS_DEVICE), but in some cases the final BAR size might still be smaller than the total probed_size. In such cases, only some subset of I915_MEMORY_CLASS_DEVICE will be CPU accessible(for example the first 256M), while the remainder is only accessible via the GPU.”…”�”}”(hhÍh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khh·h²hubh¶)�”}”(hhh]”(h»)�”}”(hŒ.I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS flag”h]”hŒ.I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS flag”…”�”}”(hhÞh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhhÛh²hh³hÊh´K ubhÌ)�”}”(hX�New gem_create_ext flag to tell the kernel that a BO will require CPU access. This becomes important when placing an object in I915_MEMORY_CLASS_DEVICE, where underneath the device has a small BAR, meaning only some portion of it is CPU accessible. Without this flag the kernel will assume that CPU access is not required, and prioritize using the non-CPU visible portion of I915_MEMORY_CLASS_DEVICE.”h]”hX�New gem_create_ext flag to tell the kernel that a BO will require CPU access. This becomes important when placing an object in I915_MEMORY_CLASS_DEVICE, where underneath the device has a small BAR, meaning only some portion of it is CPU accessible. Without this flag the kernel will assume that CPU access is not required, and prioritize using the non-CPU visible portion of I915_MEMORY_CLASS_DEVICE.”…”�”}”(hhìh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K hhÛh²hubhŒindex”“”)�”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œentries”]”(Œsingle”Œ$__drm_i915_gem_create_ext (C struct)”Œc.__drm_i915_gem_create_ext”hNt”auh1húhhÛh²hh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´NubhŒdesc”“”)�”}”(hhh]”(hŒdesc_signature”“”)�”}”(hŒ__drm_i915_gem_create_ext”h]”hŒdesc_signature_line”“”)�”}”(hŒ struct __drm_i915_gem_create_ext”h]”(hŒdesc_sig_keyword”“”)�”}”(hŒstruct”h]”hŒstruct”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”Œk”ah"]”h$]”h&]”uh1jhjh²hh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´KubhŒdesc_sig_space”“”)�”}”(hŒ ”h]”hŒ ”…”�”}”(hj1h²hh³Nh´Nubah}”(h]”h ]”Œw”ah"]”h$]”h&]”uh1j/hjh²hh³j.h´KubhŒ desc_name”“”)�”}”(hŒ__drm_i915_gem_create_ext”h]”hŒ desc_sig_name”“”)�”}”(hjh]”hŒ__drm_i915_gem_create_ext”…”�”}”(hjHh²hh³Nh´Nubah}”(h]”h ]”Œn”ah"]”h$]”h&]”uh1jFhjBubah}”(h]”h ]”(Œsig-name”Œdescname”eh"]”h$]”h&]”Œ xml:space”Œpreserve”uh1j@hjh²hh³j.h´Kubeh}”(h]”h ]”h"]”h$]”h&]”j^j_Œ add_permalink”ˆuh1jŒsphinx_line_type”Œ declarator”hjh²hh³j.h´Kubah}”(h]”j ah ]”(Œsig”Œ sig-object”eh"]”h$]”h&]”Œ is_multiline”ˆŒ _toc_parts”)Œ _toc_name”huh1jh³j.h´Khjh²hubhŒ desc_content”“”)�”}”(hhh]”hÌ)�”}”(hŒ]Existing gem_create behaviour, with added extension support using struct i915_user_extension.”h]”hŒ]Existing gem_create behaviour, with added extension support using struct i915_user_extension.”…”�”}”(hjyh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´K^hjvh²hubah}”(h]”h ]”h"]”h$]”h&]”uh1jthjh²hh³j.h´Kubeh}”(h]”h ]”(Œc”Œstruct”eh"]”h$]”h&]”Œdomain”j‘Œobjtype”j’Œdesctype”j’Œnoindex”‰Œ noindexentry”‰Œnocontentsentry”‰uh1j h²hhhÛh³j h´NubhŒ container”“”)�”}”(hXë **Definition**:: struct __drm_i915_gem_create_ext { __u64 size; __u32 handle; #define I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS (1 << 0); __u32 flags; #define I915_GEM_CREATE_EXT_MEMORY_REGIONS 0; #define I915_GEM_CREATE_EXT_PROTECTED_CONTENT 1; __u64 extensions; }; **Members** ``size`` Requested size for the object. The (page-aligned) allocated size for the object will be returned. Note that for some devices we have might have further minimum page-size restrictions (larger than 4K), like for device local-memory. However in general the final size here should always reflect any rounding up, if for example using the I915_GEM_CREATE_EXT_MEMORY_REGIONS extension to place the object in device local-memory. The kernel will always select the largest minimum page-size for the set of possible placements as the value to use when rounding up the **size**. ``handle`` Returned handle for the object. Object handles are nonzero. ``flags`` Optional flags. Supported values: I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS - Signal to the kernel that the object will need to be accessed via the CPU. Only valid when placing objects in I915_MEMORY_CLASS_DEVICE, and only strictly required on configurations where some subset of the device memory is directly visible/mappable through the CPU (which we also call small BAR), like on some DG2+ systems. Note that this is quite undesirable, but due to various factors like the client CPU, BIOS etc it's something we can expect to see in the wild. See :c:type:`__drm_i915_memory_region_info.probed_cpu_visible_size <__drm_i915_memory_region_info>` for how to determine if this system applies. Note that one of the placements MUST be I915_MEMORY_CLASS_SYSTEM, to ensure the kernel can always spill the allocation to system memory, if the object can't be allocated in the mappable part of I915_MEMORY_CLASS_DEVICE. Also note that since the kernel only supports flat-CCS on objects that can *only* be placed in I915_MEMORY_CLASS_DEVICE, we therefore don't support I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS together with flat-CCS. Without this hint, the kernel will assume that non-mappable I915_MEMORY_CLASS_DEVICE is preferred for this object. Note that the kernel can still migrate the object to the mappable part, as a last resort, if userspace ever CPU faults this object, but this might be expensive, and so ideally should be avoided. On older kernels which lack the relevant small-bar uAPI support (see also :c:type:`__drm_i915_memory_region_info.probed_cpu_visible_size <__drm_i915_memory_region_info>`), usage of the flag will result in an error, but it should NEVER be possible to end up with a small BAR configuration, assuming we can also successfully load the i915 kernel module. In such cases the entire I915_MEMORY_CLASS_DEVICE region will be CPU accessible, and as such there are zero restrictions on where the object can be placed. ``extensions`` The chain of extensions to apply to this object. This will be useful in the future when we need to support several different extensions, and we need to apply more than one when creating the object. See struct i915_user_extension. If we don't supply any extensions then we get the same old gem_create behaviour. For I915_GEM_CREATE_EXT_MEMORY_REGIONS usage see struct drm_i915_gem_create_ext_memory_regions. For I915_GEM_CREATE_EXT_PROTECTED_CONTENT usage see struct drm_i915_gem_create_ext_protected_content.”h]”(hÌ)�”}”(hŒ**Definition**::”h]”(hŒstrong”“”)�”}”(hŒ**Definition**”h]”hŒ Definition”…”�”}”(hj¨h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hj¢ubhŒ:”…”�”}”(hj¢h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´KbhjžubhŒ literal_block”“”)�”}”(hX struct __drm_i915_gem_create_ext { __u64 size; __u32 handle; #define I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS (1 << 0); __u32 flags; #define I915_GEM_CREATE_EXT_MEMORY_REGIONS 0; #define I915_GEM_CREATE_EXT_PROTECTED_CONTENT 1; __u64 extensions; };”h]”hX struct __drm_i915_gem_create_ext { __u64 size; __u32 handle; #define I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS (1 << 0); __u32 flags; #define I915_GEM_CREATE_EXT_MEMORY_REGIONS 0; #define I915_GEM_CREATE_EXT_PROTECTED_CONTENT 1; __u64 extensions; };”…”�”}”hjÃsbah}”(h]”h ]”h"]”h$]”h&]”j^j_uh1jÁh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´KdhjžubhÌ)�”}”(hŒ **Members**”h]”j§)�”}”(hjÔh]”hŒMembers”…”�”}”(hjÖh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hjÒubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´KnhjžubhŒdefinition_list”“”)�”}”(hhh]”(hŒdefinition_list_item”“”)�”}”(hXD``size`` Requested size for the object. The (page-aligned) allocated size for the object will be returned. Note that for some devices we have might have further minimum page-size restrictions (larger than 4K), like for device local-memory. However in general the final size here should always reflect any rounding up, if for example using the I915_GEM_CREATE_EXT_MEMORY_REGIONS extension to place the object in device local-memory. The kernel will always select the largest minimum page-size for the set of possible placements as the value to use when rounding up the **size**. ”h]”(hŒterm”“”)�”}”(hŒ``size``”h]”hŒliteral”“”)�”}”(hjùh]”hŒsize”…”�”}”(hjýh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jûhj÷ubah}”(h]”h ]”h"]”h$]”h&]”uh1jõh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´KthjñubhŒ definition”“”)�”}”(hhh]”(hÌ)�”}”(hŒRequested size for the object.”h]”hŒRequested size for the object.”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´KjhjubhÌ)�”}”(hŒBThe (page-aligned) allocated size for the object will be returned.”h]”hŒBThe (page-aligned) allocated size for the object will be returned.”…”�”}”(hj%h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´KlhjubhÌ)�”}”(hXÖNote that for some devices we have might have further minimum page-size restrictions (larger than 4K), like for device local-memory. However in general the final size here should always reflect any rounding up, if for example using the I915_GEM_CREATE_EXT_MEMORY_REGIONS extension to place the object in device local-memory. The kernel will always select the largest minimum page-size for the set of possible placements as the value to use when rounding up the **size**.”h]”(hXÍNote that for some devices we have might have further minimum page-size restrictions (larger than 4K), like for device local-memory. However in general the final size here should always reflect any rounding up, if for example using the I915_GEM_CREATE_EXT_MEMORY_REGIONS extension to place the object in device local-memory. The kernel will always select the largest minimum page-size for the set of possible placements as the value to use when rounding up the ”…”�”}”(hj4h²hh³Nh´Nubj§)�”}”(hŒ**size**”h]”hŒsize”…”�”}”(hj<h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hj4ubhŒ.”…”�”}”(hj4h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´Knhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhjñubeh}”(h]”h ]”h"]”h$]”h&]”uh1jïh³jh´Kthjìubjð)�”}”(hŒH``handle`` Returned handle for the object. Object handles are nonzero. ”h]”(jö)�”}”(hŒ ``handle``”h]”jü)�”}”(hjgh]”hŒhandle”…”�”}”(hjih²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jûhjeubah}”(h]”h ]”h"]”h$]”h&]”uh1jõh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´K{hjaubj)�”}”(hhh]”(hÌ)�”}”(hŒReturned handle for the object.”h]”hŒReturned handle for the object.”…”�”}”(hj€h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´Kyhj}ubhÌ)�”}”(hŒObject handles are nonzero.”h]”hŒObject handles are nonzero.”…”�”}”(hj�h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³j|h´K{hj}ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhjaubeh}”(h]”h ]”h"]”h$]”h&]”uh1jïh³j|h´K{hjìubjð)�”}”(hX§``flags`` Optional flags. Supported values: I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS - Signal to the kernel that the object will need to be accessed via the CPU. Only valid when placing objects in I915_MEMORY_CLASS_DEVICE, and only strictly required on configurations where some subset of the device memory is directly visible/mappable through the CPU (which we also call small BAR), like on some DG2+ systems. Note that this is quite undesirable, but due to various factors like the client CPU, BIOS etc it's something we can expect to see in the wild. See :c:type:`__drm_i915_memory_region_info.probed_cpu_visible_size <__drm_i915_memory_region_info>` for how to determine if this system applies. Note that one of the placements MUST be I915_MEMORY_CLASS_SYSTEM, to ensure the kernel can always spill the allocation to system memory, if the object can't be allocated in the mappable part of I915_MEMORY_CLASS_DEVICE. Also note that since the kernel only supports flat-CCS on objects that can *only* be placed in I915_MEMORY_CLASS_DEVICE, we therefore don't support I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS together with flat-CCS. Without this hint, the kernel will assume that non-mappable I915_MEMORY_CLASS_DEVICE is preferred for this object. Note that the kernel can still migrate the object to the mappable part, as a last resort, if userspace ever CPU faults this object, but this might be expensive, and so ideally should be avoided. On older kernels which lack the relevant small-bar uAPI support (see also :c:type:`__drm_i915_memory_region_info.probed_cpu_visible_size <__drm_i915_memory_region_info>`), usage of the flag will result in an error, but it should NEVER be possible to end up with a small BAR configuration, assuming we can also successfully load the i915 kernel module. In such cases the entire I915_MEMORY_CLASS_DEVICE region will be CPU accessible, and as such there are zero restrictions on where the object can be placed. ”h]”(jö)�”}”(hŒ ``flags``”h]”jü)�”}”(hj¯h]”hŒflags”…”�”}”(hj±h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jûhj­ubah}”(h]”h ]”h"]”h$]”h&]”uh1jõh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´K¦hj©ubj)�”}”(hhh]”(hÌ)�”}”(hŒOptional flags.”h]”hŒOptional flags.”…”�”}”(hjÈh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´K€hjÅubhÌ)�”}”(hŒSupported values:”h]”hŒSupported values:”…”�”}”(hj×h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´K‚hjÅubhÌ)�”}”(hŒvI915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS - Signal to the kernel that the object will need to be accessed via the CPU.”h]”hŒvI915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS - Signal to the kernel that the object will need to be accessed via the CPU.”…”�”}”(hjæh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´K„hjÅubhÌ)�”}”(hXOnly valid when placing objects in I915_MEMORY_CLASS_DEVICE, and only strictly required on configurations where some subset of the device memory is directly visible/mappable through the CPU (which we also call small BAR), like on some DG2+ systems. Note that this is quite undesirable, but due to various factors like the client CPU, BIOS etc it's something we can expect to see in the wild. See :c:type:`__drm_i915_memory_region_info.probed_cpu_visible_size <__drm_i915_memory_region_info>` for how to determine if this system applies.”h]”(hXŽOnly valid when placing objects in I915_MEMORY_CLASS_DEVICE, and only strictly required on configurations where some subset of the device memory is directly visible/mappable through the CPU (which we also call small BAR), like on some DG2+ systems. Note that this is quite undesirable, but due to various factors like the client CPU, BIOS etc it’s something we can expect to see in the wild. See ”…”�”}”(hjõh²hh³Nh´Nubh)�”}”(hŒ_:c:type:`__drm_i915_memory_region_info.probed_cpu_visible_size <__drm_i915_memory_region_info>`”h]”jü)�”}”(hjÿh]”hŒ5__drm_i915_memory_region_info.probed_cpu_visible_size”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”(Œxref”j‘Œc-type”eh"]”h$]”h&]”uh1jûhjýubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”Œgpu/rfc/i915_small_bar”Œ refdomain”j‘Œreftype”Œtype”Œ refexplicit”ˆŒrefwarn”‰Œ c:parent_key”Œsphinx.domains.c”Œ LookupKey”“”)�”}”Œdata”]”sbŒ reftarget”Œ__drm_i915_memory_region_info”uh1hh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´K‡hjõubhŒ- for how to determine if this system applies.”…”�”}”(hjõh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³j'h´K‡hjÅubhÌ)�”}”(hŒÛNote that one of the placements MUST be I915_MEMORY_CLASS_SYSTEM, to ensure the kernel can always spill the allocation to system memory, if the object can't be allocated in the mappable part of I915_MEMORY_CLASS_DEVICE.”h]”hŒÝNote that one of the placements MUST be I915_MEMORY_CLASS_SYSTEM, to ensure the kernel can always spill the allocation to system memory, if the object can’t be allocated in the mappable part of I915_MEMORY_CLASS_DEVICE.”…”�”}”(hj2h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´K�hjÅubhÌ)�”}”(hŒÕAlso note that since the kernel only supports flat-CCS on objects that can *only* be placed in I915_MEMORY_CLASS_DEVICE, we therefore don't support I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS together with flat-CCS.”h]”(hŒKAlso note that since the kernel only supports flat-CCS on objects that can ”…”�”}”(hjAh²hh³Nh´NubhŒemphasis”“”)�”}”(hŒ*only*”h]”hŒonly”…”�”}”(hjKh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jIhjAubhŒ† be placed in I915_MEMORY_CLASS_DEVICE, we therefore don’t support I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS together with flat-CCS.”…”�”}”(hjAh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´K•hjÅubhÌ)�”}”(hX5Without this hint, the kernel will assume that non-mappable I915_MEMORY_CLASS_DEVICE is preferred for this object. Note that the kernel can still migrate the object to the mappable part, as a last resort, if userspace ever CPU faults this object, but this might be expensive, and so ideally should be avoided.”h]”hX5Without this hint, the kernel will assume that non-mappable I915_MEMORY_CLASS_DEVICE is preferred for this object. Note that the kernel can still migrate the object to the mappable part, as a last resort, if userspace ever CPU faults this object, but this might be expensive, and so ideally should be avoided.”…”�”}”(hjdh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´KšhjÅubhÌ)�”}”(hXûOn older kernels which lack the relevant small-bar uAPI support (see also :c:type:`__drm_i915_memory_region_info.probed_cpu_visible_size <__drm_i915_memory_region_info>`), usage of the flag will result in an error, but it should NEVER be possible to end up with a small BAR configuration, assuming we can also successfully load the i915 kernel module. In such cases the entire I915_MEMORY_CLASS_DEVICE region will be CPU accessible, and as such there are zero restrictions on where the object can be placed.”h]”(hŒJOn older kernels which lack the relevant small-bar uAPI support (see also ”…”�”}”(hjsh²hh³Nh´Nubh)�”}”(hŒ_:c:type:`__drm_i915_memory_region_info.probed_cpu_visible_size <__drm_i915_memory_region_info>`”h]”jü)�”}”(hj}h]”hŒ5__drm_i915_memory_region_info.probed_cpu_visible_size”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”(j j‘Œc-type”eh"]”h$]”h&]”uh1jûhj{ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”jŒ refdomain”j‘Œreftype”Œtype”Œ refexplicit”ˆŒrefwarn”‰jj!j%Œ__drm_i915_memory_region_info”uh1hh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´K hjsubhXR), usage of the flag will result in an error, but it should NEVER be possible to end up with a small BAR configuration, assuming we can also successfully load the i915 kernel module. In such cases the entire I915_MEMORY_CLASS_DEVICE region will be CPU accessible, and as such there are zero restrictions on where the object can be placed.”…”�”}”(hjsh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³jšh´K hjÅubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhj©ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jïh³jÄh´K¦hjìubjð)�”}”(hX``extensions`` The chain of extensions to apply to this object. This will be useful in the future when we need to support several different extensions, and we need to apply more than one when creating the object. See struct i915_user_extension. If we don't supply any extensions then we get the same old gem_create behaviour. For I915_GEM_CREATE_EXT_MEMORY_REGIONS usage see struct drm_i915_gem_create_ext_memory_regions. For I915_GEM_CREATE_EXT_PROTECTED_CONTENT usage see struct drm_i915_gem_create_ext_protected_content.”h]”(jö)�”}”(hŒ``extensions``”h]”jü)�”}”(hj·h]”hŒ extensions”…”�”}”(hj¹h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jûhjµubah}”(h]”h ]”h"]”h$]”h&]”uh1jõh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´K¸hj±ubj)�”}”(hhh]”(hÌ)�”}”(hŒ0The chain of extensions to apply to this object.”h]”hŒ0The chain of extensions to apply to this object.”…”�”}”(hjÐh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´K¬hjÍubhÌ)�”}”(hŒ´This will be useful in the future when we need to support several different extensions, and we need to apply more than one when creating the object. See struct i915_user_extension.”h]”hŒ´This will be useful in the future when we need to support several different extensions, and we need to apply more than one when creating the object. See struct i915_user_extension.”…”�”}”(hjßh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´K®hjÍubhÌ)�”}”(hŒPIf we don't supply any extensions then we get the same old gem_create behaviour.”h]”hŒRIf we don’t supply any extensions then we get the same old gem_create behaviour.”…”�”}”(hjîh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´K²hjÍubhÌ)�”}”(hŒ_For I915_GEM_CREATE_EXT_MEMORY_REGIONS usage see struct drm_i915_gem_create_ext_memory_regions.”h]”hŒ_For I915_GEM_CREATE_EXT_MEMORY_REGIONS usage see struct drm_i915_gem_create_ext_memory_regions.”…”�”}”(hjýh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´KµhjÍubhÌ)�”}”(hŒeFor I915_GEM_CREATE_EXT_PROTECTED_CONTENT usage see struct drm_i915_gem_create_ext_protected_content.”h]”hŒeFor I915_GEM_CREATE_EXT_PROTECTED_CONTENT usage see struct drm_i915_gem_create_ext_protected_content.”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³jÌh´K¸hjÍubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhj±ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jïh³jÌh´K¸hjìubeh}”(h]”h ]”h"]”h$]”h&]”uh1jêhjžubeh}”(h]”h ]”Œ kernelindent”ah"]”h$]”h&]”uh1jœhhÛh²hh³j h´NubhÌ)�”}”(hŒ**Description**”h]”j§)�”}”(hj5h]”hŒ Description”…”�”}”(hj7h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hj3ubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´K¼hhÛh²hubhÌ)�”}”(hXcNote that new buffer flags should be added here, at least for the stuff that is immutable. Previously we would have two ioctls, one to create the object with gem_create, and another to apply various parameters, however this creates some ambiguity for the params which are considered immutable. Also in general we're phasing out the various SET/GET ioctls.”h]”hXeNote that new buffer flags should be added here, at least for the stuff that is immutable. Previously we would have two ioctls, one to create the object with gem_create, and another to apply various parameters, however this creates some ambiguity for the params which are considered immutable. Also in general we’re phasing out the various SET/GET ioctls.”…”�”}”(hjKh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:19: ./Documentation/gpu/rfc/i915_small_bar.h”h´K_hhÛh²hubeh}”(h]”Œ.i915-gem-create-ext-flag-needs-cpu-access-flag”ah ]”h"]”Œ.i915_gem_create_ext_flag_needs_cpu_access flag”ah$]”h&]”uh1hµhh·h²hh³hÊh´K ubh¶)�”}”(hhh]”(h»)�”}”(hŒ!probed_cpu_visible_size attribute”h]”hŒ!probed_cpu_visible_size attribute”…”�”}”(hjeh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjbh²hh³hÊh´KubhÌ)�”}”(hXNew struct__drm_i915_memory_region attribute which returns the total size of the CPU accessible portion, for the particular region. This should only be applicable for I915_MEMORY_CLASS_DEVICE. We also report the unallocated_cpu_visible_size, alongside the unallocated_size.”h]”hXNew struct__drm_i915_memory_region attribute which returns the total size of the CPU accessible portion, for the particular region. This should only be applicable for I915_MEMORY_CLASS_DEVICE. We also report the unallocated_cpu_visible_size, alongside the unallocated_size.”…”�”}”(hjsh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khjbh²hubhÌ)�”}”(hX+Vulkan will need this as part of creating a separate VkMemoryHeap with the VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT set, to represent the CPU visible portion, where the total size of the heap needs to be known. It also wants to be able to give a rough estimate of how memory can potentially be allocated.”h]”hX+Vulkan will need this as part of creating a separate VkMemoryHeap with the VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT set, to represent the CPU visible portion, where the total size of the heap needs to be known. It also wants to be able to give a rough estimate of how memory can potentially be allocated.”…”�”}”(hj�h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´Khjbh²hubhû)�”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œentries”]”(jŒ(__drm_i915_memory_region_info (C struct)”Œc.__drm_i915_memory_region_info”hNt”auh1húhjbh²hh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´Nubj )�”}”(hhh]”(j)�”}”(hŒ__drm_i915_memory_region_info”h]”j)�”}”(hŒ$struct __drm_i915_memory_region_info”h]”(j)�”}”(hj!h]”hŒstruct”…”�”}”(hj©h²hh³Nh´Nubah}”(h]”h ]”j*ah"]”h$]”h&]”uh1jhj¥h²hh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´Kubj0)�”}”(hŒ ”h]”hŒ ”…”�”}”(hj·h²hh³Nh´Nubah}”(h]”h ]”j<ah"]”h$]”h&]”uh1j/hj¥h²hh³j¶h´KubjA)�”}”(hŒ__drm_i915_memory_region_info”h]”jG)�”}”(hj£h]”hŒ__drm_i915_memory_region_info”…”�”}”(hjÉh²hh³Nh´Nubah}”(h]”h ]”jRah"]”h$]”h&]”uh1jFhjÅubah}”(h]”h ]”(jYjZeh"]”h$]”h&]”j^j_uh1j@hj¥h²hh³j¶h´Kubeh}”(h]”h ]”h"]”h$]”h&]”j^j_jfˆuh1jjgjhhj¡h²hh³j¶h´Kubah}”(h]”j›ah ]”(jljmeh"]”h$]”h&]”jqˆjr)jshuh1jh³j¶h´Khjžh²hubju)�”}”(hhh]”hÌ)�”}”(hŒ,Describes one region as known to the driver.”h]”hŒ,Describes one region as known to the driver.”…”�”}”(hjëh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´Khjèh²hubah}”(h]”h ]”h"]”h$]”h&]”uh1jthjžh²hh³j¶h´Kubeh}”(h]”h ]”(j‘Œstruct”eh"]”h$]”h&]”j–j‘j—jj˜jj™‰jš‰j›‰uh1j h²hhjbh³j�h´Nubj�)�”}”(hXÞ **Definition**:: struct __drm_i915_memory_region_info { struct drm_i915_gem_memory_class_instance region; __u32 rsvd0; __u64 probed_size; __u64 unallocated_size; union { __u64 rsvd1[8]; struct { __u64 probed_cpu_visible_size; __u64 unallocated_cpu_visible_size; }; }; }; **Members** ``region`` The class:instance pair encoding ``rsvd0`` MBZ ``probed_size`` Memory probed by the driver Note that it should not be possible to ever encounter a zero value here, also note that no current region type will ever return -1 here. Although for future region types, this might be a possibility. The same applies to the other size fields. ``unallocated_size`` Estimate of memory remaining Requires CAP_PERFMON or CAP_SYS_ADMIN to get reliable accounting. Without this (or if this is an older kernel) the value here will always equal the **probed_size**. Note this is only currently tracked for I915_MEMORY_CLASS_DEVICE regions (for other types the value here will always equal the **probed_size**). ``{unnamed_union}`` anonymous ``rsvd1`` MBZ ``{unnamed_struct}`` anonymous ``probed_cpu_visible_size`` Memory probed by the driver that is CPU accessible. This will be always be <= **probed_size**, and the remainder (if there is any) will not be CPU accessible. On systems without small BAR, the **probed_size** will always equal the **probed_cpu_visible_size**, since all of it will be CPU accessible. Note this is only tracked for I915_MEMORY_CLASS_DEVICE regions (for other types the value here will always equal the **probed_size**). Note that if the value returned here is zero, then this must be an old kernel which lacks the relevant small-bar uAPI support (including I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS), but on such systems we should never actually end up with a small BAR configuration, assuming we are able to load the kernel module. Hence it should be safe to treat this the same as when **probed_cpu_visible_size** == **probed_size**. ``unallocated_cpu_visible_size`` Estimate of CPU visible memory remaining Note this is only tracked for I915_MEMORY_CLASS_DEVICE regions (for other types the value here will always equal the **probed_cpu_visible_size**). Requires CAP_PERFMON or CAP_SYS_ADMIN to get reliable accounting. Without this the value here will always equal the **probed_cpu_visible_size**. Note this is only currently tracked for I915_MEMORY_CLASS_DEVICE regions (for other types the value here will also always equal the **probed_cpu_visible_size**). If this is an older kernel the value here will be zero, see also **probed_cpu_visible_size**.”h]”(hÌ)�”}”(hŒ**Definition**::”h]”(j§)�”}”(hŒ**Definition**”h]”hŒ Definition”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hj ubhŒ:”…”�”}”(hj h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´KhjubjÂ)�”}”(hXEstruct __drm_i915_memory_region_info { struct drm_i915_gem_memory_class_instance region; __u32 rsvd0; __u64 probed_size; __u64 unallocated_size; union { __u64 rsvd1[8]; struct { __u64 probed_cpu_visible_size; __u64 unallocated_cpu_visible_size; }; }; };”h]”hXEstruct __drm_i915_memory_region_info { struct drm_i915_gem_memory_class_instance region; __u32 rsvd0; __u64 probed_size; __u64 unallocated_size; union { __u64 rsvd1[8]; struct { __u64 probed_cpu_visible_size; __u64 unallocated_cpu_visible_size; }; }; };”…”�”}”hj(sbah}”(h]”h ]”h"]”h$]”h&]”j^j_uh1jÁh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´KhjubhÌ)�”}”(hŒ **Members**”h]”j§)�”}”(hj9h]”hŒMembers”…”�”}”(hj;h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hj7ubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´Khjubjë)�”}”(hhh]”(jð)�”}”(hŒ,``region`` The class:instance pair encoding ”h]”(jö)�”}”(hŒ ``region``”h]”jü)�”}”(hjXh]”hŒregion”…”�”}”(hjZh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jûhjVubah}”(h]”h ]”h"]”h$]”h&]”uh1jõh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´K hjRubj)�”}”(hhh]”hÌ)�”}”(hŒ The class:instance pair encoding”h]”hŒ The class:instance pair encoding”…”�”}”(hjqh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³jmh´K hjnubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjRubeh}”(h]”h ]”h"]”h$]”h&]”uh1jïh³jmh´K hjOubjð)�”}”(hŒ``rsvd0`` MBZ ”h]”(jö)�”}”(hŒ ``rsvd0``”h]”jü)�”}”(hj‘h]”hŒrsvd0”…”�”}”(hj“h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jûhj�ubah}”(h]”h ]”h"]”h$]”h&]”uh1jõh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´Khj‹ubj)�”}”(hhh]”hÌ)�”}”(hŒMBZ”h]”hŒMBZ”…”�”}”(hjªh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³j¦h´Khj§ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj‹ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jïh³j¦h´KhjOubjð)�”}”(hX ``probed_size`` Memory probed by the driver Note that it should not be possible to ever encounter a zero value here, also note that no current region type will ever return -1 here. Although for future region types, this might be a possibility. The same applies to the other size fields. ”h]”(jö)�”}”(hŒ``probed_size``”h]”jü)�”}”(hjÊh]”hŒ probed_size”…”�”}”(hjÌh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jûhjÈubah}”(h]”h ]”h"]”h$]”h&]”uh1jõh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´KhjÄubj)�”}”(hhh]”(hÌ)�”}”(hŒMemory probed by the driver”h]”hŒMemory probed by the driver”…”�”}”(hjãh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´KhjàubhÌ)�”}”(hŒòNote that it should not be possible to ever encounter a zero value here, also note that no current region type will ever return -1 here. Although for future region types, this might be a possibility. The same applies to the other size fields.”h]”hŒòNote that it should not be possible to ever encounter a zero value here, also note that no current region type will ever return -1 here. Although for future region types, this might be a possibility. The same applies to the other size fields.”…”�”}”(hjòh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´Khjàubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhjÄubeh}”(h]”h ]”h"]”h$]”h&]”uh1jïh³jßh´KhjOubjð)�”}”(hXi``unallocated_size`` Estimate of memory remaining Requires CAP_PERFMON or CAP_SYS_ADMIN to get reliable accounting. Without this (or if this is an older kernel) the value here will always equal the **probed_size**. Note this is only currently tracked for I915_MEMORY_CLASS_DEVICE regions (for other types the value here will always equal the **probed_size**). ”h]”(jö)�”}”(hŒ``unallocated_size``”h]”jü)�”}”(hjh]”hŒunallocated_size”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jûhjubah}”(h]”h ]”h"]”h$]”h&]”uh1jõh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´K"hj ubj)�”}”(hhh]”(hÌ)�”}”(hŒEstimate of memory remaining”h]”hŒEstimate of memory remaining”…”�”}”(hj,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´Khj)ubhÌ)�”}”(hX5Requires CAP_PERFMON or CAP_SYS_ADMIN to get reliable accounting. Without this (or if this is an older kernel) the value here will always equal the **probed_size**. Note this is only currently tracked for I915_MEMORY_CLASS_DEVICE regions (for other types the value here will always equal the **probed_size**).”h]”(hŒ”Requires CAP_PERFMON or CAP_SYS_ADMIN to get reliable accounting. Without this (or if this is an older kernel) the value here will always equal the ”…”�”}”(hj;h²hh³Nh´Nubj§)�”}”(hŒ**probed_size**”h]”hŒ probed_size”…”�”}”(hjCh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hj;ubhŒ�. Note this is only currently tracked for I915_MEMORY_CLASS_DEVICE regions (for other types the value here will always equal the ”…”�”}”(hj;h²hh³Nh´Nubj§)�”}”(hŒ**probed_size**”h]”hŒ probed_size”…”�”}”(hjUh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hj;ubhŒ).”…”�”}”(hj;h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´Khj)ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhj ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jïh³j(h´K"hjOubjð)�”}”(hŒ``{unnamed_union}`` anonymous ”h]”(jö)�”}”(hŒ``{unnamed_union}``”h]”jü)�”}”(hj€h]”hŒ{unnamed_union}”…”�”}”(hj‚h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jûhj~ubah}”(h]”h ]”h"]”h$]”h&]”uh1jõh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´Khjzubj)�”}”(hhh]”hÌ)�”}”(hŒ anonymous”h]”hŒ anonymous”…”�”}”(hj™h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³j•h´Khj–ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjzubeh}”(h]”h ]”h"]”h$]”h&]”uh1jïh³j•h´KhjOubjð)�”}”(hŒ``rsvd1`` MBZ ”h]”(jö)�”}”(hŒ ``rsvd1``”h]”jü)�”}”(hj¹h]”hŒrsvd1”…”�”}”(hj»h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jûhj·ubah}”(h]”h ]”h"]”h$]”h&]”uh1jõh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´K'hj³ubj)�”}”(hhh]”hÌ)�”}”(hŒMBZ”h]”hŒMBZ”…”�”}”(hjÒh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³jÎh´K'hjÏubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj³ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jïh³jÎh´K'hjOubjð)�”}”(hŒ``{unnamed_struct}`` anonymous ”h]”(jö)�”}”(hŒ``{unnamed_struct}``”h]”jü)�”}”(hjòh]”hŒ{unnamed_struct}”…”�”}”(hjôh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jûhjðubah}”(h]”h ]”h"]”h$]”h&]”uh1jõh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´Khjìubj)�”}”(hhh]”hÌ)�”}”(hŒ anonymous”h]”hŒ anonymous”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³jh´Khjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjìubeh}”(h]”h ]”h"]”h$]”h&]”uh1jïh³jh´KhjOubjð)�”}”(hXs``probed_cpu_visible_size`` Memory probed by the driver that is CPU accessible. This will be always be <= **probed_size**, and the remainder (if there is any) will not be CPU accessible. On systems without small BAR, the **probed_size** will always equal the **probed_cpu_visible_size**, since all of it will be CPU accessible. Note this is only tracked for I915_MEMORY_CLASS_DEVICE regions (for other types the value here will always equal the **probed_size**). Note that if the value returned here is zero, then this must be an old kernel which lacks the relevant small-bar uAPI support (including I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS), but on such systems we should never actually end up with a small BAR configuration, assuming we are able to load the kernel module. Hence it should be safe to treat this the same as when **probed_cpu_visible_size** == **probed_size**. ”h]”(jö)�”}”(hŒ``probed_cpu_visible_size``”h]”jü)�”}”(hj+h]”hŒprobed_cpu_visible_size”…”�”}”(hj-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jûhj)ubah}”(h]”h ]”h"]”h$]”h&]”uh1jõh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´KBhj%ubj)�”}”(hhh]”(hÌ)�”}”(hŒ3Memory probed by the driver that is CPU accessible.”h]”hŒ3Memory probed by the driver that is CPU accessible.”…”�”}”(hjDh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´K+hjAubhÌ)�”}”(hŒjThis will be always be <= **probed_size**, and the remainder (if there is any) will not be CPU accessible.”h]”(hŒThis will be always be <= ”…”�”}”(hjSh²hh³Nh´Nubj§)�”}”(hŒ**probed_size**”h]”hŒ probed_size”…”�”}”(hj[h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hjSubhŒA, and the remainder (if there is any) will not be CPU accessible.”…”�”}”(hjSh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´K.hjAubhÌ)�”}”(hŒŒOn systems without small BAR, the **probed_size** will always equal the **probed_cpu_visible_size**, since all of it will be CPU accessible.”h]”(hŒ"On systems without small BAR, the ”…”�”}”(hjth²hh³Nh´Nubj§)�”}”(hŒ**probed_size**”h]”hŒ probed_size”…”�”}”(hj|h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hjtubhŒ will always equal the ”…”�”}”(hjth²hh³Nh´Nubj§)�”}”(hŒ**probed_cpu_visible_size**”h]”hŒprobed_cpu_visible_size”…”�”}”(hjŽh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hjtubhŒ), since all of it will be CPU accessible.”…”�”}”(hjth²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´K2hjAubhÌ)�”}”(hŒ†Note this is only tracked for I915_MEMORY_CLASS_DEVICE regions (for other types the value here will always equal the **probed_size**).”h]”(hŒuNote this is only tracked for I915_MEMORY_CLASS_DEVICE regions (for other types the value here will always equal the ”…”�”}”(hj§h²hh³Nh´Nubj§)�”}”(hŒ**probed_size**”h]”hŒ probed_size”…”�”}”(hj¯h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hj§ubhŒ).”…”�”}”(hj§h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´K6hjAubhÌ)�”}”(hXŸNote that if the value returned here is zero, then this must be an old kernel which lacks the relevant small-bar uAPI support (including I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS), but on such systems we should never actually end up with a small BAR configuration, assuming we are able to load the kernel module. Hence it should be safe to treat this the same as when **probed_cpu_visible_size** == **probed_size**.”h]”(hXpNote that if the value returned here is zero, then this must be an old kernel which lacks the relevant small-bar uAPI support (including I915_GEM_CREATE_EXT_FLAG_NEEDS_CPU_ACCESS), but on such systems we should never actually end up with a small BAR configuration, assuming we are able to load the kernel module. Hence it should be safe to treat this the same as when ”…”�”}”(hjÈh²hh³Nh´Nubj§)�”}”(hŒ**probed_cpu_visible_size**”h]”hŒprobed_cpu_visible_size”…”�”}”(hjÐh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hjÈubhŒ == ”…”�”}”(hjÈh²hh³Nh´Nubj§)�”}”(hŒ**probed_size**”h]”hŒ probed_size”…”�”}”(hjâh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hjÈubhŒ.”…”�”}”(hjÈh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´K:hjAubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhj%ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jïh³j@h´KBhjOubjð)�”}”(hXq``unallocated_cpu_visible_size`` Estimate of CPU visible memory remaining Note this is only tracked for I915_MEMORY_CLASS_DEVICE regions (for other types the value here will always equal the **probed_cpu_visible_size**). Requires CAP_PERFMON or CAP_SYS_ADMIN to get reliable accounting. Without this the value here will always equal the **probed_cpu_visible_size**. Note this is only currently tracked for I915_MEMORY_CLASS_DEVICE regions (for other types the value here will also always equal the **probed_cpu_visible_size**). If this is an older kernel the value here will be zero, see also **probed_cpu_visible_size**.”h]”(jö)�”}”(hŒ ``unallocated_cpu_visible_size``”h]”jü)�”}”(hj h]”hŒunallocated_cpu_visible_size”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jûhj ubah}”(h]”h ]”h"]”h$]”h&]”uh1jõh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´KVhjubj)�”}”(hhh]”(hÌ)�”}”(hŒ(Estimate of CPU visible memory remaining”h]”hŒ(Estimate of CPU visible memory remaining”…”�”}”(hj&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´KGhj#ubhÌ)�”}”(hŒ’Note this is only tracked for I915_MEMORY_CLASS_DEVICE regions (for other types the value here will always equal the **probed_cpu_visible_size**).”h]”(hŒuNote this is only tracked for I915_MEMORY_CLASS_DEVICE regions (for other types the value here will always equal the ”…”�”}”(hj5h²hh³Nh´Nubj§)�”}”(hŒ**probed_cpu_visible_size**”h]”hŒprobed_cpu_visible_size”…”�”}”(hj=h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hj5ubhŒ).”…”�”}”(hj5h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´KJhj#ubhÌ)�”}”(hX3Requires CAP_PERFMON or CAP_SYS_ADMIN to get reliable accounting. Without this the value here will always equal the **probed_cpu_visible_size**. Note this is only currently tracked for I915_MEMORY_CLASS_DEVICE regions (for other types the value here will also always equal the **probed_cpu_visible_size**).”h]”(hŒuRequires CAP_PERFMON or CAP_SYS_ADMIN to get reliable accounting. Without this the value here will always equal the ”…”�”}”(hjVh²hh³Nh´Nubj§)�”}”(hŒ**probed_cpu_visible_size**”h]”hŒprobed_cpu_visible_size”…”�”}”(hj^h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hjVubhŒ†. Note this is only currently tracked for I915_MEMORY_CLASS_DEVICE regions (for other types the value here will also always equal the ”…”�”}”(hjVh²hh³Nh´Nubj§)�”}”(hŒ**probed_cpu_visible_size**”h]”hŒprobed_cpu_visible_size”…”�”}”(hjph²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hjVubhŒ).”…”�”}”(hjVh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´KOhj#ubhÌ)�”}”(hŒ]If this is an older kernel the value here will be zero, see also **probed_cpu_visible_size**.”h]”(hŒAIf this is an older kernel the value here will be zero, see also ”…”�”}”(hj‰h²hh³Nh´Nubj§)�”}”(hŒ**probed_cpu_visible_size**”h]”hŒprobed_cpu_visible_size”…”�”}”(hj‘h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hj‰ubhŒ.”…”�”}”(hj‰h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³j"h´KVhj#ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jïh³j"h´KVhjOubeh}”(h]”h ]”h"]”h$]”h&]”uh1jêhjubeh}”(h]”h ]”Œ kernelindent”ah"]”h$]”h&]”uh1jœhjbh²hh³j�h´NubhÌ)�”}”(hŒ**Description**”h]”j§)�”}”(hjÄh]”hŒ Description”…”�”}”(hjÆh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦hjÂubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´KZhjbh²hubhÌ)�”}”(hŒÞNote this is using both struct drm_i915_query_item and struct drm_i915_query. For this new query we are adding the new query id DRM_I915_QUERY_MEMORY_REGIONS at :c:type:`drm_i915_query_item.query_id `.”h]”(hŒ¡Note this is using both struct drm_i915_query_item and struct drm_i915_query. For this new query we are adding the new query id DRM_I915_QUERY_MEMORY_REGIONS at ”…”�”}”(hjÚh²hh³Nh´Nubh)�”}”(hŒ<:c:type:`drm_i915_query_item.query_id `”h]”jü)�”}”(hjäh]”hŒdrm_i915_query_item.query_id”…”�”}”(hjæh²hh³Nh´Nubah}”(h]”h ]”(j j‘Œc-type”eh"]”h$]”h&]”uh1jûhjâubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”jŒ refdomain”j‘Œreftype”Œtype”Œ refexplicit”ˆŒrefwarn”‰jj!j%Œdrm_i915_query_item”uh1hh³Œm/var/lib/git/docbuild/linux/Documentation/gpu/rfc/i915_small_bar:34: ./Documentation/gpu/rfc/i915_small_bar.h”h´KhjÚubhŒ.”…”�”}”(hjÚh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hËh³j h´Khjbh²hubeh}”(h]”Œ!probed-cpu-visible-size-attribute”ah ]”h"]”Œ!probed_cpu_visible_size attribute”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kubh¶)�”}”(hhh]”(h»)�”}”(hŒError Capture restrictions”h]”hŒError Capture restrictions”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj h²hh³hÊh´K&ubhÌ)�”}”(hŒ0With error capture we have two new restrictions:”h]”hŒ0With error capture we have two new restrictions:”…”�”}”(hj% h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K'hj h²hubhŒ block_quote”“”)�”}”(hXŠ1) Error capture is best effort on small BAR systems; if the pages are not CPU accessible, at the time of capture, then the kernel is free to skip trying to capture them. 2) On discrete and newer integrated platforms we now reject error capture on recoverable contexts. In the future the kernel may want to blit during error capture, when for example something is not currently CPU accessible.”h]”(hÌ)�”}”(hŒª1) Error capture is best effort on small BAR systems; if the pages are not CPU accessible, at the time of capture, then the kernel is free to skip trying to capture them.”h]”hŒª1) Error capture is best effort on small BAR systems; if the pages are not CPU accessible, at the time of capture, then the kernel is free to skip trying to capture them.”…”�”}”(hj9 h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K)hj5 ubhÌ)�”}”(hŒÞ2) On discrete and newer integrated platforms we now reject error capture on recoverable contexts. In the future the kernel may want to blit during error capture, when for example something is not currently CPU accessible.”h]”hŒÞ2) On discrete and newer integrated platforms we now reject error capture on recoverable contexts. In the future the kernel may want to blit during error capture, when for example something is not currently CPU accessible.”…”�”}”(hjG h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hËh³hÊh´K-hj5 ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j3 h³hÊh´K)hj h²hubeh}”(h]”Œerror-capture-restrictions”ah ]”h"]”Œerror capture restrictions”ah$]”h&]”uh1hµhh·h²hh³hÊh´K&ubeh}”(h]”Œi915-small-bar-rfc-section”ah ]”h"]”Œi915 small bar rfc section”ah$]”h&]”uh1hµhhh²hh³hÊh´Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”hÊuh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)�”}”(hºNŒ generator”NŒ datestamp”NŒ source_link”NŒ source_url”NŒ toc_backlinks”Œentry”Œfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒ report_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jŽ Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”hÊŒ _destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒ raw_enabled”KŒline_length_limit”M'Œpep_references”NŒ pep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒ rfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œ smart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(jh je j_j\j j j` j] uŒ nametypes”}”(jh ‰j_‰j ‰j` ‰uh}”(je h·j\hÛj jj jbj›j¡j] j uŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œ collections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œ transformer”NŒ include_log”]”Œ decoration”Nh²hub.