2022-04-29 17:40:29 +03:00
|
|
|
/*
|
|
|
|
* QEMU CXL Devices
|
|
|
|
*
|
|
|
|
* Copyright (c) 2020 Intel
|
|
|
|
*
|
|
|
|
* This work is licensed under the terms of the GNU GPL, version 2. See the
|
|
|
|
* COPYING file in the top-level directory.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef CXL_DEVICE_H
|
|
|
|
#define CXL_DEVICE_H
|
|
|
|
|
2022-12-22 13:03:26 +03:00
|
|
|
#include "hw/cxl/cxl_component.h"
|
2022-12-22 13:03:28 +03:00
|
|
|
#include "hw/pci/pci_device.h"
|
2022-04-29 17:40:29 +03:00
|
|
|
#include "hw/register.h"
|
2023-05-30 16:35:57 +03:00
|
|
|
#include "hw/cxl/cxl_events.h"
|
2022-04-29 17:40:29 +03:00
|
|
|
|
|
|
|
/*
|
|
|
|
* The following is how a CXL device's Memory Device registers are laid out.
|
|
|
|
* The only requirement from the spec is that the capabilities array and the
|
|
|
|
* capability headers start at offset 0 and are contiguously packed. The headers
|
|
|
|
* themselves provide offsets to the register fields. For this emulation, the
|
|
|
|
* actual registers * will start at offset 0x80 (m == 0x80). No secondary
|
|
|
|
* mailbox is implemented which means that the offset of the start of the
|
|
|
|
* mailbox payload (n) is given by
|
|
|
|
* n = m + sizeof(mailbox registers) + sizeof(device registers).
|
|
|
|
*
|
|
|
|
* +---------------------------------+
|
|
|
|
* | |
|
|
|
|
* | Memory Device Registers |
|
|
|
|
* | |
|
|
|
|
* n + PAYLOAD_SIZE_MAX -----------------------------------
|
|
|
|
* ^ | |
|
|
|
|
* | | |
|
|
|
|
* | | |
|
|
|
|
* | | |
|
|
|
|
* | | |
|
|
|
|
* | | Mailbox Payload |
|
|
|
|
* | | |
|
|
|
|
* | | |
|
|
|
|
* | | |
|
|
|
|
* n -----------------------------------
|
|
|
|
* ^ | Mailbox Registers |
|
|
|
|
* | | |
|
|
|
|
* | -----------------------------------
|
|
|
|
* | | |
|
|
|
|
* | | Device Registers |
|
|
|
|
* | | |
|
|
|
|
* m ---------------------------------->
|
|
|
|
* ^ | Memory Device Capability Header|
|
|
|
|
* | -----------------------------------
|
|
|
|
* | | Mailbox Capability Header |
|
|
|
|
* | -----------------------------------
|
|
|
|
* | | Device Capability Header |
|
|
|
|
* | -----------------------------------
|
|
|
|
* | | Device Cap Array Register |
|
|
|
|
* 0 +---------------------------------+
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
2024-01-26 15:16:36 +03:00
|
|
|
/* CXL r3.1 Figure 8-12: CXL Device Registers */
|
|
|
|
#define CXL_DEVICE_CAP_HDR1_OFFSET 0x10
|
|
|
|
/* CXL r3.1 Section 8.2.8.2: CXL Device Capability Header Register */
|
|
|
|
#define CXL_DEVICE_CAP_REG_SIZE 0x10
|
|
|
|
|
|
|
|
/*
|
|
|
|
* CXL r3.1 Section 8.2.8.2.1: CXL Device Capabilities +
|
|
|
|
* CXL r3.1 Section 8.2.8.5: Memory Device Capabilities
|
|
|
|
*/
|
|
|
|
#define CXL_DEVICE_CAPS_MAX 4
|
2022-04-29 17:40:30 +03:00
|
|
|
#define CXL_CAPS_SIZE \
|
|
|
|
(CXL_DEVICE_CAP_REG_SIZE * (CXL_DEVICE_CAPS_MAX + 1)) /* +1 for header */
|
2022-04-29 17:40:29 +03:00
|
|
|
|
|
|
|
#define CXL_DEVICE_STATUS_REGISTERS_OFFSET 0x80 /* Read comment above */
|
2024-01-26 15:16:36 +03:00
|
|
|
/*
|
|
|
|
* CXL r3.1 Section 8.2.8.3: Device Status Registers
|
|
|
|
* As it is the only Device Status Register in CXL r3.1
|
|
|
|
*/
|
|
|
|
#define CXL_DEVICE_STATUS_REGISTERS_LENGTH 0x8
|
2022-04-29 17:40:29 +03:00
|
|
|
|
|
|
|
#define CXL_MAILBOX_REGISTERS_OFFSET \
|
|
|
|
(CXL_DEVICE_STATUS_REGISTERS_OFFSET + CXL_DEVICE_STATUS_REGISTERS_LENGTH)
|
2024-01-26 15:16:36 +03:00
|
|
|
/* CXL r3.1 Figure 8-13: Mailbox Registers */
|
|
|
|
#define CXL_MAILBOX_REGISTERS_SIZE 0x20
|
2022-04-29 17:40:29 +03:00
|
|
|
#define CXL_MAILBOX_PAYLOAD_SHIFT 11
|
|
|
|
#define CXL_MAILBOX_MAX_PAYLOAD_SIZE (1 << CXL_MAILBOX_PAYLOAD_SHIFT)
|
|
|
|
#define CXL_MAILBOX_REGISTERS_LENGTH \
|
|
|
|
(CXL_MAILBOX_REGISTERS_SIZE + CXL_MAILBOX_MAX_PAYLOAD_SIZE)
|
|
|
|
|
2022-04-29 17:40:32 +03:00
|
|
|
#define CXL_MEMORY_DEVICE_REGISTERS_OFFSET \
|
|
|
|
(CXL_MAILBOX_REGISTERS_OFFSET + CXL_MAILBOX_REGISTERS_LENGTH)
|
|
|
|
#define CXL_MEMORY_DEVICE_REGISTERS_LENGTH 0x8
|
|
|
|
|
|
|
|
#define CXL_MMIO_SIZE \
|
|
|
|
(CXL_DEVICE_CAP_REG_SIZE + CXL_DEVICE_STATUS_REGISTERS_LENGTH + \
|
|
|
|
CXL_MAILBOX_REGISTERS_LENGTH + CXL_MEMORY_DEVICE_REGISTERS_LENGTH)
|
2022-04-29 17:40:30 +03:00
|
|
|
|
2024-01-26 15:16:36 +03:00
|
|
|
/* CXL r3.1 Table 8-34: Command Return Codes */
|
2023-05-30 16:35:58 +03:00
|
|
|
typedef enum {
|
|
|
|
CXL_MBOX_SUCCESS = 0x0,
|
|
|
|
CXL_MBOX_BG_STARTED = 0x1,
|
|
|
|
CXL_MBOX_INVALID_INPUT = 0x2,
|
|
|
|
CXL_MBOX_UNSUPPORTED = 0x3,
|
|
|
|
CXL_MBOX_INTERNAL_ERROR = 0x4,
|
|
|
|
CXL_MBOX_RETRY_REQUIRED = 0x5,
|
|
|
|
CXL_MBOX_BUSY = 0x6,
|
|
|
|
CXL_MBOX_MEDIA_DISABLED = 0x7,
|
|
|
|
CXL_MBOX_FW_XFER_IN_PROGRESS = 0x8,
|
|
|
|
CXL_MBOX_FW_XFER_OUT_OF_ORDER = 0x9,
|
|
|
|
CXL_MBOX_FW_AUTH_FAILED = 0xa,
|
|
|
|
CXL_MBOX_FW_INVALID_SLOT = 0xb,
|
|
|
|
CXL_MBOX_FW_ROLLEDBACK = 0xc,
|
|
|
|
CXL_MBOX_FW_REST_REQD = 0xd,
|
|
|
|
CXL_MBOX_INVALID_HANDLE = 0xe,
|
|
|
|
CXL_MBOX_INVALID_PA = 0xf,
|
|
|
|
CXL_MBOX_INJECT_POISON_LIMIT = 0x10,
|
|
|
|
CXL_MBOX_PERMANENT_MEDIA_FAILURE = 0x11,
|
|
|
|
CXL_MBOX_ABORTED = 0x12,
|
|
|
|
CXL_MBOX_INVALID_SECURITY_STATE = 0x13,
|
|
|
|
CXL_MBOX_INCORRECT_PASSPHRASE = 0x14,
|
|
|
|
CXL_MBOX_UNSUPPORTED_MAILBOX = 0x15,
|
|
|
|
CXL_MBOX_INVALID_PAYLOAD_LENGTH = 0x16,
|
2024-01-26 15:16:36 +03:00
|
|
|
CXL_MBOX_INVALID_LOG = 0x17,
|
|
|
|
CXL_MBOX_INTERRUPTED = 0x18,
|
|
|
|
CXL_MBOX_UNSUPPORTED_FEATURE_VERSION = 0x19,
|
|
|
|
CXL_MBOX_UNSUPPORTED_FEATURE_SELECTION_VALUE = 0x1a,
|
|
|
|
CXL_MBOX_FEATURE_TRANSFER_IN_PROGRESS = 0x1b,
|
|
|
|
CXL_MBOX_FEATURE_TRANSFER_OUT_OF_ORDER = 0x1c,
|
|
|
|
CXL_MBOX_RESOURCES_EXHAUSTED = 0x1d,
|
|
|
|
CXL_MBOX_INVALID_EXTENT_LIST = 0x1e,
|
|
|
|
CXL_MBOX_TRANSFER_OUT_OF_ORDER = 0x1f,
|
|
|
|
CXL_MBOX_REQUEST_ABORT_NOTSUP = 0x20,
|
|
|
|
CXL_MBOX_MAX = 0x20
|
2023-05-30 16:35:58 +03:00
|
|
|
} CXLRetCode;
|
|
|
|
|
2023-10-23 19:07:52 +03:00
|
|
|
typedef struct CXLCCI CXLCCI;
|
2023-10-23 19:07:50 +03:00
|
|
|
typedef struct cxl_device_state CXLDeviceState;
|
|
|
|
struct cxl_cmd;
|
|
|
|
typedef CXLRetCode (*opcode_handler)(const struct cxl_cmd *cmd,
|
2023-10-23 19:07:51 +03:00
|
|
|
uint8_t *payload_in, size_t len_in,
|
|
|
|
uint8_t *payload_out, size_t *len_out,
|
2023-10-23 19:07:52 +03:00
|
|
|
CXLCCI *cci);
|
2023-10-23 19:07:50 +03:00
|
|
|
struct cxl_cmd {
|
|
|
|
const char *name;
|
|
|
|
opcode_handler handler;
|
|
|
|
ssize_t in;
|
|
|
|
uint16_t effect; /* Reported in CEL */
|
|
|
|
};
|
|
|
|
|
2023-05-30 16:35:59 +03:00
|
|
|
typedef struct CXLEvent {
|
|
|
|
CXLEventRecordRaw data;
|
|
|
|
QSIMPLEQ_ENTRY(CXLEvent) node;
|
|
|
|
} CXLEvent;
|
|
|
|
|
|
|
|
typedef struct CXLEventLog {
|
|
|
|
uint16_t next_handle;
|
|
|
|
uint16_t overflow_err_count;
|
|
|
|
uint64_t first_overflow_timestamp;
|
|
|
|
uint64_t last_overflow_timestamp;
|
2023-05-30 16:36:00 +03:00
|
|
|
bool irq_enabled;
|
|
|
|
int irq_vec;
|
2023-05-30 16:35:59 +03:00
|
|
|
QemuMutex lock;
|
|
|
|
QSIMPLEQ_HEAD(, CXLEvent) events;
|
|
|
|
} CXLEventLog;
|
|
|
|
|
2023-10-23 19:07:52 +03:00
|
|
|
typedef struct CXLCCI {
|
2024-05-23 20:44:41 +03:00
|
|
|
struct cxl_cmd cxl_cmd_set[256][256];
|
2023-10-23 19:07:52 +03:00
|
|
|
struct cel_log {
|
|
|
|
uint16_t opcode;
|
|
|
|
uint16_t effect;
|
|
|
|
} cel_log[1 << 16];
|
|
|
|
size_t cel_size;
|
|
|
|
|
2023-10-23 19:08:00 +03:00
|
|
|
/* background command handling (times in ms) */
|
|
|
|
struct {
|
|
|
|
uint16_t opcode;
|
|
|
|
uint16_t complete_pct;
|
|
|
|
uint16_t ret_code; /* Current value of retcode */
|
|
|
|
uint64_t starttime;
|
|
|
|
/* set by each bg cmd, cleared by the bg_timer when complete */
|
|
|
|
uint64_t runtime;
|
|
|
|
QEMUTimer *timer;
|
|
|
|
} bg;
|
2023-10-23 19:07:52 +03:00
|
|
|
size_t payload_max;
|
|
|
|
/* Pointer to device hosting the CCI */
|
|
|
|
DeviceState *d;
|
|
|
|
/* Pointer to the device hosting the protocol conversion */
|
|
|
|
DeviceState *intf;
|
|
|
|
} CXLCCI;
|
|
|
|
|
2022-04-29 17:40:29 +03:00
|
|
|
typedef struct cxl_device_state {
|
|
|
|
MemoryRegion device_registers;
|
|
|
|
|
2024-01-26 15:16:36 +03:00
|
|
|
/* CXL r3.1 Section 8.2.8.3: Device Status Registers */
|
2023-05-30 16:35:57 +03:00
|
|
|
struct {
|
|
|
|
MemoryRegion device;
|
|
|
|
union {
|
|
|
|
uint8_t dev_reg_state[CXL_DEVICE_STATUS_REGISTERS_LENGTH];
|
|
|
|
uint16_t dev_reg_state16[CXL_DEVICE_STATUS_REGISTERS_LENGTH / 2];
|
|
|
|
uint32_t dev_reg_state32[CXL_DEVICE_STATUS_REGISTERS_LENGTH / 4];
|
|
|
|
uint64_t dev_reg_state64[CXL_DEVICE_STATUS_REGISTERS_LENGTH / 8];
|
|
|
|
};
|
|
|
|
uint64_t event_status;
|
|
|
|
};
|
2022-04-29 17:40:32 +03:00
|
|
|
MemoryRegion memory_device;
|
2022-04-29 17:40:30 +03:00
|
|
|
struct {
|
|
|
|
MemoryRegion caps;
|
|
|
|
union {
|
|
|
|
uint32_t caps_reg_state32[CXL_CAPS_SIZE / 4];
|
|
|
|
uint64_t caps_reg_state64[CXL_CAPS_SIZE / 8];
|
|
|
|
};
|
|
|
|
};
|
2022-04-29 17:40:29 +03:00
|
|
|
|
2024-01-26 15:16:35 +03:00
|
|
|
/* CXL r3.1 Section 8.2.8.4: Mailbox Registers */
|
2022-04-29 17:40:31 +03:00
|
|
|
struct {
|
|
|
|
MemoryRegion mailbox;
|
|
|
|
uint16_t payload_size;
|
2023-10-23 19:08:01 +03:00
|
|
|
uint8_t mbox_msi_n;
|
2022-04-29 17:40:31 +03:00
|
|
|
union {
|
|
|
|
uint8_t mbox_reg_state[CXL_MAILBOX_REGISTERS_LENGTH];
|
|
|
|
uint16_t mbox_reg_state16[CXL_MAILBOX_REGISTERS_LENGTH / 2];
|
|
|
|
uint32_t mbox_reg_state32[CXL_MAILBOX_REGISTERS_LENGTH / 4];
|
|
|
|
uint64_t mbox_reg_state64[CXL_MAILBOX_REGISTERS_LENGTH / 8];
|
|
|
|
};
|
|
|
|
};
|
2022-04-29 17:40:29 +03:00
|
|
|
|
2024-01-26 15:01:26 +03:00
|
|
|
/* Stash the memory device status value */
|
|
|
|
uint64_t memdev_status;
|
|
|
|
|
2022-04-29 17:40:34 +03:00
|
|
|
struct {
|
|
|
|
bool set;
|
|
|
|
uint64_t last_set;
|
|
|
|
uint64_t host_set;
|
|
|
|
} timestamp;
|
|
|
|
|
2023-04-21 19:08:27 +03:00
|
|
|
/* memory region size, HDM */
|
|
|
|
uint64_t mem_size;
|
2022-04-29 17:40:29 +03:00
|
|
|
uint64_t pmem_size;
|
2023-04-21 19:08:27 +03:00
|
|
|
uint64_t vmem_size;
|
2023-05-30 16:35:59 +03:00
|
|
|
|
2023-10-23 19:07:50 +03:00
|
|
|
const struct cxl_cmd (*cxl_cmd_set)[256];
|
2023-05-30 16:35:59 +03:00
|
|
|
CXLEventLog event_logs[CXL_EVENT_TYPE_MAX];
|
2022-04-29 17:40:29 +03:00
|
|
|
} CXLDeviceState;
|
|
|
|
|
|
|
|
/* Initialize the register block for a device */
|
2023-10-23 19:07:52 +03:00
|
|
|
void cxl_device_register_block_init(Object *obj, CXLDeviceState *dev,
|
|
|
|
CXLCCI *cci);
|
2022-04-29 17:40:29 +03:00
|
|
|
|
2023-10-23 19:07:52 +03:00
|
|
|
typedef struct CXLType3Dev CXLType3Dev;
|
2023-10-23 19:07:55 +03:00
|
|
|
typedef struct CSWMBCCIDev CSWMBCCIDev;
|
2022-04-29 17:40:29 +03:00
|
|
|
/* Set up default values for the register block */
|
2023-10-23 19:07:52 +03:00
|
|
|
void cxl_device_register_init_t3(CXLType3Dev *ct3d);
|
2023-10-23 19:07:55 +03:00
|
|
|
void cxl_device_register_init_swcci(CSWMBCCIDev *sw);
|
2022-04-29 17:40:29 +03:00
|
|
|
|
|
|
|
/*
|
2024-01-26 15:16:36 +03:00
|
|
|
* CXL r3.1 Section 8.2.8.1: CXL Device Capabilities Array Register
|
2022-04-29 17:40:29 +03:00
|
|
|
* Documented as a 128 bit register, but 64 bit accesses and the second
|
|
|
|
* 64 bits are currently reserved.
|
|
|
|
*/
|
2023-10-23 17:02:09 +03:00
|
|
|
REG64(CXL_DEV_CAP_ARRAY, 0)
|
2022-04-29 17:40:29 +03:00
|
|
|
FIELD(CXL_DEV_CAP_ARRAY, CAP_ID, 0, 16)
|
|
|
|
FIELD(CXL_DEV_CAP_ARRAY, CAP_VERSION, 16, 8)
|
|
|
|
FIELD(CXL_DEV_CAP_ARRAY, CAP_COUNT, 32, 16)
|
|
|
|
|
2023-05-30 16:35:57 +03:00
|
|
|
void cxl_event_set_status(CXLDeviceState *cxl_dstate, CXLEventLogType log_type,
|
|
|
|
bool available);
|
|
|
|
|
2022-04-29 17:40:29 +03:00
|
|
|
/*
|
|
|
|
* Helper macro to initialize capability headers for CXL devices.
|
|
|
|
*
|
2024-02-20 11:52:18 +03:00
|
|
|
* In CXL r3.1 Section 8.2.8.2: CXL Device Capability Header Register, this is
|
2024-01-26 15:16:36 +03:00
|
|
|
* listed as a 128b register, but in CXL r3.1 Section 8.2.8: CXL Device Register
|
|
|
|
* Interface, it says:
|
2022-04-29 17:40:29 +03:00
|
|
|
* > No registers defined in Section 8.2.8 are larger than 64-bits wide so that
|
|
|
|
* > is the maximum access size allowed for these registers. If this rule is not
|
2024-01-26 15:16:36 +03:00
|
|
|
* > followed, the behavior is undefined.
|
2022-04-29 17:40:29 +03:00
|
|
|
*
|
2024-01-26 15:16:36 +03:00
|
|
|
* > To illustrate how the fields fit together, the layouts ... are shown as
|
2024-02-20 11:52:18 +03:00
|
|
|
* > wider than a 64 bit register. Implementations are expected to use any size
|
2024-01-26 15:16:36 +03:00
|
|
|
* > accesses for this information up to 64 bits without lost of functionality
|
2022-04-29 17:40:29 +03:00
|
|
|
*
|
2024-01-26 15:16:36 +03:00
|
|
|
* Here we've chosen to make it 4 dwords.
|
2022-04-29 17:40:29 +03:00
|
|
|
*/
|
|
|
|
#define CXL_DEVICE_CAPABILITY_HEADER_REGISTER(n, offset) \
|
|
|
|
REG32(CXL_DEV_##n##_CAP_HDR0, offset) \
|
|
|
|
FIELD(CXL_DEV_##n##_CAP_HDR0, CAP_ID, 0, 16) \
|
|
|
|
FIELD(CXL_DEV_##n##_CAP_HDR0, CAP_VERSION, 16, 8) \
|
|
|
|
REG32(CXL_DEV_##n##_CAP_HDR1, offset + 4) \
|
|
|
|
FIELD(CXL_DEV_##n##_CAP_HDR1, CAP_OFFSET, 0, 32) \
|
|
|
|
REG32(CXL_DEV_##n##_CAP_HDR2, offset + 8) \
|
|
|
|
FIELD(CXL_DEV_##n##_CAP_HDR2, CAP_LENGTH, 0, 32)
|
|
|
|
|
|
|
|
CXL_DEVICE_CAPABILITY_HEADER_REGISTER(DEVICE_STATUS, CXL_DEVICE_CAP_HDR1_OFFSET)
|
|
|
|
CXL_DEVICE_CAPABILITY_HEADER_REGISTER(MAILBOX, CXL_DEVICE_CAP_HDR1_OFFSET + \
|
|
|
|
CXL_DEVICE_CAP_REG_SIZE)
|
2022-04-29 17:40:32 +03:00
|
|
|
CXL_DEVICE_CAPABILITY_HEADER_REGISTER(MEMORY_DEVICE,
|
|
|
|
CXL_DEVICE_CAP_HDR1_OFFSET +
|
|
|
|
CXL_DEVICE_CAP_REG_SIZE * 2)
|
2022-04-29 17:40:29 +03:00
|
|
|
|
2023-10-23 19:07:52 +03:00
|
|
|
void cxl_initialize_mailbox_t3(CXLCCI *cci, DeviceState *d, size_t payload_max);
|
2023-10-23 19:07:55 +03:00
|
|
|
void cxl_initialize_mailbox_swcci(CXLCCI *cci, DeviceState *intf,
|
|
|
|
DeviceState *d, size_t payload_max);
|
2023-10-23 19:07:52 +03:00
|
|
|
void cxl_init_cci(CXLCCI *cci, size_t payload_max);
|
2024-05-23 20:44:42 +03:00
|
|
|
void cxl_add_cci_commands(CXLCCI *cci, const struct cxl_cmd (*cxl_cmd_set)[256],
|
|
|
|
size_t payload_max);
|
2023-10-23 19:07:53 +03:00
|
|
|
int cxl_process_cci_message(CXLCCI *cci, uint8_t set, uint8_t cmd,
|
|
|
|
size_t len_in, uint8_t *pl_in,
|
|
|
|
size_t *len_out, uint8_t *pl_out,
|
|
|
|
bool *bg_started);
|
2023-10-23 19:08:06 +03:00
|
|
|
void cxl_initialize_t3_fm_owned_ld_mctpcci(CXLCCI *cci, DeviceState *d,
|
|
|
|
DeviceState *intf,
|
|
|
|
size_t payload_max);
|
|
|
|
|
|
|
|
void cxl_initialize_t3_ld_cci(CXLCCI *cci, DeviceState *d,
|
|
|
|
DeviceState *intf, size_t payload_max);
|
2022-04-29 17:40:31 +03:00
|
|
|
|
2023-05-30 16:35:57 +03:00
|
|
|
#define cxl_device_cap_init(dstate, reg, cap_id, ver) \
|
2022-04-29 17:40:30 +03:00
|
|
|
do { \
|
|
|
|
uint32_t *cap_hdrs = dstate->caps_reg_state32; \
|
|
|
|
int which = R_CXL_DEV_##reg##_CAP_HDR0; \
|
|
|
|
cap_hdrs[which] = \
|
|
|
|
FIELD_DP32(cap_hdrs[which], CXL_DEV_##reg##_CAP_HDR0, \
|
|
|
|
CAP_ID, cap_id); \
|
|
|
|
cap_hdrs[which] = FIELD_DP32( \
|
2023-05-30 16:35:57 +03:00
|
|
|
cap_hdrs[which], CXL_DEV_##reg##_CAP_HDR0, CAP_VERSION, ver); \
|
2022-04-29 17:40:30 +03:00
|
|
|
cap_hdrs[which + 1] = \
|
|
|
|
FIELD_DP32(cap_hdrs[which + 1], CXL_DEV_##reg##_CAP_HDR1, \
|
|
|
|
CAP_OFFSET, CXL_##reg##_REGISTERS_OFFSET); \
|
|
|
|
cap_hdrs[which + 2] = \
|
|
|
|
FIELD_DP32(cap_hdrs[which + 2], CXL_DEV_##reg##_CAP_HDR2, \
|
|
|
|
CAP_LENGTH, CXL_##reg##_REGISTERS_LENGTH); \
|
|
|
|
} while (0)
|
|
|
|
|
2024-01-26 15:16:36 +03:00
|
|
|
/* CXL r3.2 Section 8.2.8.3.1: Event Status Register */
|
|
|
|
#define CXL_DEVICE_STATUS_VERSION 2
|
2023-05-30 16:35:57 +03:00
|
|
|
REG64(CXL_DEV_EVENT_STATUS, 0)
|
|
|
|
FIELD(CXL_DEV_EVENT_STATUS, EVENT_STATUS, 0, 32)
|
|
|
|
|
2024-01-26 15:16:35 +03:00
|
|
|
#define CXL_DEV_MAILBOX_VERSION 1
|
|
|
|
/* CXL r3.1 Section 8.2.8.4.3: Mailbox Capabilities Register */
|
2022-04-29 17:40:29 +03:00
|
|
|
REG32(CXL_DEV_MAILBOX_CAP, 0)
|
|
|
|
FIELD(CXL_DEV_MAILBOX_CAP, PAYLOAD_SIZE, 0, 5)
|
|
|
|
FIELD(CXL_DEV_MAILBOX_CAP, INT_CAP, 5, 1)
|
|
|
|
FIELD(CXL_DEV_MAILBOX_CAP, BG_INT_CAP, 6, 1)
|
|
|
|
FIELD(CXL_DEV_MAILBOX_CAP, MSI_N, 7, 4)
|
2024-01-26 15:16:35 +03:00
|
|
|
FIELD(CXL_DEV_MAILBOX_CAP, MBOX_READY_TIME, 11, 8)
|
|
|
|
FIELD(CXL_DEV_MAILBOX_CAP, TYPE, 19, 4)
|
2022-04-29 17:40:29 +03:00
|
|
|
|
2024-01-26 15:16:35 +03:00
|
|
|
/* CXL r3.1 Section 8.2.8.4.4: Mailbox Control Register */
|
2022-04-29 17:40:29 +03:00
|
|
|
REG32(CXL_DEV_MAILBOX_CTRL, 4)
|
|
|
|
FIELD(CXL_DEV_MAILBOX_CTRL, DOORBELL, 0, 1)
|
|
|
|
FIELD(CXL_DEV_MAILBOX_CTRL, INT_EN, 1, 1)
|
|
|
|
FIELD(CXL_DEV_MAILBOX_CTRL, BG_INT_EN, 2, 1)
|
|
|
|
|
2024-01-26 15:16:35 +03:00
|
|
|
/* CXL r3.1 Section 8.2.8.4.5: Command Register */
|
2022-04-29 17:40:29 +03:00
|
|
|
REG64(CXL_DEV_MAILBOX_CMD, 8)
|
|
|
|
FIELD(CXL_DEV_MAILBOX_CMD, COMMAND, 0, 8)
|
|
|
|
FIELD(CXL_DEV_MAILBOX_CMD, COMMAND_SET, 8, 8)
|
|
|
|
FIELD(CXL_DEV_MAILBOX_CMD, LENGTH, 16, 20)
|
|
|
|
|
2024-01-26 15:16:35 +03:00
|
|
|
/* CXL r3.1 Section 8.2.8.4.6: Mailbox Status Register */
|
2022-04-29 17:40:29 +03:00
|
|
|
REG64(CXL_DEV_MAILBOX_STS, 0x10)
|
|
|
|
FIELD(CXL_DEV_MAILBOX_STS, BG_OP, 0, 1)
|
|
|
|
FIELD(CXL_DEV_MAILBOX_STS, ERRNO, 32, 16)
|
|
|
|
FIELD(CXL_DEV_MAILBOX_STS, VENDOR_ERRNO, 48, 16)
|
|
|
|
|
2024-01-26 15:16:35 +03:00
|
|
|
/* CXL r3.1 Section 8.2.8.4.7: Background Command Status Register */
|
2022-04-29 17:40:29 +03:00
|
|
|
REG64(CXL_DEV_BG_CMD_STS, 0x18)
|
|
|
|
FIELD(CXL_DEV_BG_CMD_STS, OP, 0, 16)
|
|
|
|
FIELD(CXL_DEV_BG_CMD_STS, PERCENTAGE_COMP, 16, 7)
|
|
|
|
FIELD(CXL_DEV_BG_CMD_STS, RET_CODE, 32, 16)
|
|
|
|
FIELD(CXL_DEV_BG_CMD_STS, VENDOR_RET_CODE, 48, 16)
|
|
|
|
|
2024-01-26 15:16:35 +03:00
|
|
|
/* CXL r3.1 Section 8.2.8.4.8: Command Payload Registers */
|
2022-04-29 17:40:29 +03:00
|
|
|
REG32(CXL_DEV_CMD_PAYLOAD, 0x20)
|
|
|
|
|
2024-01-26 15:16:36 +03:00
|
|
|
/* CXL r3.1 Section 8.2.8.4.1: Memory Device Status Registers */
|
|
|
|
#define CXL_MEM_DEV_STATUS_VERSION 1
|
2022-04-29 17:40:32 +03:00
|
|
|
REG64(CXL_MEM_DEV_STS, 0)
|
|
|
|
FIELD(CXL_MEM_DEV_STS, FATAL, 0, 1)
|
|
|
|
FIELD(CXL_MEM_DEV_STS, FW_HALT, 1, 1)
|
|
|
|
FIELD(CXL_MEM_DEV_STS, MEDIA_STATUS, 2, 2)
|
|
|
|
FIELD(CXL_MEM_DEV_STS, MBOX_READY, 4, 1)
|
|
|
|
FIELD(CXL_MEM_DEV_STS, RESET_NEEDED, 5, 3)
|
|
|
|
|
2023-10-23 19:08:02 +03:00
|
|
|
static inline void __toggle_media(CXLDeviceState *cxl_dstate, int val)
|
|
|
|
{
|
|
|
|
uint64_t dev_status_reg;
|
|
|
|
|
2024-01-26 15:01:26 +03:00
|
|
|
dev_status_reg = cxl_dstate->memdev_status;
|
|
|
|
dev_status_reg = FIELD_DP64(dev_status_reg, CXL_MEM_DEV_STS, MEDIA_STATUS,
|
|
|
|
val);
|
|
|
|
cxl_dstate->memdev_status = dev_status_reg;
|
2023-10-23 19:08:02 +03:00
|
|
|
}
|
|
|
|
#define cxl_dev_disable_media(cxlds) \
|
|
|
|
do { __toggle_media((cxlds), 0x3); } while (0)
|
|
|
|
#define cxl_dev_enable_media(cxlds) \
|
|
|
|
do { __toggle_media((cxlds), 0x1); } while (0)
|
|
|
|
|
|
|
|
static inline bool sanitize_running(CXLCCI *cci)
|
|
|
|
{
|
|
|
|
return !!cci->bg.runtime && cci->bg.opcode == 0x4400;
|
|
|
|
}
|
|
|
|
|
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 16:37:09 +03:00
|
|
|
typedef struct CXLError {
|
|
|
|
QTAILQ_ENTRY(CXLError) node;
|
|
|
|
int type; /* Error code as per FE definition */
|
2023-09-04 16:28:05 +03:00
|
|
|
uint32_t header[CXL_RAS_ERR_HEADER_NUM];
|
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 16:37:09 +03:00
|
|
|
} CXLError;
|
|
|
|
|
|
|
|
typedef QTAILQ_HEAD(, CXLError) CXLErrorList;
|
|
|
|
|
2023-05-26 20:00:08 +03:00
|
|
|
typedef struct CXLPoison {
|
|
|
|
uint64_t start, length;
|
|
|
|
uint8_t type;
|
|
|
|
#define CXL_POISON_TYPE_EXTERNAL 0x1
|
|
|
|
#define CXL_POISON_TYPE_INTERNAL 0x2
|
|
|
|
#define CXL_POISON_TYPE_INJECTED 0x3
|
|
|
|
QLIST_ENTRY(CXLPoison) node;
|
|
|
|
} CXLPoison;
|
|
|
|
|
|
|
|
typedef QLIST_HEAD(, CXLPoison) CXLPoisonList;
|
|
|
|
#define CXL_POISON_LIST_LIMIT 256
|
|
|
|
|
hw/cxl/device: Add a memory device (8.2.8.5)
A CXL memory device (AKA Type 3) is a CXL component that contains some
combination of volatile and persistent memory. It also implements the
previously defined mailbox interface as well as the memory device
firmware interface.
Although the memory device is configured like a normal PCIe device, the
memory traffic is on an entirely separate bus conceptually (using the
same physical wires as PCIe, but different protocol).
Once the CXL topology is fully configure and address decoders committed,
the guest physical address for the memory device is part of a larger
window which is owned by the platform. The creation of these windows
is later in this series.
The following example will create a 256M device in a 512M window:
-object "memory-backend-file,id=cxl-mem1,share,mem-path=cxl-type3,size=512M"
-device "cxl-type3,bus=rp0,memdev=cxl-mem1,id=cxl-pmem0"
Note: Dropped PCDIMM info interfaces for now. They can be added if
appropriate at a later date.
Signed-off-by: Ben Widawsky <ben.widawsky@intel.com>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20220429144110.25167-18-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2022-04-29 17:40:42 +03:00
|
|
|
struct CXLType3Dev {
|
|
|
|
/* Private */
|
|
|
|
PCIDevice parent_obj;
|
|
|
|
|
|
|
|
/* Properties */
|
2023-04-21 19:08:27 +03:00
|
|
|
HostMemoryBackend *hostmem; /* deprecated */
|
|
|
|
HostMemoryBackend *hostvmem;
|
|
|
|
HostMemoryBackend *hostpmem;
|
2022-04-29 17:40:45 +03:00
|
|
|
HostMemoryBackend *lsa;
|
2022-09-23 19:18:35 +03:00
|
|
|
uint64_t sn;
|
hw/cxl/device: Add a memory device (8.2.8.5)
A CXL memory device (AKA Type 3) is a CXL component that contains some
combination of volatile and persistent memory. It also implements the
previously defined mailbox interface as well as the memory device
firmware interface.
Although the memory device is configured like a normal PCIe device, the
memory traffic is on an entirely separate bus conceptually (using the
same physical wires as PCIe, but different protocol).
Once the CXL topology is fully configure and address decoders committed,
the guest physical address for the memory device is part of a larger
window which is owned by the platform. The creation of these windows
is later in this series.
The following example will create a 256M device in a 512M window:
-object "memory-backend-file,id=cxl-mem1,share,mem-path=cxl-type3,size=512M"
-device "cxl-type3,bus=rp0,memdev=cxl-mem1,id=cxl-pmem0"
Note: Dropped PCDIMM info interfaces for now. They can be added if
appropriate at a later date.
Signed-off-by: Ben Widawsky <ben.widawsky@intel.com>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20220429144110.25167-18-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2022-04-29 17:40:42 +03:00
|
|
|
|
|
|
|
/* State */
|
2023-04-21 19:08:27 +03:00
|
|
|
AddressSpace hostvmem_as;
|
|
|
|
AddressSpace hostpmem_as;
|
hw/cxl/device: Add a memory device (8.2.8.5)
A CXL memory device (AKA Type 3) is a CXL component that contains some
combination of volatile and persistent memory. It also implements the
previously defined mailbox interface as well as the memory device
firmware interface.
Although the memory device is configured like a normal PCIe device, the
memory traffic is on an entirely separate bus conceptually (using the
same physical wires as PCIe, but different protocol).
Once the CXL topology is fully configure and address decoders committed,
the guest physical address for the memory device is part of a larger
window which is owned by the platform. The creation of these windows
is later in this series.
The following example will create a 256M device in a 512M window:
-object "memory-backend-file,id=cxl-mem1,share,mem-path=cxl-type3,size=512M"
-device "cxl-type3,bus=rp0,memdev=cxl-mem1,id=cxl-pmem0"
Note: Dropped PCDIMM info interfaces for now. They can be added if
appropriate at a later date.
Signed-off-by: Ben Widawsky <ben.widawsky@intel.com>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20220429144110.25167-18-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2022-04-29 17:40:42 +03:00
|
|
|
CXLComponentState cxl_cstate;
|
|
|
|
CXLDeviceState cxl_dstate;
|
2023-10-23 19:07:52 +03:00
|
|
|
CXLCCI cci; /* Primary PCI mailbox CCI */
|
2023-11-14 19:06:48 +03:00
|
|
|
/* Always initialized as no way to know if a VDM might show up */
|
2023-10-23 19:08:06 +03:00
|
|
|
CXLCCI vdm_fm_owned_ld_mctp_cci;
|
|
|
|
CXLCCI ld0_cci;
|
2022-10-14 18:10:43 +03:00
|
|
|
|
|
|
|
/* DOE */
|
|
|
|
DOECap doe_cdat;
|
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 16:37:09 +03:00
|
|
|
|
|
|
|
/* Error injection */
|
|
|
|
CXLErrorList error_list;
|
2023-05-26 20:00:08 +03:00
|
|
|
|
|
|
|
/* Poison Injection - cache */
|
|
|
|
CXLPoisonList poison_list;
|
|
|
|
unsigned int poison_list_cnt;
|
|
|
|
bool poison_list_overflowed;
|
|
|
|
uint64_t poison_list_overflow_ts;
|
hw/cxl/device: Add a memory device (8.2.8.5)
A CXL memory device (AKA Type 3) is a CXL component that contains some
combination of volatile and persistent memory. It also implements the
previously defined mailbox interface as well as the memory device
firmware interface.
Although the memory device is configured like a normal PCIe device, the
memory traffic is on an entirely separate bus conceptually (using the
same physical wires as PCIe, but different protocol).
Once the CXL topology is fully configure and address decoders committed,
the guest physical address for the memory device is part of a larger
window which is owned by the platform. The creation of these windows
is later in this series.
The following example will create a 256M device in a 512M window:
-object "memory-backend-file,id=cxl-mem1,share,mem-path=cxl-type3,size=512M"
-device "cxl-type3,bus=rp0,memdev=cxl-mem1,id=cxl-pmem0"
Note: Dropped PCDIMM info interfaces for now. They can be added if
appropriate at a later date.
Signed-off-by: Ben Widawsky <ben.widawsky@intel.com>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20220429144110.25167-18-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2022-04-29 17:40:42 +03:00
|
|
|
};
|
|
|
|
|
|
|
|
#define TYPE_CXL_TYPE3 "cxl-type3"
|
2022-04-29 17:40:45 +03:00
|
|
|
OBJECT_DECLARE_TYPE(CXLType3Dev, CXLType3Class, CXL_TYPE3)
|
|
|
|
|
|
|
|
struct CXLType3Class {
|
|
|
|
/* Private */
|
|
|
|
PCIDeviceClass parent_class;
|
|
|
|
|
|
|
|
/* public */
|
|
|
|
uint64_t (*get_lsa_size)(CXLType3Dev *ct3d);
|
2022-04-29 17:40:46 +03:00
|
|
|
|
|
|
|
uint64_t (*get_lsa)(CXLType3Dev *ct3d, void *buf, uint64_t size,
|
|
|
|
uint64_t offset);
|
|
|
|
void (*set_lsa)(CXLType3Dev *ct3d, const void *buf, uint64_t size,
|
|
|
|
uint64_t offset);
|
2023-10-23 17:02:09 +03:00
|
|
|
bool (*set_cacheline)(CXLType3Dev *ct3d, uint64_t dpa_offset,
|
|
|
|
uint8_t *data);
|
2022-04-29 17:40:45 +03:00
|
|
|
};
|
hw/cxl/device: Add a memory device (8.2.8.5)
A CXL memory device (AKA Type 3) is a CXL component that contains some
combination of volatile and persistent memory. It also implements the
previously defined mailbox interface as well as the memory device
firmware interface.
Although the memory device is configured like a normal PCIe device, the
memory traffic is on an entirely separate bus conceptually (using the
same physical wires as PCIe, but different protocol).
Once the CXL topology is fully configure and address decoders committed,
the guest physical address for the memory device is part of a larger
window which is owned by the platform. The creation of these windows
is later in this series.
The following example will create a 256M device in a 512M window:
-object "memory-backend-file,id=cxl-mem1,share,mem-path=cxl-type3,size=512M"
-device "cxl-type3,bus=rp0,memdev=cxl-mem1,id=cxl-pmem0"
Note: Dropped PCDIMM info interfaces for now. They can be added if
appropriate at a later date.
Signed-off-by: Ben Widawsky <ben.widawsky@intel.com>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Message-Id: <20220429144110.25167-18-Jonathan.Cameron@huawei.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2022-04-29 17:40:42 +03:00
|
|
|
|
2023-10-23 19:07:55 +03:00
|
|
|
struct CSWMBCCIDev {
|
|
|
|
PCIDevice parent_obj;
|
|
|
|
PCIDevice *target;
|
|
|
|
CXLComponentState cxl_cstate;
|
|
|
|
CXLDeviceState cxl_dstate;
|
|
|
|
CXLCCI *cci;
|
|
|
|
};
|
|
|
|
|
|
|
|
#define TYPE_CXL_SWITCH_MAILBOX_CCI "cxl-switch-mailbox-cci"
|
|
|
|
OBJECT_DECLARE_TYPE(CSWMBCCIDev, CSWMBCCIClass, CXL_SWITCH_MAILBOX_CCI)
|
|
|
|
|
2022-04-29 17:40:57 +03:00
|
|
|
MemTxResult cxl_type3_read(PCIDevice *d, hwaddr host_addr, uint64_t *data,
|
|
|
|
unsigned size, MemTxAttrs attrs);
|
|
|
|
MemTxResult cxl_type3_write(PCIDevice *d, hwaddr host_addr, uint64_t data,
|
|
|
|
unsigned size, MemTxAttrs attrs);
|
|
|
|
|
2023-04-23 19:20:09 +03:00
|
|
|
uint64_t cxl_device_get_timestamp(CXLDeviceState *cxlds);
|
|
|
|
|
2023-05-30 16:36:00 +03:00
|
|
|
void cxl_event_init(CXLDeviceState *cxlds, int start_msg_num);
|
2023-05-30 16:35:59 +03:00
|
|
|
bool cxl_event_insert(CXLDeviceState *cxlds, CXLEventLogType log_type,
|
|
|
|
CXLEventRecordRaw *event);
|
|
|
|
CXLRetCode cxl_event_get_records(CXLDeviceState *cxlds, CXLGetEventPayload *pl,
|
|
|
|
uint8_t log_type, int max_recs,
|
2023-10-23 19:07:51 +03:00
|
|
|
size_t *len);
|
2023-05-30 16:35:59 +03:00
|
|
|
CXLRetCode cxl_event_clear_records(CXLDeviceState *cxlds,
|
|
|
|
CXLClearEventPayload *pl);
|
|
|
|
|
2023-05-30 16:36:00 +03:00
|
|
|
void cxl_event_irq_assert(CXLType3Dev *ct3d);
|
|
|
|
|
2023-05-26 20:00:08 +03:00
|
|
|
void cxl_set_poison_list_overflowed(CXLType3Dev *ct3d);
|
|
|
|
|
2022-04-29 17:40:29 +03:00
|
|
|
#endif
|