From: alison.schofield@intel.com
To: Davidlohr Bueso <dave@stgolabs.net>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Alison Schofield <alison.schofield@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Ira Weiny <ira.weiny@intel.com>,
	Dan Williams <dan.j.williams@intel.com>
Cc: linux-cxl@vger.kernel.org
Subject: [PATCH v2 0/2] Return EBUSY on inject poison limit reached
Date: Sat,  6 Jul 2024 18:53:42 -0700
Message-Id: <cover.1720316188.git.alison.schofield@intel.com>
X-Mailing-List: linux-cxl@vger.kernel.org
List-Id: <linux-cxl.vger.kernel.org>
List-Subscribe: <mailto:linux-cxl+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-cxl+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Xref: photonic.trudheim.com org.kernel.vger.linux-cxl:29325
Newsgroups: org.kernel.vger.linux-cxl
Path: photonic.trudheim.com!nntp.lore.kernel.org!not-for-mail

From: Alison Schofield <alison.schofield@intel.com>

Changes in v2:
- Use poison_inject_dev_max in cxl-test dev_dbg() msg and note that
  change in the Patch 2 commit log (Xingtao)
Link to v1: https://lore.kernel.org/cover.1720052137.git.alison.schofield@intel.com/

Validation users are asking for the ability to recognize when
their injection testing has hit the limit of the device.

Change the drivers error code for this failure to EBUSY and do
the same in the cxl-test mock of inject poison.

Alison Schofield (2):
  cxl/memdev: Replace ENXIO with EBUSY for inject poison limit reached
  cxl/test: Replace ENXIO with EBUSY for inject poison limit reached

 Documentation/ABI/testing/debugfs-cxl |  7 ++++---
 drivers/cxl/cxlmem.h                  |  2 +-
 tools/testing/cxl/test/mem.c          | 15 +++++++--------
 3 files changed, 12 insertions(+), 12 deletions(-)


base-commit: 22a40d14b572deb80c0648557f4bd502d7e83826
-- 
2.37.3

.

