€•ø9      Œ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”Œ7/translations/zh_CN/driver-api/nvdimm/firmware-activate”Œ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”Œ7/translations/zh_TW/driver-api/nvdimm/firmware-activate”Œ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”Œ7/translations/it_IT/driver-api/nvdimm/firmware-activate”Œ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”Œ7/translations/ja_JP/driver-api/nvdimm/firmware-activate”Œ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”Œ7/translations/ko_KR/driver-api/nvdimm/firmware-activate”Œ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”Œ7/translations/sp_SP/driver-api/nvdimm/firmware-activate”Œ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”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1h¡hhhžhhŸŒQ/var/lib/git/docbuild/linux/Documentation/driver-api/nvdimm/firmware-activate.rst”h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ"NVDIMM Runtime Firmware Activation”h]”hŒ"NVDIMM Runtime Firmware Activation”…””}”(hh»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh¶hžhhŸh³h KubhŒ	paragraph”“”)”}”(hXî  Some persistent memory devices run a firmware locally on the device /
"DIMM" to perform tasks like media management, capacity provisioning,
and health monitoring. The process of updating that firmware typically
involves a reboot because it has implications for in-flight memory
transactions. However, reboots are disruptive and at least the Intel
persistent memory platform implementation, described by the Intel ACPI
DSM specification [1], has added support for activating firmware at
runtime.”h]”hXò  Some persistent memory devices run a firmware locally on the device /
â€œDIMMâ€ to perform tasks like media management, capacity provisioning,
and health monitoring. The process of updating that firmware typically
involves a reboot because it has implications for in-flight memory
transactions. However, reboots are disruptive and at least the Intel
persistent memory platform implementation, described by the Intel ACPI
DSM specification [1], has added support for activating firmware at
runtime.”…””}”(hhËhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶hžhubhÊ)”}”(hŒ“A native sysfs interface is implemented in libnvdimm to allow platform
to advertise and control their local runtime firmware activation
capability.”h]”hŒ“A native sysfs interface is implemented in libnvdimm to allow platform
to advertise and control their local runtime firmware activation
capability.”…””}”(hhÙhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶hžhubhÊ)”}”(hŒµThe libnvdimm bus object, ndbusX, implements an ndbusX/firmware/activate
attribute that shows the state of the firmware activation as one of 'idle',
'armed', 'overflow', and 'busy'.”h]”hŒÅThe libnvdimm bus object, ndbusX, implements an ndbusX/firmware/activate
attribute that shows the state of the firmware activation as one of â€˜idleâ€™,
â€˜armedâ€™, â€˜overflowâ€™, and â€˜busyâ€™.”…””}”(hhçhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶hžhubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒ6idle:
No devices are set / armed to activate firmware
”h]”hÊ)”}”(hŒ5idle:
No devices are set / armed to activate firmware”h]”hŒ5idle:
No devices are set / armed to activate firmware”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khhüubah}”(h]”h ]”h"]”h$]”h&]”uh1húhh÷hžhhŸh³h Nubhû)”}”(hŒ$armed:
At least one device is armed
”h]”hÊ)”}”(hŒ#armed:
At least one device is armed”h]”hŒ#armed:
At least one device is armed”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1húhh÷hžhhŸh³h Nubhû)”}”(hŒ{busy:
In the busy state armed devices are in the process of transitioning
back to idle and completing an activation cycle.
”h]”hÊ)”}”(hŒzbusy:
In the busy state armed devices are in the process of transitioning
back to idle and completing an activation cycle.”h]”hŒzbusy:
In the busy state armed devices are in the process of transitioning
back to idle and completing an activation cycle.”…””}”(hj0  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj,  ubah}”(h]”h ]”h"]”h$]”h&]”uh1húhh÷hžhhŸh³h Nubhû)”}”(hX  overflow:
If the platform has a concept of incremental work needed to perform
the activation it could be the case that too many DIMMs are armed for
activation. In that scenario the potential for firmware activation to
timeout is indicated by the 'overflow' state.
”h]”hÊ)”}”(hX  overflow:
If the platform has a concept of incremental work needed to perform
the activation it could be the case that too many DIMMs are armed for
activation. In that scenario the potential for firmware activation to
timeout is indicated by the 'overflow' state.”h]”hX  overflow:
If the platform has a concept of incremental work needed to perform
the activation it could be the case that too many DIMMs are armed for
activation. In that scenario the potential for firmware activation to
timeout is indicated by the â€˜overflowâ€™ state.”…””}”(hjH  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K"hjD  ubah}”(h]”h ]”h"]”h$]”h&]”uh1húhh÷hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1hõhŸh³h Khh¶hžhubhÊ)”}”(hX  The 'ndbusX/firmware/activate' property can be written with a value of
either 'live', or 'quiesce'. A value of 'quiesce' triggers the kernel to
run firmware activation from within the equivalent of the hibernation
'freeze' state where drivers and applications are notified to stop their
modifications of system memory. A value of 'live' attempts
firmware activation without this hibernation cycle. The
'ndbusX/firmware/activate' property will be elided completely if no
firmware activation capability is detected.”h]”hX  The â€˜ndbusX/firmware/activateâ€™ property can be written with a value of
either â€˜liveâ€™, or â€˜quiesceâ€™. A value of â€˜quiesceâ€™ triggers the kernel to
run firmware activation from within the equivalent of the hibernation
â€˜freezeâ€™ state where drivers and applications are notified to stop their
modifications of system memory. A value of â€˜liveâ€™ attempts
firmware activation without this hibernation cycle. The
â€˜ndbusX/firmware/activateâ€™ property will be elided completely if no
firmware activation capability is detected.”…””}”(hjd  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K(hh¶hžhubhÊ)”}”(hXk  Another property 'ndbusX/firmware/capability' indicates a value of
'live' or 'quiesce', where 'live' indicates that the firmware
does not require or inflict any quiesce period on the system to update
firmware. A capability value of 'quiesce' indicates that firmware does
expect and injects a quiet period for the memory controller, but 'live'
may still be written to 'ndbusX/firmware/activate' as an override to
assume the risk of racing firmware update with in-flight device and
application activity. The 'ndbusX/firmware/capability' property will be
elided completely if no firmware activation capability is detected.”h]”hX‹  Another property â€˜ndbusX/firmware/capabilityâ€™ indicates a value of
â€˜liveâ€™ or â€˜quiesceâ€™, where â€˜liveâ€™ indicates that the firmware
does not require or inflict any quiesce period on the system to update
firmware. A capability value of â€˜quiesceâ€™ indicates that firmware does
expect and injects a quiet period for the memory controller, but â€˜liveâ€™
may still be written to â€˜ndbusX/firmware/activateâ€™ as an override to
assume the risk of racing firmware update with in-flight device and
application activity. The â€˜ndbusX/firmware/capabilityâ€™ property will be
elided completely if no firmware activation capability is detected.”…””}”(hjr  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K1hh¶hžhubhÊ)”}”(hX`  The libnvdimm memory-device / DIMM object, nmemX, implements
'nmemX/firmware/activate' and 'nmemX/firmware/result' attributes to
communicate the per-device firmware activation state. Similar to the
'ndbusX/firmware/activate' attribute, the 'nmemX/firmware/activate'
attribute indicates 'idle', 'armed', or 'busy'. The state transitions
from 'armed' to 'idle' when the system is prepared to activate firmware,
firmware staged + state set to armed, and 'ndbusX/firmware/activate' is
triggered. After that activation event the nmemX/firmware/result
attribute reflects the state of the last activation as one of:”h]”hXˆ  The libnvdimm memory-device / DIMM object, nmemX, implements
â€˜nmemX/firmware/activateâ€™ and â€˜nmemX/firmware/resultâ€™ attributes to
communicate the per-device firmware activation state. Similar to the
â€˜ndbusX/firmware/activateâ€™ attribute, the â€˜nmemX/firmware/activateâ€™
attribute indicates â€˜idleâ€™, â€˜armedâ€™, or â€˜busyâ€™. The state transitions
from â€˜armedâ€™ to â€˜idleâ€™ when the system is prepared to activate firmware,
firmware staged + state set to armed, and â€˜ndbusX/firmware/activateâ€™ is
triggered. After that activation event the nmemX/firmware/result
attribute reflects the state of the last activation as one of:”…””}”(hj€  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K;hh¶hžhubhö)”}”(hhh]”(hû)”}”(hŒOnone:
No runtime activation triggered since the last time the device was reset
”h]”hÊ)”}”(hŒNnone:
No runtime activation triggered since the last time the device was reset”h]”hŒNnone:
No runtime activation triggered since the last time the device was reset”…””}”(hj•  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KEhj‘  ubah}”(h]”h ]”h"]”h$]”h&]”uh1húhjŽ  hžhhŸh³h Nubhû)”}”(hŒ=success:
The last runtime activation completed successfully.
”h]”hÊ)”}”(hŒ<success:
The last runtime activation completed successfully.”h]”hŒ<success:
The last runtime activation completed successfully.”…””}”(hj­  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KHhj©  ubah}”(h]”h ]”h"]”h$]”h&]”uh1húhjŽ  hžhhŸh³h Nubhû)”}”(hŒFfail:
The last runtime activation failed for device-specific reasons.
”h]”hÊ)”}”(hŒEfail:
The last runtime activation failed for device-specific reasons.”h]”hŒEfail:
The last runtime activation failed for device-specific reasons.”…””}”(hjÅ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KKhjÁ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1húhjŽ  hžhhŸh³h Nubhû)”}”(hŒqnot_staged:
The last runtime activation failed due to a sequencing error of the
firmware image not being staged.
”h]”hÊ)”}”(hŒpnot_staged:
The last runtime activation failed due to a sequencing error of the
firmware image not being staged.”h]”hŒpnot_staged:
The last runtime activation failed due to a sequencing error of the
firmware image not being staged.”…””}”(hjÝ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KNhjÙ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1húhjŽ  hžhhŸh³h Nubhû)”}”(hŒ‹need_reset:
Runtime firmware activation failed, but the firmware can still be
activated via the legacy method of power-cycling the system.
”h]”hÊ)”}”(hŒŠneed_reset:
Runtime firmware activation failed, but the firmware can still be
activated via the legacy method of power-cycling the system.”h]”hŒŠneed_reset:
Runtime firmware activation failed, but the firmware can still be
activated via the legacy method of power-cycling the system.”…””}”(hjõ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KRhjñ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1húhjŽ  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”jb  jc  uh1hõhŸh³h KEhh¶hžhubhÊ)”}”(hŒ,[1]: https://docs.pmem.io/persistent-memory/”h]”(hŒ[1]: ”…””}”(hj  hžhhŸNh NubhŒ	reference”“”)”}”(hŒ'https://docs.pmem.io/persistent-memory/”h]”hŒ'https://docs.pmem.io/persistent-memory/”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j  uh1j  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KVhh¶hžhubeh}”(h]”Œ"nvdimm-runtime-firmware-activation”ah ]”h"]”Œ"nvdimm runtime firmware activation”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  sŒ	nametypes”}”j3  ‰sh}”j0  h¶sŒ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.