From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4973F1E7C23 for ; Fri, 2 Jan 2026 15:15:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.176.79.56 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767366919; cv=none; b=oaWtlokpHfaB1bBrNr3XrPl/dsXI5CZfdXAjXmiyr7qPsrWgvp9lscDvm4UZF+pxFnyCr8ATNZ3kCR4w+trm80qFiwO43Yv0pc01Df7ehLxhq3DbvZvde1sbr+zH1xNY6HhecFZUkbYyYeBaDhqpfuHU/wqQMl7R0AeyBfJcuHc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767366919; c=relaxed/simple; bh=EQ1dhy3suI4aJygEBgEm4jp6DZlzD6y4+qG+xAHBO3Q=; h=From:To:CC:Subject:Date:Message-ID:MIME-Version:Content-Type; b=ouHXY+r7kaoqV9sM0Dm0DjYWsYeubl+3z0+pBUTsugoJ+ZDxL4twg9iESQbdpyK17z+H4qUxg2NHy7FmXRCiwKo9fx30KST7PcglzhRjfWviGqJEwbLrNOeFxo4+FIo9fIRcLKgV4JmG4DCQX72O4nWlocgIPYi2N5Dy6HvWmnE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=185.176.79.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.18.224.83]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4djS0B08StzJ467L; Fri, 2 Jan 2026 23:14:18 +0800 (CST) Received: from dubpeml100005.china.huawei.com (unknown [7.214.146.113]) by mail.maildlp.com (Postfix) with ESMTPS id A1F494056F; Fri, 2 Jan 2026 23:15:13 +0800 (CST) Received: from SecurePC-101-06.huawei.com (10.122.19.247) by dubpeml100005.china.huawei.com (7.214.146.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.36; Fri, 2 Jan 2026 15:15:13 +0000 From: Jonathan Cameron To: Michael Tsirkin , , , CC: , , Ravi Shankar Subject: [PATCH qemu v2 0/5] cxl: r3.2 specification event updates. Date: Fri, 2 Jan 2026 15:15:07 +0000 Message-ID: <20260102151512.460766-1-Jonathan.Cameron@huawei.com> X-Mailer: git-send-email 2.48.1 Precedence: bulk X-Mailing-List: linux-cxl@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-ClientProxiedBy: lhrpeml500012.china.huawei.com (7.191.174.4) To dubpeml100005.china.huawei.com (7.214.146.113) Hi Michael, This is a rebase/resend of: https://lore.kernel.org/qemu-devel/20250917141355.293217-1-Jonathan.Cameron@huawei.com/ which I think slipped through the cracks for 10.2. Original cover letter: This is the 1st CXL set that I think is ready for upstream. They are lightly tweaked and rebased from the first part of: https://lore.kernel.org/qemu-devel/20250811085530.2263-1-shiju.jose@huawei.com/ [PATCH v6 0/8] hw/cxl: Update CXL events to rev3.2 and add maintenance support for memory repair features I've split that series up as the two parts were only slightly connected. The initial rework was a request from Markus from an earlier version. Shiju Jose (5): qapi: cxl: Refactor CXL event injection for common commands arguments hw/cxl/events: Update for rev3.2 common event record format hw/cxl/events: Updates for rev3.2 general media event record hw/cxl/events: Updates for rev3.2 DRAM event record hw/cxl/events: Updates for rev3.2 memory module event record qapi/cxl.json | 151 +++++++++++++++++++++++++-------- include/hw/cxl/cxl_device.h | 7 +- include/hw/cxl/cxl_events.h | 38 +++++++-- hw/cxl/cxl-events.c | 3 +- hw/cxl/cxl-mailbox-utils.c | 3 +- hw/mem/cxl_type3.c | 163 ++++++++++++++++++++++++++++++++++-- hw/mem/cxl_type3_stubs.c | 41 ++++++++- 7 files changed, 347 insertions(+), 59 deletions(-) -- 2.48.1