€•1_      Œ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/driver-api/mei/iamt”Œ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/driver-api/mei/iamt”Œ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/driver-api/mei/iamt”Œ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/driver-api/mei/iamt”Œ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/driver-api/mei/iamt”Œ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/driver-api/mei/iamt”Œ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ŸŒA/var/lib/git/docbuild/linux/Documentation/driver-api/mei/iamt.rst”h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ1Intel(R) Active Management Technology (Intel AMT)”h]”hŒ1Intel(R) Active Management Technology (Intel AMT)”…””}”(hh»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh¶hžhhŸh³h KubhŒ	paragraph”“”)”}”(hŒ£Prominent usage of the Intel ME Interface is to communicate with Intel(R)
Active Management Technology (Intel AMT) implemented in firmware running on
the Intel ME.”h]”hŒ£Prominent usage of the Intel ME Interface is to communicate with Intel(R)
Active Management Technology (Intel AMT) implemented in firmware running on
the Intel ME.”…””}”(hhËhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶hžhubhÊ)”}”(hŒ«Intel AMT provides the ability to manage a host remotely out-of-band (OOB)
even when the operating system running on the host processor has crashed or
is in a sleep state.”h]”hŒ«Intel AMT provides the ability to manage a host remotely out-of-band (OOB)
even when the operating system running on the host processor has crashed or
is in a sleep state.”…””}”(hhÙhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K
hh¶hžhubhŒdefinition_list”“”)”}”(hhh]”hŒdefinition_list_item”“”)”}”(hXÀ  Some examples of Intel AMT usage are:
- Monitoring hardware state and platform components
- Remote power off/on (useful for green computing or overnight IT
  maintenance)
- OS updates
- Storage of useful platform information such as software assets
- Built-in hardware KVM
- Selective network isolation of Ethernet and IP protocol flows based
  on policies set by a remote management console
- IDE device redirection from remote management console
”h]”(hŒterm”“”)”}”(hŒ%Some examples of Intel AMT usage are:”h]”hŒ%Some examples of Intel AMT usage are:”…””}”(hhôhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hòhŸh³h KhhîubhŒ
definition”“”)”}”(hhh]”hŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒ1Monitoring hardware state and platform components”h]”hÊ)”}”(hj  h]”hŒ1Monitoring hardware state and platform components”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj	  ubj  )”}”(hŒLRemote power off/on (useful for green computing or overnight IT
maintenance)”h]”hÊ)”}”(hŒLRemote power off/on (useful for green computing or overnight IT
maintenance)”h]”hŒLRemote power off/on (useful for green computing or overnight IT
maintenance)”…””}”(hj)  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj%  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj	  ubj  )”}”(hŒ
OS updates”h]”hÊ)”}”(hj?  h]”hŒ
OS updates”…””}”(hjA  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj=  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj	  ubj  )”}”(hŒ>Storage of useful platform information such as software assets”h]”hÊ)”}”(hjV  h]”hŒ>Storage of useful platform information such as software assets”…””}”(hjX  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KhjT  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj	  ubj  )”}”(hŒBuilt-in hardware KVM”h]”hÊ)”}”(hjm  h]”hŒBuilt-in hardware KVM”…””}”(hjo  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khjk  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj	  ubj  )”}”(hŒrSelective network isolation of Ethernet and IP protocol flows based
on policies set by a remote management console”h]”hÊ)”}”(hŒrSelective network isolation of Ethernet and IP protocol flows based
on policies set by a remote management console”h]”hŒrSelective network isolation of Ethernet and IP protocol flows based
on policies set by a remote management console”…””}”(hj†  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khj‚  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj	  ubj  )”}”(hŒ6IDE device redirection from remote management console
”h]”hÊ)”}”(hŒ5IDE device redirection from remote management console”h]”hŒ5IDE device redirection from remote management console”…””}”(hjž  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khjš  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj	  ubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1j  hŸh³h Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hhîubeh}”(h]”h ]”h"]”h$]”h&]”uh1hìhŸh³h Khhéubah}”(h]”h ]”h"]”h$]”h&]”uh1hçhh¶hžhhŸNh NubhÊ)”}”(hŒÇIntel AMT (OOB) communication is based on SOAP (deprecated
starting with Release 6.0) over HTTP/S or WS-Management protocol over
HTTP/S that are received from a remote management console application.”h]”hŒÇIntel AMT (OOB) communication is based on SOAP (deprecated
starting with Release 6.0) over HTTP/S or WS-Management protocol over
HTTP/S that are received from a remote management console application.”…””}”(hjÌ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Khh¶hžhubhÊ)”}”(hŒ‡For more information about Intel AMT:
https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm”h]”(hŒ&For more information about Intel AMT:
”…””}”(hjÚ  hžhhŸNh NubhŒ	reference”“”)”}”(hŒahttps://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm”h]”hŒahttps://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm”…””}”(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 Khh¶hžhubhµ)”}”(hhh]”(hº)”}”(hŒIntel AMT Applications”h]”hŒIntel AMT Applications”…””}”(hjü  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjù  hžhhŸh³h K"ubhŒblock_quote”“”)”}”(hXÉ  1) Intel Local Management Service (Intel LMS)

   Applications running locally on the platform communicate with Intel AMT Release
   2.0 and later releases in the same way that network applications do via SOAP
   over HTTP (deprecated starting with Release 6.0) or with WS-Management over
   SOAP over HTTP. This means that some Intel AMT features can be accessed from a
   local application using the same network interface as a remote application
   communicating with Intel AMT over the network.

   When a local application sends a message addressed to the local Intel AMT host
   name, the Intel LMS, which listens for traffic directed to the host name,
   intercepts the message and routes it to the Intel MEI.
   For more information:
   https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm
   Under "About Intel AMT" => "Local Access"

   For downloading Intel LMS:
   https://github.com/intel/lms

   The Intel LMS opens a connection using the Intel MEI driver to the Intel LMS
   firmware feature using a defined GUID and then communicates with the feature
   using a protocol called Intel AMT Port Forwarding Protocol (Intel APF protocol).
   The protocol is used to maintain multiple sessions with Intel AMT from a
   single application.

   See the protocol specification in the Intel AMT Software Development Kit (SDK)
   https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm
   Under "SDK Resources" => "Intel(R) vPro(TM) Gateway (MPS)"
   => "Information for Intel(R) vPro(TM) Gateway Developers"
   => "Description of the Intel AMT Port Forwarding (APF) Protocol"

2) Intel AMT Remote configuration using a Local Agent

   A Local Agent enables IT personnel to configure Intel AMT out-of-the-box
   without requiring installing additional data to enable setup. The remote
   configuration process may involve an ISV-developed remote configuration
   agent that runs on the host.
   For more information:
   https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm
   Under "Setup and Configuration of Intel AMT" =>
   "SDK Tools Supporting Setup and Configuration" =>
   "Using the Local Agent Sample"
