hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
# -*- Mode: Python -*-
|
|
|
|
# vim: filetype=python
|
|
|
|
|
|
|
|
##
|
|
|
|
# = CXL devices
|
|
|
|
##
|
|
|
|
|
2023-05-30 15:36:01 +02:00
|
|
|
##
|
|
|
|
# @CxlEventLog:
|
|
|
|
#
|
|
|
|
# CXL has a number of separate event logs for different types of
|
|
|
|
# events. Each such event log is handled and signaled independently.
|
|
|
|
#
|
|
|
|
# @informational: Information Event Log
|
|
|
|
#
|
|
|
|
# @warning: Warning Event Log
|
|
|
|
#
|
|
|
|
# @failure: Failure Event Log
|
|
|
|
#
|
|
|
|
# @fatal: Fatal Event Log
|
|
|
|
#
|
|
|
|
# Since: 8.1
|
|
|
|
##
|
|
|
|
{ 'enum': 'CxlEventLog',
|
|
|
|
'data': ['informational',
|
|
|
|
'warning',
|
|
|
|
'failure',
|
|
|
|
'fatal']
|
|
|
|
}
|
|
|
|
|
|
|
|
##
|
|
|
|
# @cxl-inject-general-media-event:
|
|
|
|
#
|
|
|
|
# Inject an event record for a General Media Event (CXL r3.0
|
|
|
|
# 8.2.9.2.1.1). This event type is reported via one of the event logs
|
|
|
|
# specified via the log parameter.
|
|
|
|
#
|
|
|
|
# @path: CXL type 3 device canonical QOM path
|
|
|
|
#
|
|
|
|
# @log: event log to add the event to
|
|
|
|
#
|
|
|
|
# @flags: Event Record Flags. See CXL r3.0 Table 8-42 Common Event
|
|
|
|
# Record Format, Event Record Flags for subfield definitions.
|
|
|
|
#
|
|
|
|
# @dpa: Device Physical Address (relative to @path device). Note
|
|
|
|
# lower bits include some flags. See CXL r3.0 Table 8-43 General
|
|
|
|
# Media Event Record, Physical Address.
|
|
|
|
#
|
|
|
|
# @descriptor: Memory Event Descriptor with additional memory event
|
|
|
|
# information. See CXL r3.0 Table 8-43 General Media Event
|
|
|
|
# Record, Memory Event Descriptor for bit definitions.
|
|
|
|
#
|
|
|
|
# @type: Type of memory event that occurred. See CXL r3.0 Table 8-43
|
|
|
|
# General Media Event Record, Memory Event Type for possible
|
|
|
|
# values.
|
|
|
|
#
|
|
|
|
# @transaction-type: Type of first transaction that caused the event
|
|
|
|
# to occur. See CXL r3.0 Table 8-43 General Media Event Record,
|
|
|
|
# Transaction Type for possible values.
|
|
|
|
#
|
|
|
|
# @channel: The channel of the memory event location. A channel is an
|
|
|
|
# interface that can be independently accessed for a transaction.
|
|
|
|
#
|
|
|
|
# @rank: The rank of the memory event location. A rank is a set of
|
|
|
|
# memory devices on a channel that together execute a transaction.
|
|
|
|
#
|
|
|
|
# @device: Bitmask that represents all devices in the rank associated
|
|
|
|
# with the memory event location.
|
|
|
|
#
|
|
|
|
# @component-id: Device specific component identifier for the event.
|
|
|
|
# May describe a field replaceable sub-component of the device.
|
|
|
|
#
|
|
|
|
# Since: 8.1
|
|
|
|
##
|
|
|
|
{ 'command': 'cxl-inject-general-media-event',
|
|
|
|
'data': { 'path': 'str', 'log': 'CxlEventLog', 'flags': 'uint8',
|
|
|
|
'dpa': 'uint64', 'descriptor': 'uint8',
|
|
|
|
'type': 'uint8', 'transaction-type': 'uint8',
|
|
|
|
'*channel': 'uint8', '*rank': 'uint8',
|
|
|
|
'*device': 'uint32', '*component-id': 'str' } }
|
|
|
|
|
hw/cxl/events: Add injection of DRAM events
Defined in CXL r3.0 8.2.9.2.1.2 DRAM Event Record, this event
provides information related to DRAM devices.
Example injection command in QMP:
{ "execute": "cxl-inject-dram-event",
"arguments": {
"path": "/machine/peripheral/cxl-mem0",
"log": "informational",
"flags": 1,
"dpa": 1000,
"descriptor": 3,
"type": 3,
"transaction-type": 192,
"channel": 3,
"rank": 17,
"nibble-mask": 37421234,
"bank-group": 7,
"bank": 11,
"row": 2,
"column": 77,
"correction-mask": [33, 44, 55,66]
}}
Acked-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Fan Ni <fan.ni@samsung.com>
Reviewed-by: Ira Weiny <ira.weiny@intel.com>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230530133603.16934-7-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-05-30 15:36:02 +02:00
|
|
|
##
|
|
|
|
# @cxl-inject-dram-event:
|
|
|
|
#
|
|
|
|
# Inject an event record for a DRAM Event (CXL r3.0 8.2.9.2.1.2).
|
|
|
|
# This event type is reported via one of the event logs specified via
|
|
|
|
# the log parameter.
|
|
|
|
#
|
|
|
|
# @path: CXL type 3 device canonical QOM path
|
|
|
|
#
|
|
|
|
# @log: Event log to add the event to
|
|
|
|
#
|
|
|
|
# @flags: Event Record Flags. See CXL r3.0 Table 8-42 Common Event
|
|
|
|
# Record Format, Event Record Flags for subfield definitions.
|
|
|
|
#
|
|
|
|
# @dpa: Device Physical Address (relative to @path device). Note
|
|
|
|
# lower bits include some flags. See CXL r3.0 Table 8-44 DRAM
|
|
|
|
# Event Record, Physical Address.
|
|
|
|
#
|
|
|
|
# @descriptor: Memory Event Descriptor with additional memory event
|
|
|
|
# information. See CXL r3.0 Table 8-44 DRAM Event Record, Memory
|
|
|
|
# Event Descriptor for bit definitions.
|
|
|
|
#
|
|
|
|
# @type: Type of memory event that occurred. See CXL r3.0 Table 8-44
|
|
|
|
# DRAM Event Record, Memory Event Type for possible values.
|
|
|
|
#
|
|
|
|
# @transaction-type: Type of first transaction that caused the event
|
|
|
|
# to occur. See CXL r3.0 Table 8-44 DRAM Event Record,
|
|
|
|
# Transaction Type for possible values.
|
|
|
|
#
|
|
|
|
# @channel: The channel of the memory event location. A channel is an
|
|
|
|
# interface that can be independently accessed for a transaction.
|
|
|
|
#
|
|
|
|
# @rank: The rank of the memory event location. A rank is a set of
|
|
|
|
# memory devices on a channel that together execute a transaction.
|
|
|
|
#
|
|
|
|
# @nibble-mask: Identifies one or more nibbles that the error affects
|
|
|
|
#
|
|
|
|
# @bank-group: Bank group of the memory event location, incorporating
|
|
|
|
# a number of Banks.
|
|
|
|
#
|
|
|
|
# @bank: Bank of the memory event location. A single bank is accessed
|
|
|
|
# per read or write of the memory.
|
|
|
|
#
|
|
|
|
# @row: Row address within the DRAM.
|
|
|
|
#
|
|
|
|
# @column: Column address within the DRAM.
|
|
|
|
#
|
|
|
|
# @correction-mask: Bits within each nibble. Used in order of bits
|
|
|
|
# set in the nibble-mask. Up to 4 nibbles may be covered.
|
|
|
|
#
|
|
|
|
# Since: 8.1
|
|
|
|
##
|
|
|
|
{ 'command': 'cxl-inject-dram-event',
|
|
|
|
'data': { 'path': 'str', 'log': 'CxlEventLog', 'flags': 'uint8',
|
|
|
|
'dpa': 'uint64', 'descriptor': 'uint8',
|
|
|
|
'type': 'uint8', 'transaction-type': 'uint8',
|
|
|
|
'*channel': 'uint8', '*rank': 'uint8', '*nibble-mask': 'uint32',
|
|
|
|
'*bank-group': 'uint8', '*bank': 'uint8', '*row': 'uint32',
|
|
|
|
'*column': 'uint16', '*correction-mask': [ 'uint64' ]
|
|
|
|
}}
|
|
|
|
|
2023-05-30 15:36:03 +02:00
|
|
|
##
|
|
|
|
# @cxl-inject-memory-module-event:
|
|
|
|
#
|
|
|
|
# Inject an event record for a Memory Module Event (CXL r3.0
|
2024-03-22 15:09:08 +01:00
|
|
|
# 8.2.9.2.1.3). This event includes a copy of the Device Health info
|
|
|
|
# at the time of the event.
|
2023-05-30 15:36:03 +02:00
|
|
|
#
|
|
|
|
# @path: CXL type 3 device canonical QOM path
|
|
|
|
#
|
|
|
|
# @log: Event Log to add the event to
|
|
|
|
#
|
|
|
|
# @flags: Event Record Flags. See CXL r3.0 Table 8-42 Common Event
|
|
|
|
# Record Format, Event Record Flags for subfield definitions.
|
|
|
|
#
|
|
|
|
# @type: Device Event Type. See CXL r3.0 Table 8-45 Memory Module
|
|
|
|
# Event Record for bit definitions for bit definiions.
|
|
|
|
#
|
|
|
|
# @health-status: Overall health summary bitmap. See CXL r3.0 Table
|
|
|
|
# 8-100 Get Health Info Output Payload, Health Status for bit
|
|
|
|
# definitions.
|
|
|
|
#
|
|
|
|
# @media-status: Overall media health summary. See CXL r3.0 Table
|
|
|
|
# 8-100 Get Health Info Output Payload, Media Status for bit
|
|
|
|
# definitions.
|
|
|
|
#
|
|
|
|
# @additional-status: See CXL r3.0 Table 8-100 Get Health Info Output
|
|
|
|
# Payload, Additional Status for subfield definitions.
|
|
|
|
#
|
|
|
|
# @life-used: Percentage (0-100) of factory expected life span.
|
|
|
|
#
|
|
|
|
# @temperature: Device temperature in degrees Celsius.
|
|
|
|
#
|
2023-07-20 09:16:09 +02:00
|
|
|
# @dirty-shutdown-count: Number of times the device has been unable to
|
|
|
|
# determine whether data loss may have occurred.
|
2023-05-30 15:36:03 +02:00
|
|
|
#
|
|
|
|
# @corrected-volatile-error-count: Total number of correctable errors
|
|
|
|
# in volatile memory.
|
|
|
|
#
|
|
|
|
# @corrected-persistent-error-count: Total number of correctable
|
|
|
|
# errors in persistent memory
|
|
|
|
#
|
|
|
|
# Since: 8.1
|
|
|
|
##
|
|
|
|
{ 'command': 'cxl-inject-memory-module-event',
|
|
|
|
'data': { 'path': 'str', 'log': 'CxlEventLog', 'flags' : 'uint8',
|
|
|
|
'type': 'uint8', 'health-status': 'uint8',
|
|
|
|
'media-status': 'uint8', 'additional-status': 'uint8',
|
|
|
|
'life-used': 'uint8', 'temperature' : 'int16',
|
|
|
|
'dirty-shutdown-count': 'uint32',
|
|
|
|
'corrected-volatile-error-count': 'uint32',
|
|
|
|
'corrected-persistent-error-count': 'uint32'
|
|
|
|
}}
|
|
|
|
|
2023-05-26 19:00:08 +02:00
|
|
|
##
|
|
|
|
# @cxl-inject-poison:
|
|
|
|
#
|
|
|
|
# Poison records indicate that a CXL memory device knows that a
|
|
|
|
# particular memory region may be corrupted. This may be because of
|
|
|
|
# locally detected errors (e.g. ECC failure) or poisoned writes
|
|
|
|
# received from other components in the system. This injection
|
|
|
|
# mechanism enables testing of the OS handling of poison records which
|
|
|
|
# may be queried via the CXL mailbox.
|
|
|
|
#
|
|
|
|
# @path: CXL type 3 device canonical QOM path
|
|
|
|
#
|
|
|
|
# @start: Start address; must be 64 byte aligned.
|
|
|
|
#
|
|
|
|
# @length: Length of poison to inject; must be a multiple of 64 bytes.
|
|
|
|
#
|
|
|
|
# Since: 8.1
|
|
|
|
##
|
|
|
|
{ 'command': 'cxl-inject-poison',
|
|
|
|
'data': { 'path': 'str', 'start': 'uint64', 'length': 'size' }}
|
|
|
|
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
##
|
|
|
|
# @CxlUncorErrorType:
|
|
|
|
#
|
2023-04-28 12:54:29 +02:00
|
|
|
# Type of uncorrectable CXL error to inject. These errors are
|
|
|
|
# reported via an AER uncorrectable internal error with additional
|
|
|
|
# information logged at the CXL device.
|
|
|
|
#
|
|
|
|
# @cache-data-parity: Data error such as data parity or data ECC error
|
|
|
|
# CXL.cache
|
|
|
|
#
|
|
|
|
# @cache-address-parity: Address parity or other errors associated
|
|
|
|
# with the address field on CXL.cache
|
|
|
|
#
|
|
|
|
# @cache-be-parity: Byte enable parity or other byte enable errors on
|
|
|
|
# CXL.cache
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
#
|
|
|
|
# @cache-data-ecc: ECC error on CXL.cache
|
2023-04-28 12:54:29 +02:00
|
|
|
#
|
|
|
|
# @mem-data-parity: Data error such as data parity or data ECC error
|
|
|
|
# on CXL.mem
|
|
|
|
#
|
|
|
|
# @mem-address-parity: Address parity or other errors associated with
|
|
|
|
# the address field on CXL.mem
|
|
|
|
#
|
|
|
|
# @mem-be-parity: Byte enable parity or other byte enable errors on
|
|
|
|
# CXL.mem.
|
|
|
|
#
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
# @mem-data-ecc: Data ECC error on CXL.mem.
|
2023-04-28 12:54:29 +02:00
|
|
|
#
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
# @reinit-threshold: REINIT threshold hit.
|
2023-04-28 12:54:29 +02:00
|
|
|
#
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
# @rsvd-encoding: Received unrecognized encoding.
|
2023-04-28 12:54:29 +02:00
|
|
|
#
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
# @poison-received: Received poison from the peer.
|
2023-04-28 12:54:29 +02:00
|
|
|
#
|
|
|
|
# @receiver-overflow: Buffer overflows (first 3 bits of header log
|
|
|
|
# indicate which)
|
|
|
|
#
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
# @internal: Component specific error
|
2023-04-28 12:54:29 +02:00
|
|
|
#
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
# @cxl-ide-tx: Integrity and data encryption tx error.
|
2023-04-28 12:54:29 +02:00
|
|
|
#
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
# @cxl-ide-rx: Integrity and data encryption rx error.
|
|
|
|
#
|
|
|
|
# Since: 8.0
|
|
|
|
##
|
|
|
|
|
|
|
|
{ 'enum': 'CxlUncorErrorType',
|
|
|
|
'data': ['cache-data-parity',
|
|
|
|
'cache-address-parity',
|
|
|
|
'cache-be-parity',
|
|
|
|
'cache-data-ecc',
|
|
|
|
'mem-data-parity',
|
|
|
|
'mem-address-parity',
|
|
|
|
'mem-be-parity',
|
|
|
|
'mem-data-ecc',
|
|
|
|
'reinit-threshold',
|
|
|
|
'rsvd-encoding',
|
|
|
|
'poison-received',
|
|
|
|
'receiver-overflow',
|
|
|
|
'internal',
|
|
|
|
'cxl-ide-tx',
|
|
|
|
'cxl-ide-rx'
|
|
|
|
]
|
|
|
|
}
|
|
|
|
|
|
|
|
##
|
|
|
|
# @CXLUncorErrorRecord:
|
|
|
|
#
|
|
|
|
# Record of a single error including header log.
|
|
|
|
#
|
|
|
|
# @type: Type of error
|
2023-04-28 12:54:29 +02:00
|
|
|
#
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
# @header: 16 DWORD of header.
|
|
|
|
#
|
|
|
|
# Since: 8.0
|
|
|
|
##
|
|
|
|
{ 'struct': 'CXLUncorErrorRecord',
|
|
|
|
'data': {
|
|
|
|
'type': 'CxlUncorErrorType',
|
|
|
|
'header': [ 'uint32' ]
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
##
|
|
|
|
# @cxl-inject-uncorrectable-errors:
|
|
|
|
#
|
2023-04-28 12:54:29 +02:00
|
|
|
# Command to allow injection of multiple errors in one go. This
|
|
|
|
# allows testing of multiple header log handling in the OS.
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
#
|
|
|
|
# @path: CXL Type 3 device canonical QOM path
|
2023-04-28 12:54:29 +02:00
|
|
|
#
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
# @errors: Errors to inject
|
|
|
|
#
|
|
|
|
# Since: 8.0
|
|
|
|
##
|
|
|
|
{ 'command': 'cxl-inject-uncorrectable-errors',
|
|
|
|
'data': { 'path': 'str',
|
|
|
|
'errors': [ 'CXLUncorErrorRecord' ] }}
|
|
|
|
|
|
|
|
##
|
|
|
|
# @CxlCorErrorType:
|
|
|
|
#
|
|
|
|
# Type of CXL correctable error to inject
|
|
|
|
#
|
|
|
|
# @cache-data-ecc: Data ECC error on CXL.cache
|
2023-04-28 12:54:29 +02:00
|
|
|
#
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
# @mem-data-ecc: Data ECC error on CXL.mem
|
2023-04-28 12:54:29 +02:00
|
|
|
#
|
|
|
|
# @crc-threshold: Component specific and applicable to 68 byte Flit
|
|
|
|
# mode only.
|
|
|
|
#
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
# @cache-poison-received: Received poison from a peer on CXL.cache.
|
2023-04-28 12:54:29 +02:00
|
|
|
#
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
# @mem-poison-received: Received poison from a peer on CXL.mem
|
2023-04-28 12:54:29 +02:00
|
|
|
#
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
# @physical: Received error indication from the physical layer.
|
|
|
|
#
|
|
|
|
# Since: 8.0
|
|
|
|
##
|
|
|
|
{ 'enum': 'CxlCorErrorType',
|
|
|
|
'data': ['cache-data-ecc',
|
|
|
|
'mem-data-ecc',
|
|
|
|
'crc-threshold',
|
|
|
|
'retry-threshold',
|
|
|
|
'cache-poison-received',
|
|
|
|
'mem-poison-received',
|
|
|
|
'physical']
|
|
|
|
}
|
|
|
|
|
|
|
|
##
|
|
|
|
# @cxl-inject-correctable-error:
|
|
|
|
#
|
2023-04-28 12:54:29 +02:00
|
|
|
# Command to inject a single correctable error. Multiple error
|
|
|
|
# injection of this error type is not interesting as there is no
|
|
|
|
# associated header log. These errors are reported via AER as a
|
|
|
|
# correctable internal error, with additional detail available from
|
|
|
|
# the CXL device.
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
#
|
|
|
|
# @path: CXL Type 3 device canonical QOM path
|
2023-04-28 12:54:29 +02:00
|
|
|
#
|
hw/mem/cxl_type3: Add CXL RAS Error Injection Support.
CXL uses PCI AER Internal errors to signal to the host that an error has
occurred. The host can then read more detailed status from the CXL RAS
capability.
For uncorrectable errors: support multiple injection in one operation
as this is needed to reliably test multiple header logging support in an
OS. The equivalent feature doesn't exist for correctable errors, so only
one error need be injected at a time.
Note:
- Header content needs to be manually specified in a fashion that
matches the specification for what can be in the header for each
error type.
Injection via QMP:
{ "execute": "qmp_capabilities" }
...
{ "execute": "cxl-inject-uncorrectable-errors",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"errors": [
{
"type": "cache-address-parity",
"header": [ 3, 4]
},
{
"type": "cache-data-parity",
"header": [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31]
},
{
"type": "internal",
"header": [ 1, 2, 4]
}
]
}}
...
{ "execute": "cxl-inject-correctable-error",
"arguments": {
"path": "/machine/peripheral/cxl-pmem0",
"type": "physical"
} }
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20230302133709.30373-9-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2023-03-02 14:37:09 +01:00
|
|
|
# @type: Type of error.
|
|
|
|
#
|
|
|
|
# Since: 8.0
|
|
|
|
##
|
2023-04-28 12:54:29 +02:00
|
|
|
{'command': 'cxl-inject-correctable-error',
|
|
|
|
'data': {'path': 'str', 'type': 'CxlCorErrorType'}}
|