91 lines · plain
1What: /sys/bus/auxiliary/devices/intel_vsec.sdsi.X2Date: Feb 20223KernelVersion: 5.184Contact: "David E. Box" <david.e.box@linux.intel.com>5Description:6 This directory contains interface files for accessing Intel7 On Demand (formerly Software Defined Silicon or SDSi) features8 on a CPU. X represents the socket instance (though not the9 socket ID). The socket ID is determined by reading the10 registers file and decoding it per the specification.11 12 Some files communicate with On Demand hardware through a13 mailbox. Should the operation fail, one of the following error14 codes may be returned:15 16 ========== =====17 Error Code Cause18 ========== =====19 EIO General mailbox failure. Log may indicate cause.20 EBUSY Mailbox is owned by another agent.21 EPERM On Demand capability is not enabled in hardware.22 EPROTO Failure in mailbox protocol detected by driver.23 See log for details.24 EOVERFLOW For provision commands, the size of the data25 exceeds what may be written.26 ESPIPE Seeking is not allowed.27 ETIMEDOUT Failure to complete mailbox transaction in time.28 ========== =====29 30What: /sys/bus/auxiliary/devices/intel_vsec.sdsi.X/guid31Date: Feb 202232KernelVersion: 5.1833Contact: "David E. Box" <david.e.box@linux.intel.com>34Description:35 (RO) The GUID for the registers file. The GUID identifies36 the layout of the registers file in this directory.37 Information about the register layouts for a particular GUID38 is available at http://github.com/intel/intel-sdsi39 40What: /sys/bus/auxiliary/devices/intel_vsec.sdsi.X/registers41Date: Feb 202242KernelVersion: 5.1843Contact: "David E. Box" <david.e.box@linux.intel.com>44Description:45 (RO) Contains information needed by applications to provision46 a CPU and monitor status information. The layout of this file47 is determined by the GUID in this directory. Information about48 the layout for a particular GUID is available at49 http://github.com/intel/intel-sdsi50 51What: /sys/bus/auxiliary/devices/intel_vsec.sdsi.X/provision_akc52Date: Feb 202253KernelVersion: 5.1854Contact: "David E. Box" <david.e.box@linux.intel.com>55Description:56 (WO) Used to write an Authentication Key Certificate (AKC) to57 the On Demand NVRAM for the CPU. The AKC is used to authenticate58 a Capability Activation Payload. Mailbox command.59 60What: /sys/bus/auxiliary/devices/intel_vsec.sdsi.X/provision_cap61Date: Feb 202262KernelVersion: 5.1863Contact: "David E. Box" <david.e.box@linux.intel.com>64Description:65 (WO) Used to write a Capability Activation Payload (CAP) to the66 On Demand NVRAM for the CPU. CAPs are used to activate a given67 CPU feature. A CAP is validated by On Demand hardware using a68 previously provisioned AKC file. Upon successful authentication,69 the CPU configuration is updated. A cold reboot is required to70 fully activate the feature. Mailbox command.71 72What: /sys/bus/auxiliary/devices/intel_vsec.sdsi.X/meter_certificate73Date: Nov 202274KernelVersion: 6.275Contact: "David E. Box" <david.e.box@linux.intel.com>76Description:77 (RO) Used to read back the current meter certificate for the CPU78 from Intel On Demand hardware. The meter certificate contains79 utilization metrics of On Demand enabled features. Mailbox80 command.81 82What: /sys/bus/auxiliary/devices/intel_vsec.sdsi.X/state_certificate83Date: Feb 202284KernelVersion: 5.1885Contact: "David E. Box" <david.e.box@linux.intel.com>86Description:87 (RO) Used to read back the current state certificate for the CPU88 from On Demand hardware. The state certificate contains89 information about the current licenses on the CPU. Mailbox90 command.91