”h]”hŒenumerated_list”“”)”}”(hhh]”(j  )”}”(hX;  Intel Local Management Service (Intel LMS)

Applications running locally on the platform communicate with Intel AMT Release
2.0 and later releases in the same way that network applications do via SOAP
over HTTP (deprecated starting with Release 6.0) or with WS-Management over
SOAP over HTTP. This means that some Intel AMT features can be accessed from a
local application using the same network interface as a remote application
communicating with Intel AMT over the network.

When a local application sends a message addressed to the local Intel AMT host
name, the Intel LMS, which listens for traffic directed to the host name,
intercepts the message and routes it to the Intel MEI.
For more information:
https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm
Under "About Intel AMT" => "Local Access"

For downloading Intel LMS:
https://github.com/intel/lms

The Intel LMS opens a connection using the Intel MEI driver to the Intel LMS
firmware feature using a defined GUID and then communicates with the feature
using a protocol called Intel AMT Port Forwarding Protocol (Intel APF protocol).
The protocol is used to maintain multiple sessions with Intel AMT from a
single application.

See the protocol specification in the Intel AMT Software Development Kit (SDK)
https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm
Under "SDK Resources" => "Intel(R) vPro(TM) Gateway (MPS)"
=> "Information for Intel(R) vPro(TM) Gateway Developers"
=> "Description of the Intel AMT Port Forwarding (APF) Protocol"
”h]”(hÊ)”}”(hŒ*Intel Local Management Service (Intel LMS)”h]”hŒ*Intel Local Management Service (Intel LMS)”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K$hj  ubhÊ)”}”(hX±  Applications running locally on the platform communicate with Intel AMT Release
2.0 and later releases in the same way that network applications do via SOAP
over HTTP (deprecated starting with Release 6.0) or with WS-Management over
SOAP over HTTP. This means that some Intel AMT features can be accessed from a
local application using the same network interface as a remote application
communicating with Intel AMT over the network.”h]”hX±  Applications running locally on the platform communicate with Intel AMT Release
2.0 and later releases in the same way that network applications do via SOAP
over HTTP (deprecated starting with Release 6.0) or with WS-Management over
SOAP over HTTP. This means that some Intel AMT features can be accessed from a
local application using the same network interface as a remote application
communicating with Intel AMT over the network.”…””}”(hj'  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K&hj  ubhÊ)”}”(hXq  When a local application sends a message addressed to the local Intel AMT host
name, the Intel LMS, which listens for traffic directed to the host name,
intercepts the message and routes it to the Intel MEI.
For more information:
https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm
Under "About Intel AMT" => "Local Access"”h]”(hŒæWhen a local application sends a message addressed to the local Intel AMT host
name, the Intel LMS, which listens for traffic directed to the host name,
intercepts the message and routes it to the Intel MEI.
For more information:
”…””}”(hj5  hžhhŸNh Nubjã  )”}”(hŒahttps://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm”h]”hŒahttps://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm”…””}”(hj=  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j?  uh1jâ  hj5  ubhŒ2
Under â€œAbout Intel AMTâ€ => â€œLocal Accessâ€”…””}”(hj5  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K-hj  ubhÊ)”}”(hŒ7For downloading Intel LMS:
https://github.com/intel/lms”h]”(hŒFor downloading Intel LMS:
”…””}”(hjV  hžhhŸNh Nubjã  )”}”(hŒhttps://github.com/intel/lms”h]”hŒhttps://github.com/intel/lms”…””}”(hj^  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j`  uh1jâ  hjV  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K4hj  ubhÊ)”}”(hXG  The Intel LMS opens a connection using the Intel MEI driver to the Intel LMS
firmware feature using a defined GUID and then communicates with the feature
using a protocol called Intel AMT Port Forwarding Protocol (Intel APF protocol).
The protocol is used to maintain multiple sessions with Intel AMT from a
single application.”h]”hXG  The Intel LMS opens a connection using the Intel MEI driver to the Intel LMS
firmware feature using a defined GUID and then communicates with the feature
using a protocol called Intel AMT Port Forwarding Protocol (Intel APF protocol).
The protocol is used to maintain multiple sessions with Intel AMT from a
single application.”…””}”(hjs  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K7hj  ubhÊ)”}”(hXf  See the protocol specification in the Intel AMT Software Development Kit (SDK)
https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm
Under "SDK Resources" => "Intel(R) vPro(TM) Gateway (MPS)"
=> "Information for Intel(R) vPro(TM) Gateway Developers"
=> "Description of the Intel AMT Port Forwarding (APF) Protocol"”h]”(hŒOSee the protocol specification in the Intel AMT Software Development Kit (SDK)
”…””}”(hj  hžhhŸNh Nubjã  )”}”(hŒahttps://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm”h]”hŒahttps://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm”…””}”(hj‰  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j‹  uh1jâ  hj  ubhŒÆ
Under â€œSDK Resourcesâ€ => â€œIntel(R) vPro(TM) Gateway (MPS)â€
=> â€œInformation for Intel(R) vPro(TM) Gateway Developersâ€
=> â€œDescription of the Intel AMT Port Forwarding (APF) Protocolâ€”…””}”(hj  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K=hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj  )”}”(hX$  Intel AMT Remote configuration using a Local Agent

A Local Agent enables IT personnel to configure Intel AMT out-of-the-box
without requiring installing additional data to enable setup. The remote
configuration process may involve an ISV-developed remote configuration
agent that runs on the host.
For more information:
https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm
Under "Setup and Configuration of Intel AMT" =>
"SDK Tools Supporting Setup and Configuration" =>
"Using the Local Agent Sample"
”h]”(hÊ)”}”(hŒ2Intel AMT Remote configuration using a Local Agent”h]”hŒ2Intel AMT Remote configuration using a Local Agent”…””}”(hj¬  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KChj¨  ubhÊ)”}”(hXï  A Local Agent enables IT personnel to configure Intel AMT out-of-the-box
without requiring installing additional data to enable setup. The remote
configuration process may involve an ISV-developed remote configuration
agent that runs on the host.
For more information:
https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm
Under "Setup and Configuration of Intel AMT" =>
"SDK Tools Supporting Setup and Configuration" =>
"Using the Local Agent Sample"”h]”(hX  A Local Agent enables IT personnel to configure Intel AMT out-of-the-box
without requiring installing additional data to enable setup. The remote
configuration process may involve an ISV-developed remote configuration
agent that runs on the host.
For more information:
”…””}”(hjº  hžhhŸNh Nubjã  )”}”(hŒahttps://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm”h]”hŒahttps://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm”…””}”(hjÂ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jÄ  uh1jâ  hjº  ubhŒ
Under â€œSetup and Configuration of Intel AMTâ€ =>
â€œSDK Tools Supporting Setup and Configurationâ€ =>
â€œUsing the Local Agent Sampleâ€”…””}”(hjº  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KEhj¨  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œarabic”Œprefix”hŒsuffix”Œ)”uh1j  hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j
  hŸh³h K$hjù  hžhubeh}”(h]”Œintel-amt-applications”ah ]”h"]”Œintel amt applications”ah$]”h&]”uh1h´hh¶hžhhŸh³h K"ubhµ)”}”(hhh]”(hº)”}”(hŒIntel AMT OS Health Watchdog”h]”hŒIntel AMT OS Health Watchdog”…””}”(hjý  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hjú  hžhhŸh³h KPubhÊ)”}”(hX  The Intel AMT Watchdog is an OS Health (Hang/Crash) watchdog.
Whenever the OS hangs or crashes, Intel AMT will send an event
to any subscriber to this event. This mechanism means that
IT knows when a platform crashes even when there is a hard failure on the host.”h]”hX  The Intel AMT Watchdog is an OS Health (Hang/Crash) watchdog.
Whenever the OS hangs or crashes, Intel AMT will send an event
to any subscriber to this event. This mechanism means that
IT knows when a platform crashes even when there is a hard failure on the host.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KRhjú  hžhubhè)”}”(hhh]”hí)”}”(hX
  The Intel AMT Watchdog is composed of two parts:
1) Firmware feature - receives the heartbeats
   and sends an event when the heartbeats stop.
