hw: introduce a lightweight MCTP-over-I2C responder

[PATCH v1 0/2] hw: introduce a lightweight MCTP-over-I2C responder

Jian Zhang posted 2 patches 3 days, 8 hours ago

Download series mbox

Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20260408085941.3837334-1-zhangjian.3032@bytedance.com

Maintainers: "Cédric Le Goater" <clg@kaod.org>, Peter Maydell <peter.maydell@linaro.org>, Steven Lee <steven_lee@aspeedtech.com>, Troy Lee <leetroy@gmail.com>, Jamin Lin <jamin_lin@aspeedtech.com>, Kane Chen <kane_chen@aspeedtech.com>, Andrew Jeffery <andrew@codeconstruct.com.au>, Joel Stanley <joel@jms.id.au>, Paolo Bonzini <pbonzini@redhat.com>

MAINTAINERS                          |   2 +
hw/arm/aspeed_ast2600_evb.c          |  14 +
hw/misc/Kconfig                      |   5 +
hw/misc/mctp-i2c-responder-ncsi.c    | 777 +++++++++++++++++++++++++++
hw/misc/mctp-i2c-responder.c         | 694 ++++++++++++++++++++++++
hw/misc/meson.build                  |   5 +
include/hw/misc/mctp-i2c-responder.h | 116 ++++
7 files changed, 1613 insertions(+)
create mode 100644 hw/misc/mctp-i2c-responder-ncsi.c
create mode 100644 hw/misc/mctp-i2c-responder.c
create mode 100644 include/hw/misc/mctp-i2c-responder.h

Expand all Fold all

[PATCH v1 0/2] hw: introduce a lightweight MCTP-over-I2C responder

Posted by Jian Zhang 3 days, 8 hours ago

Hi,

MCTP (Management Component Transport Protocol) is a DMTF-defined
management transport protocol commonly used between BMCs and managed
components.

This series adds a lightweight MCTP implementation to QEMU. To keep the
scope small and make the first step easier to review, the current series
focuses only on the SMBus/I2C transport layer.

Patch 1 introduces a minimal MCTP-over-I2C responder core together with
a simple NCSI-related extension built on top of it. Patch 2 wires the
device into the ASPEED AST2600 EVB machine for initial testing.

The goal of this series is not to implement a full MCTP stack, but to
provide a small and practical foundation for simple emulation use cases.

This is my first submission to the QEMU upstream community, so any
comments, suggestions, or corrections would be valuable.

mctp spec[0]: https://www.dmtf.org/sites/default/files/standards/documents/DSP0236_1.3.1.pdf
mctp i2c binding[1]: https://www.dmtf.org/sites/default/files/standards/documents/DSP0237_1.2.0.pdf
ncsi spec[2]: https://www.dmtf.org/sites/default/files/standards/documents/DSP0222_1.2.0.pdf

Jian Zhang (2):
  hw/misc: introduce mctp I2C responder and NCSI support
  hw/arm/aspeed: add mctp responder device for test

 MAINTAINERS                          |   2 +
 hw/arm/aspeed_ast2600_evb.c          |  14 +
 hw/misc/Kconfig                      |   5 +
 hw/misc/mctp-i2c-responder-ncsi.c    | 777 +++++++++++++++++++++++++++
 hw/misc/mctp-i2c-responder.c         | 694 ++++++++++++++++++++++++
 hw/misc/meson.build                  |   5 +
 include/hw/misc/mctp-i2c-responder.h | 116 ++++
 7 files changed, 1613 insertions(+)
 create mode 100644 hw/misc/mctp-i2c-responder-ncsi.c
 create mode 100644 hw/misc/mctp-i2c-responder.c
 create mode 100644 include/hw/misc/mctp-i2c-responder.h

-- 
2.20.1