Table of Contents
Advertisement
7.1.5.8
Originator Retry and Timeout Policy
The PECI originator may need to retry a command if the processor PECI client responds
with a 'response timeout' completion code or a bad Read FCS. In each instance, the
processor PECI client may have started the operation but not completed it yet. When
the 'retry' bit is set, the PECI client will ignore a new request if it exactly matches a
previous valid request.
The processor PECI client will not clear the semaphore that was acquired to service the
request until the originator sends the 'retry' request in a timely fashion to successfully
retrieve the response data. In the absence of any automatic timeouts, this could tie up
shared resources and result in artificial bandwidth conflicts.
7.1.5.9
Enumerating PECI Client Capabilities
The PECI host originator should be designed to support all optional but desirable
features from all processors of interest. Each feature has a discovery method and
response code that indicates availability on the destination PECI client.
The first step in the enumeration process would be for the PECI host to confirm the
Revision Number through the use of the GetDIB() command. The revision number
returned by the PECI client processor always maps to the revision number of the PECI
specification that it is designed to.
The next step in the enumeration process is to utilize the desired command suite in a
real execution context. If the Write FCS response is an Abort FCS or if the data
returned includes an "Unknown/Invalid Request" completion code (0x90), then the
command is unsupported.
Enumerating known commands without real, execution context data, or attempting
undefined commands, is dangerous because a write command could result in
unexpected behavior if the data is not properly formatted. Methods for enumerating
write commands using carefully constructed and innocuous data are possible, but are
not guaranteed by the PECI client definition.
This enumeration procedure is not robust enough to detect differences in bit definitions
or data interpretation in the message payload or client response. Instead, it is only
designed to enumerate discrete features.
7.1.6
Multi-Domain Commands
The Intel
3930K processor, and Intel
domains, but it is possible that future products will, and the following tables are
included as a reference for domain-specific definitions.
Table 7-20. Domain ID Definition
Domain ID
0b01
0b10
92
®
Core™ i7-3960X, i7-3970X processor Extreme Edition, Intel
®
Core™ i7-3820 processor does not support multiple
Domain Number
0
1
Thermal/Mechanical Specifications and Design Guide
PECI Interface
®
Core™ i7-
Advertisement
Table of Contents