2) Intel MEI iAMT watchdog driver - connects to the watchdog feature,
   configures the watchdog and sends the heartbeats.
”h]”(hó)”}”(hŒ0The Intel AMT Watchdog is composed of two parts:”h]”hŒ0The Intel AMT Watchdog is composed of two parts:”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hòhŸh³h K[hj  ubj  )”}”(hhh]”j  )”}”(hhh]”(j  )”}”(hŒWFirmware feature - receives the heartbeats
and sends an event when the heartbeats stop.”h]”hÊ)”}”(hŒWFirmware feature - receives the heartbeats
and sends an event when the heartbeats stop.”h]”hŒWFirmware feature - receives the heartbeats
and sends an event when the heartbeats stop.”…””}”(hj8  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KXhj4  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj1  ubj  )”}”(hŒuIntel MEI iAMT watchdog driver - connects to the watchdog feature,
configures the watchdog and sends the heartbeats.
”h]”hÊ)”}”(hŒtIntel MEI iAMT watchdog driver - connects to the watchdog feature,
configures the watchdog and sends the heartbeats.”h]”hŒtIntel MEI iAMT watchdog driver - connects to the watchdog feature,
configures the watchdog and sends the heartbeats.”…””}”(hjP  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h KZhjL  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj1  ubeh}”(h]”h ]”h"]”h$]”h&]”jç  jè  jé  hjê  jë  uh1j  hj.  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hìhŸh³h K[hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hçhjú  hžhhŸNh NubhÊ)”}”(hŒµThe Intel iAMT watchdog MEI driver uses the kernel watchdog API to configure
the Intel AMT Watchdog and to send heartbeats to it. The default timeout of the
watchdog is 120 seconds.”h]”hŒµThe Intel iAMT watchdog MEI driver uses the kernel watchdog API to configure
the Intel AMT Watchdog and to send heartbeats to it. The default timeout of the
watchdog is 120 seconds.”…””}”(hj|  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h K]hjú  hžhubhÊ)”}”(hŒ”If the Intel AMT is not enabled in the firmware then the watchdog client won't enumerate
on the me client bus and watchdog devices won't be exposed.”h]”hŒ˜If the Intel AMT is not enabled in the firmware then the watchdog client wonâ€™t enumerate
on the me client bus and watchdog devices wonâ€™t be exposed.”…””}”(hjŠ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kahjú  hžhubhÊ)”}”(hŒ---
linux-mei@linux.intel.com”h]”(hŒ---
”…””}”(hj˜  hžhhŸNh Nubjã  )”}”(hŒlinux-mei@linux.intel.com”h]”hŒlinux-mei@linux.intel.com”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ mailto:linux-mei@linux.intel.com”uh1jâ  hj˜  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÉhŸh³h Kdhjú  hžhubeh}”(h]”Œintel-amt-os-health-watchdog”ah ]”h"]”Œintel amt os health watchdog”ah$]”h&]”uh1h´hh¶hžhhŸh³h KPubeh}”(h]”Œ.intel-r-active-management-technology-intel-amt”ah ]”h"]”Œ1intel(r) active management technology (intel amt)”ah$]”h&]”uh1h´hhhž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”}”(jÃ  jÀ  j÷  jô  j»  j¸  uŒ	nametypes”}”(jÃ  ‰j÷  ‰j»  ‰uh}”(jÀ  h¶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”]”hŒsystem_message”“”)”}”(hhh]”hÊ)”}”(hŒ`Possible incomplete section title.
Treating the overline as ordinary text because it's so short.”h]”hŒbPossible incomplete section title.
Treating the overline as ordinary text because itâ€™s so short.”…””}”(hjP  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÉhjM  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”ŒINFO”Œline”KdŒsource”h³uh1jK  hjú  hžhhŸh³h NubaŒtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.