diff options
| author | Alison Schofield <[email protected]> | 2023-04-18 20:26:33 -0700 |
|---|---|---|
| committer | Dan Williams <[email protected]> | 2023-04-23 12:08:39 -0700 |
| commit | 98980d76c3fc3d56b34e425eb102b10355ccc743 (patch) | |
| tree | 3ceb586c609d5f43ce95e8d93ecba1b8b70f9c4f /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | 8eac7ea72593010726713c5359a4b6aedf29b6fe (diff) | |
tools/testing/cxl: Add a sysfs attr to test poison inject limits
CXL devices may report a maximum number of addresses that a device
allows to be poisoned using poison injection. When cxl_test creates
mock CXL memory devices, it defaults to MOCK_INJECT_DEV_MAX==88 for
all mocked memdevs.
Add a sysfs attribute, poison_inject_max to module cxl_mock_mem so
that users can set a custom device injection limit. Fail, and return
-EBUSY, if the mock poison list is not empty.
/sys/bus/platform/drivers/cxl_mock_mem/poison_inject_max
A simple usage model is to set the attribute before running a test in
order to emulate a device's poison handling.
Signed-off-by: Alison Schofield <[email protected]>
Reviewed-by: Dave Jiang <[email protected]>
Link: https://lore.kernel.org/r/0f25b2862b90013545450222d2199e435c6cc11a.1681874357.git.alison.schofield@intel.com
Signed-off-by: Dan Williams <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions