From: nifan.cxl@gmail.com
To: jonathan.cameron@huawei.com, qemu-devel@nongnu.org
Cc: linux-cxl@vger.kernel.org, a.manzanares@samsung.com,
dave@stgolabs.net, nmtadam.samsung@gmail.com,
nifan.cxl@gmail.com, anisa.su887@gmail.com, gourry@gourry.net,
Fan Ni <fan.ni@samsung.com>
Subject: [RFC 2/3] cxl_type3: Add qmp_cxl_process_mctp_message qmp interface
Date: Mon, 7 Apr 2025 21:20:29 -0700 [thread overview]
Message-ID: <20250408043051.430340-3-nifan.cxl@gmail.com> (raw)
In-Reply-To: <20250408043051.430340-1-nifan.cxl@gmail.com>
From: Fan Ni <fan.ni@samsung.com>
Add a new QAPI "qmp-cxl-process-mctp-message" to process the MCTP
request cached in the shared buffer from FM VM.
Signed-off-by: Fan Ni <fan.ni@samsung.com>
---
hw/mem/cxl_type3.c | 41 ++++++++++++++++++++++++++++++++++++++++
hw/mem/cxl_type3_stubs.c | 5 +++++
qapi/cxl.json | 18 ++++++++++++++++++
3 files changed, 64 insertions(+)
diff --git a/hw/mem/cxl_type3.c b/hw/mem/cxl_type3.c
index 7f85616ca1..f7ac8e8da7 100644
--- a/hw/mem/cxl_type3.c
+++ b/hw/mem/cxl_type3.c
@@ -1614,6 +1614,47 @@ void cxl_clear_poison_list_overflowed(CXLType3Dev *ct3d)
ct3d->poison_list_overflow_ts = 0;
}
+void qmp_cxl_process_mctp_message(const char *cci_name, Error **errp)
+{
+ int i;
+ struct CXLCCINamePtrMap *map;
+ struct CXLMCTPCommandBuf *buf;
+ CXLCCI *cci = NULL;
+ CXLType3Dev *ct3d;
+
+ if (!cci_map_buf) {
+ error_setg(errp, "CCI name mapping buffer not setup");
+ return;
+ }
+
+ for (i = 0; i < cci_map_buf->num_mappings; i++) {
+ map = &cci_map_buf->maps[i];
+ if (!strcmp(map->cci_name, cci_name)) {
+ cci = (CXLCCI *) map->cci_pointer;
+ break;
+ }
+ }
+ if (!cci) {
+ error_setg(errp, "CCI instance is not found with name: %s", cci_name);
+ return;
+ }
+ ct3d = CXL_TYPE3(OBJECT(cci->d));
+ if (!ct3d) {
+ error_setg(errp, "No Type3 device associated with the cci");
+ return;
+ }
+ if (ct3d->mctp_shared_buffer->status != 1) {
+ error_setg(errp, "MCTP buffer status is not set to 1, skip");
+ return;
+ }
+ buf = &ct3d->mctp_shared_buffer->command_buf;
+ buf->ret_val = cxl_process_cci_message(cci, buf->command_set, buf->command,
+ buf->len_in, buf->payload,
+ &buf->len_out, buf->payload_out,
+ &buf->bg_started);
+ ct3d->mctp_shared_buffer->status = 0;
+}
+
void qmp_cxl_inject_poison(const char *path, uint64_t start, uint64_t length,
Error **errp)
{
diff --git a/hw/mem/cxl_type3_stubs.c b/hw/mem/cxl_type3_stubs.c
index c1a5e4a7c1..dbf18f2af2 100644
--- a/hw/mem/cxl_type3_stubs.c
+++ b/hw/mem/cxl_type3_stubs.c
@@ -92,3 +92,8 @@ void qmp_cxl_release_dynamic_capacity(const char *path, uint16_t host_id,
{
error_setg(errp, "CXL Type 3 support is not compiled in");
}
+
+void qmp_cxl_process_mctp_message(const char *cci_name, Error **errp)
+{
+ error_setg(errp, "CXL Type 3 support is not compiled in");
+}
diff --git a/qapi/cxl.json b/qapi/cxl.json
index dd947d3bbc..fcb1e0b3fd 100644
--- a/qapi/cxl.json
+++ b/qapi/cxl.json
@@ -553,3 +553,21 @@
},
'features': [ 'unstable' ]
}
+
+##
+# @cxl-process-mctp-message:
+#
+# Command to process a MCTP command sent from another VM.
+#
+# @cci-name: name of the CCI to process the command;
+#
+# Features:
+#
+# @unstable: For now this command is subject to change.
+#
+# Since: 9.1
+##
+{'command': 'cxl-process-mctp-message',
+ 'data': {'cci-name': 'str'},
+ 'features': [ 'unstable' ]
+ }
--
2.47.2
next prev parent reply other threads:[~2025-04-08 4:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 4:20 [RFC 0/3] Qemu FM emulation nifan.cxl
2025-04-08 4:20 ` [RFC 1/3] cxl_type3: Preparing information sharing between VMs nifan.cxl
2025-04-08 4:20 ` nifan.cxl [this message]
2025-04-08 4:20 ` [RFC 3/3] cxl/i2c_mctp_cxl: Add support to process MCTP command remotely nifan.cxl
2025-04-08 15:04 ` [RFC 0/3] Qemu FM emulation Gregory Price
2025-04-14 15:44 ` Fan Ni
2025-04-15 15:37 ` Jonathan Cameron 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=20250408043051.430340-3-nifan.cxl@gmail.com \
--to=nifan.cxl@gmail.com \
--cc=a.manzanares@samsung.com \
--cc=anisa.su887@gmail.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=gourry@gourry.net \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nmtadam.samsung@gmail.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).