€•7      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ%/translations/zh_CN/gpu/xe/xe_migrate”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ%/translations/zh_TW/gpu/xe/xe_migrate”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ%/translations/it_IT/gpu/xe/xe_migrate”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ%/translations/ja_JP/gpu/xe/xe_migrate”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ%/translations/ko_KR/gpu/xe/xe_migrate”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ%/translations/sp_SP/gpu/xe/xe_migrate”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ*SPDX-License-Identifier: (GPL-2.0+ OR MIT)”h]”hŒ*SPDX-License-Identifier: (GPL-2.0+ OR MIT)”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1h¡hhhžhhŸŒ?/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate.rst”h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒMigrate Layer”h]”hŒMigrate Layer”…””}”(hh»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh¶hžhhŸh³h KubhŒ	paragraph”“”)”}”(hŒØThe XE migrate layer is used generate jobs which can copy memory (eviction),
clear memory, or program tables (binds). This layer exists in every GT, has
a migrate engine, and uses a special VM for all generated jobs.”h]”hŒØThe XE migrate layer is used generate jobs which can copy memory (eviction),
clear memory, or program tables (binds). This layer exists in every GT, has
a migrate engine, and uses a special VM for all generated jobs.”…””}”(hhËhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸŒd/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate:7: ./drivers/gpu/drm/xe/xe_migrate_doc.h”h K
hh¶hžhubhµ)”}”(hhh]”(hº)”}”(hŒSpecial VM details”h]”hŒSpecial VM details”…””}”(hhÝhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hhÚhŸNh NubhÊ)”}”(hŒêThe special VM is configured with a page structure where we can dynamically
map BOs which need to be copied and cleared, dynamically map other VM's page
table BOs for updates, and identity map the entire device's VRAM with 1 GB
pages.”h]”hŒîThe special VM is configured with a page structure where we can dynamically
map BOs which need to be copied and cleared, dynamically map other VMâ€™s page
table BOs for updates, and identity map the entire deviceâ€™s VRAM with 1 GB
pages.”…””}”(hhëhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸŒd/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate:7: ./drivers/gpu/drm/xe/xe_migrate_doc.h”h KhhÚubhÊ)”}”(hXE  Currently the page structure consists of 32 physical pages with 16 being
reserved for BO mapping during copies and clear, 1 reserved for kernel binds,
several pages are needed to setup the identity mappings (exact number based
on how many bits of address space the device has), and the rest are reserved
user bind operations.”h]”hXE  Currently the page structure consists of 32 physical pages with 16 being
reserved for BO mapping during copies and clear, 1 reserved for kernel binds,
several pages are needed to setup the identity mappings (exact number based
on how many bits of address space the device has), and the rest are reserved
user bind operations.”…””}”(hhúhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸŒd/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate:7: ./drivers/gpu/drm/xe/xe_migrate_doc.h”h KhhÚubhÊ)”}”(hŒTODO: Diagram of layout”h]”hŒTODO: Diagram of layout”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸŒd/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate:7: ./drivers/gpu/drm/xe/xe_migrate_doc.h”h KhhÚubeh}”(h]”Œspecial-vm-details”ah ]”h"]”Œspecial vm details”ah$]”h&]”uh1h´hh¶hžhhŸNh Nubhµ)”}”(hhh]”(hº)”}”(hŒ	Bind jobs”h]”hŒ	Bind jobs”…””}”(hj#  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj   hŸNh NubhÊ)”}”(hŒ·A bind job consist of two batches and runs either on the migrate engine
(kernel binds) or the bind engine passed in (user binds). In both cases the
VM of the engine is the migrate VM.”h]”hŒ·A bind job consist of two batches and runs either on the migrate engine
(kernel binds) or the bind engine passed in (user binds). In both cases the
VM of the engine is the migrate VM.”…””}”(hj1  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸŒd/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate:7: ./drivers/gpu/drm/xe/xe_migrate_doc.h”h K!hj   ubhÊ)”}”(hXo  The first batch is used to update the migration VM page structure to point to
the bind VM page table BOs which need to be updated. A physical page is
required for this. If it is a user bind, the page is allocated from pool of
pages reserved user bind operations with drm_suballoc managing this pool. If
it is a kernel bind, the page reserved for kernel binds is used.”h]”hXo  The first batch is used to update the migration VM page structure to point to
the bind VM page table BOs which need to be updated. A physical page is
required for this. If it is a user bind, the page is allocated from pool of
pages reserved user bind operations with drm_suballoc managing this pool. If
it is a kernel bind, the page reserved for kernel binds is used.”…””}”(hj@  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸŒd/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate:7: ./drivers/gpu/drm/xe/xe_migrate_doc.h”h K%hj   ubhÊ)”}”(hŒ¢The first batch is only required for devices without VRAM as when the device
has VRAM the bind VM page table BOs are in VRAM and the identity mapping can
be used.”h]”hŒ¢The first batch is only required for devices without VRAM as when the device
has VRAM the bind VM page table BOs are in VRAM and the identity mapping can
be used.”…””}”(hjO  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸŒd/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate:7: ./drivers/gpu/drm/xe/xe_migrate_doc.h”h K+hj   ubhÊ)”}”(hŒÆThe second batch is used to program page table updated in the bind VM. Why
not just one batch? Well the TLBs need to be invalidated between these two
batches and that only can be done from the ring.”h]”hŒÆThe second batch is used to program page table updated in the bind VM. Why
not just one batch? Well the TLBs need to be invalidated between these two
batches and that only can be done from the ring.”…””}”(hj^  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸŒd/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate:7: ./drivers/gpu/drm/xe/xe_migrate_doc.h”h K/hj   ubhÊ)”}”(hŒÙWhen the bind job complete, the page allocated is returned the pool of pages
reserved for user bind operations if a user bind. No need do this for kernel
binds as the reserved kernel page is serially used by each job.”h]”hŒÙWhen the bind job complete, the page allocated is returned the pool of pages
reserved for user bind operations if a user bind. No need do this for kernel
binds as the reserved kernel page is serially used by each job.”…””}”(hjm  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸŒd/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate:7: ./drivers/gpu/drm/xe/xe_migrate_doc.h”h K3hj   ubeh}”(h]”Œ	bind-jobs”ah ]”h"]”Œ	bind jobs”ah$]”h&]”uh1h´hh¶hžhhŸNh Nubhµ)”}”(hhh]”(hº)”}”(hŒCopy / clear jobs”h]”hŒCopy / clear jobs”…””}”(hj‡  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj„  hŸNh NubhÊ)”}”(hŒJA copy or clear job consist of two batches and runs on the migrate engine.”h]”hŒJA copy or clear job consist of two batches and runs on the migrate engine.”…””}”(hj•  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸŒd/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate:7: ./drivers/gpu/drm/xe/xe_migrate_doc.h”h K:hj„  ubhÊ)”}”(hXy  Like binds, the first batch is used update the migration VM page structure.
In copy jobs, we need to map the source and destination of the BO into page
the structure. In clear jobs, we just need to add 1 mapping of BO into the
page structure. We use the 16 reserved pages in migration VM for mappings,
this gives us a maximum copy size of 16 MB and maximum clear size of 32 MB.”h]”hXy  Like binds, the first batch is used update the migration VM page structure.
In copy jobs, we need to map the source and destination of the BO into page
the structure. In clear jobs, we just need to add 1 mapping of BO into the
page structure. We use the 16 reserved pages in migration VM for mappings,
this gives us a maximum copy size of 16 MB and maximum clear size of 32 MB.”…””}”(hj¤  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸŒd/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate:7: ./drivers/gpu/drm/xe/xe_migrate_doc.h”h K<hj„  ubhÊ)”}”(hŒ¯The second batch is used do either do the copy or clear. Again similar to
binds, two batches are required as the TLBs need to be invalidated from the
ring between the batches.”h]”hŒ¯The second batch is used do either do the copy or clear. Again similar to
binds, two batches are required as the TLBs need to be invalidated from the
ring between the batches.”…””}”(hj³  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸŒd/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate:7: ./drivers/gpu/drm/xe/xe_migrate_doc.h”h KBhj„  ubhÊ)”}”(hŒWMore than one job will be generated if the BO is larger than maximum copy /
clear size.”h]”hŒWMore than one job will be generated if the BO is larger than maximum copy /
clear size.”…””}”(hjÂ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸŒd/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate:7: ./drivers/gpu/drm/xe/xe_migrate_doc.h”h KFhj„  ubeh}”(h]”Œcopy-clear-jobs”ah ]”h"]”Œcopy / clear jobs”ah$]”h&]”uh1h´hh¶hžhhŸNh Nubhµ)”}”(hhh]”(hº)”}”(hŒFuture work”h]”hŒFuture work”…””}”(hjÜ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjÙ  hŸNh NubhÊ)”}”(hŒ7Update copy and clear code to use identity mapped VRAM.”h]”hŒ7Update copy and clear code to use identity mapped VRAM.”…””}”(hjê  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸŒd/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate:7: ./drivers/gpu/drm/xe/xe_migrate_doc.h”h KLhjÙ  ubhÊ)”}”(hŒSCan we rework the use of the pages async binds to use all the entries in each
page?”h]”hŒSCan we rework the use of the pages async binds to use all the entries in each
page?”…””}”(hjù  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸŒd/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate:7: ./drivers/gpu/drm/xe/xe_migrate_doc.h”h KNhjÙ  ubhÊ)”}”(hŒ&Using large pages for sysmem mappings.”h]”hŒ&Using large pages for sysmem mappings.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸŒd/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate:7: ./drivers/gpu/drm/xe/xe_migrate_doc.h”h KQhjÙ  ubhÊ)”}”(hŒBIs it possible to identity map the sysmem? We should explore this.”h]”hŒBIs it possible to identity map the sysmem? We should explore this.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸŒd/var/lib/git/docbuild/linux/Documentation/gpu/xe/xe_migrate:7: ./drivers/gpu/drm/xe/xe_migrate_doc.h”h KShjÙ  ubeh}”(h]”Œfuture-work”ah ]”h"]”Œfuture work”ah$]”h&]”uh1h´hh¶hžhhŸNh Nubeh}”(h]”Œmigrate-layer”ah ]”h"]”Œmigrate layer”ah$]”h&]”uh1h´hhhžhhŸh³h Kubeh}”(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”jY  Œ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”}”(j3  j0  j  j  j  j~  jÖ  jÓ  j+  j(  uŒ	nametypes”}”(j3  ‰j  ‰j  ‰jÖ  ‰j+  ‰uh}”(j0  h¶j  hÚj~  j   jÓ  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.