Intel X5675 BX80614X5675 Manual De Usuario
Los códigos de productos
BX80614X5675
Intel
®
Xeon
®
Processor 5600 Series Datasheet Volume 1
155
Thermal Specifications
cleared. In the event that this timeout occurs, the originating agent will receive a failed
completion code upon issuing a MbxGet() command, or even worse, it may receive
corrupt data if this MbxGet() command so happens to be interleaved with an
MbxSend() from another process. Please refer to
completion code upon issuing a MbxGet() command, or even worse, it may receive
corrupt data if this MbxGet() command so happens to be interleaved with an
MbxSend() from another process. Please refer to
for more information
regarding failed completion codes from MbxGet() commands.
Timeouts are undesirable, and the best way to avoid them and guarantee valid data is
for the originating agent to always issue MbxGet() commands immediately following
MbxSend() commands.
for the originating agent to always issue MbxGet() commands immediately following
MbxSend() commands.
If the timeout policy is too restrictive, it can be disabled. BIOS may write
MSR_MISC_POWER_MGMT (0x1AA), bit 11 to 0b1 in order to force a disable of this
automatic timeout.
MSR_MISC_POWER_MGMT (0x1AA), bit 11 to 0b1 in order to force a disable of this
automatic timeout.
7.3.2.9.5
Response Latency
The PECI mailbox interface is designed to have response data available within plenty of
margin to allow for back-to-back MbxSend() and MbxGet() requests. However, under
rare circumstances that are out of the scope of this specification, it is possible that the
response data is not available when the MbxGet() command is issued. Under these
circumstances, the MbxGet() command will respond with an Abort FCS and the
originator should re-issue the MbxGet() request.
margin to allow for back-to-back MbxSend() and MbxGet() requests. However, under
rare circumstances that are out of the scope of this specification, it is possible that the
response data is not available when the MbxGet() command is issued. Under these
circumstances, the MbxGet() command will respond with an Abort FCS and the
originator should re-issue the MbxGet() request.
7.3.3
Multi-Domain Commands
The Intel Xeon processor 5600 series does not support multiple domains, but it is
possible that future products will, and the following tables are included as a reference
for domain-specific definitions.
possible that future products will, and the following tables are included as a reference
for domain-specific definitions.
7.3.4
Client Responses
7.3.4.1
Abort FCS
The Client responds with an Abort FCS under the following conditions:
• The decoded command is not understood or not supported on this processor (this
includes good command codes with bad Read Length or Write Length bytes).
• Data is not ready.
Table 7-31. Domain ID Definition
Domain ID
Domain Number
0b01
0
0b10
1
Table 7-32. Multi-Domain Command Code Reference
Command Name
Domain 0 Code
Domain 1 Code
GetTemp()
0x01
0x02
PCIConfigRd()
0xC1
0xC2
PCIConfigWr()
0xC5
0xC6
MbxSend()
0xD1
0xD2
MbxGet()
0xD5
0xD6