All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: <shiju.jose@huawei.com>
Cc: <qemu-devel@nongnu.org>, <linux-cxl@vger.kernel.org>,
	<fan.ni@samsung.com>, <dave@stgolabs.net>, <linuxarm@huawei.com>
Subject: Re: [PATCH v3 1/7] hw/cxl/events: Update for rev3.2 common event record format
Date: Thu, 3 Jul 2025 13:51:36 +0100	[thread overview]
Message-ID: <20250703135136.00002b0d@huawei.com> (raw)
In-Reply-To: <20250703091657.1868-2-shiju.jose@huawei.com>

On Thu, 3 Jul 2025 10:16:50 +0100
<shiju.jose@huawei.com> wrote:

> From: Shiju Jose <shiju.jose@huawei.com>
> 
> CXL spec 3.2 section 8.2.9.2.1 Table 8-55, Common Event Record
> format has updated with optional Maintenance Operation Subclass,
> LD ID and ID of the device head information.
> 
> Add updates for the above optional parameters in the related
> CXL events reporting and in the QMP commands to inject CXL events.
> 
> Signed-off-by: Shiju Jose <shiju.jose@huawei.com>
Hi Shiju,

Anisa's fmapi-dcd series moved one instance of this from cxl_type3.c to cxl/cxl-events.c
I'll tweak that whilst applying it to my gitlab tree.

Doesn't make any fundamental difference for anyone wishing to review
the series.

Thanks,

Jonathan


WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: <shiju.jose@huawei.com>
Cc: <qemu-devel@nongnu.org>, <linux-cxl@vger.kernel.org>,
	<fan.ni@samsung.com>, <dave@stgolabs.net>, <linuxarm@huawei.com>
Subject: Re: [PATCH v3 1/7] hw/cxl/events: Update for rev3.2 common event record format
Date: Thu, 3 Jul 2025 13:51:36 +0100	[thread overview]
Message-ID: <20250703135136.00002b0d@huawei.com> (raw)
In-Reply-To: <20250703091657.1868-2-shiju.jose@huawei.com>

On Thu, 3 Jul 2025 10:16:50 +0100
<shiju.jose@huawei.com> wrote:

> From: Shiju Jose <shiju.jose@huawei.com>
> 
> CXL spec 3.2 section 8.2.9.2.1 Table 8-55, Common Event Record
> format has updated with optional Maintenance Operation Subclass,
> LD ID and ID of the device head information.
> 
> Add updates for the above optional parameters in the related
> CXL events reporting and in the QMP commands to inject CXL events.
> 
> Signed-off-by: Shiju Jose <shiju.jose@huawei.com>
Hi Shiju,

Anisa's fmapi-dcd series moved one instance of this from cxl_type3.c to cxl/cxl-events.c
I'll tweak that whilst applying it to my gitlab tree.

Doesn't make any fundamental difference for anyone wishing to review
the series.

Thanks,

Jonathan



  reply	other threads:[~2025-07-03 12:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03  9:16 [PATCH v3 0/7] hw/cxl: Update CXL events to rev3.2 and add maintenance support for memory repair features shiju.jose
2025-07-03  9:16 ` shiju.jose--- via
2025-07-03  9:16 ` [PATCH v3 1/7] hw/cxl/events: Update for rev3.2 common event record format shiju.jose
2025-07-03  9:16   ` shiju.jose--- via
2025-07-03 12:51   ` Jonathan Cameron [this message]
2025-07-03 12:51     ` Jonathan Cameron via
2025-07-03  9:16 ` [PATCH v3 2/7] hw/cxl/events: Updates for rev3.2 general media event record shiju.jose
2025-07-03  9:16   ` shiju.jose--- via
2025-07-03  9:16 ` [PATCH v3 3/7] hw/cxl/events: Updates for rev3.2 DRAM " shiju.jose
2025-07-03  9:16   ` shiju.jose--- via
2025-07-03  9:16 ` [PATCH v3 4/7] hw/cxl/events: Updates for rev3.2 memory module " shiju.jose
2025-07-03  9:16   ` shiju.jose--- via
2025-07-03  9:16 ` [PATCH v3 5/7] hw/cxl/cxl-mailbox-utils: Move declaration of scrub and ECS feature attributes in cmd_features_set_feature() shiju.jose
2025-07-03  9:16   ` shiju.jose--- via
2025-07-03  9:16 ` [PATCH v3 6/7] hw/cxl: Add Maintenance support shiju.jose
2025-07-03  9:16   ` shiju.jose--- via
2025-07-03  9:16 ` [PATCH v3 7/7] hw/cxl: Add emulation for memory sparing control feature shiju.jose
2025-07-03  9:16   ` shiju.jose--- via

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250703135136.00002b0d@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=dave@stgolabs.net \
    --cc=fan.ni@samsung.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shiju.jose@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.