Intel® Core™ Ultra 200V Series Processors SOC I/O Registers
| ID | Date | Version | Classification |
|---|---|---|---|
| 831520 | 09/03/2024 | 001 | Public |
Context Command Register (CCMD_REG_0_0_0_VTDBAR) – Offset 20028
Register to manage context cache. The act of writing the uppermost byte of the CCMD_REG with the ICC field Set causes the hardware to perform the context-cache invalidation.
| Bit Range | Default | Access | Field Name and Description |
|---|---|---|---|
| 63 | 0h | RW/V | Invalidate Context Cache (ICC) Software requests invalidation of context-cache by setting this field. Software must also set the requested invalidation granularity by programming the CIRG field. Software must read back and check the ICC field is Clear to confirm the invalidation is complete. Software must not update this register when this field is set. Hardware clears the ICC field to indicate the invalidation request is complete. Hardware also indicates the granularity at which the invalidation operation was performed through the CAIG field. Software must submit a context-cache invalidation request through this field only when there are no invalidation requests pending at this remapping hardware unit. Since information from the context-cache may be used by hardware to tag IOTLB entries, software must perform domain-selective (or global) invalidation of IOTLB after the context cache invalidation has completed. Hardware implementations reporting write-buffer flushing requirement (RWBF=1 in Capability register) must implicitly perform a write buffer flush before invalidating the context cache. |
| 62:61 | 0h | RW | Context Invalidation Request Granularity (CIRG) Software provides the requested invalidation granularity through this field when setting the ICC field:
Hardware implementations may process an invalidation request by performing invalidation at a coarser granularity than requested. Hardware indicates completion of the invalidation request by clearing the ICC field. At this time, hardware also indicates the granularity at which the actual invalidation was performed through the CAIG field. |
| 60:59 | 1h | RO/V | Context Actual Invalidation Granularity (CAIG) Hardware reports the granularity at which an invalidation request was processed through the CAIG field at the time of reporting invalidation completion (by clearing the ICC field). The following are the encodings for this field:
|
| 58:34 | 0h | RO | Reserved |
| 33:32 | 0h | WO | Function Mask (FM) Software may use the Function Mask to perform device-selective invalidations on behalf of devices supporting PCI Express Phantom Functions...This field specifies which bits of the function number portion (least significant three bits) of the SID field to mask when performing device-selective invalidations. The following encodings are defined for this field:
The context-entries corresponding to all the source-ids specified through the FM and SID fields must have to the domain-id specified in the DID field. |
| 31:16 | 0h | WO | Source-ID (SID) Indicates the source-id of the device whose corresponding context-entry needs to be selectively invalidated. This field along with the FM field must be programmed by software for device-selective invalidation requests. |
| 15:0 | 0h | RW | Domain-ID (DID) Indicates the id of the domain whose context-entries need to be selectively invalidated. This field must be programmed by software for both domain-selective and device-selective invalidation requests. The Capability register reports the domain-id width supported by hardware. Software must ensure that the value written to this field is within this limit. Hardware may ignore and not implement bits15:N, where N is the supported domain-id width reported in the Capability register. |