From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Klaus Jensen <its@irrelevant.dk>
Cc: Corey Minyard <cminyard@mvista.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Jason Wang <jasowang@redhat.com>, Keith Busch <kbusch@kernel.org>,
Lior Weintraub <liorw@pliops.com>,
Jeremy Kerr <jk@codeconstruct.com.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Matt Johnston <matt@codeconstruct.com.au>,
Peter Delevoryas <peter@pjd.dev>, <qemu-devel@nongnu.org>,
<qemu-arm@nongnu.org>, <qemu-block@nongnu.org>,
Klaus Jensen <k.jensen@samsung.com>
Subject: Re: [PATCH v6 0/3] hw/{i2c,nvme}: mctp endpoint, nvme management interface model
Date: Wed, 20 Sep 2023 12:48:03 +0100 [thread overview]
Message-ID: <20230920124803.00005ae9@Huawei.com> (raw)
In-Reply-To: <20230914-nmi-i2c-v6-0-11bbb4f74d18@samsung.com>
On Thu, 14 Sep 2023 11:53:40 +0200
Klaus Jensen <its@irrelevant.dk> wrote:
> This adds a generic MCTP endpoint model that other devices may derive
> from.
>
> Also included is a very basic implementation of an NVMe-MI device,
> supporting only a small subset of the required commands.
>
> Since this all relies on i2c target mode, this can currently only be
> used with an SoC that includes the Aspeed I2C controller.
>
> The easiest way to get up and running with this, is to grab my buildroot
> overlay[1] (aspeed_ast2600evb_nmi_defconfig). It includes modified a
> modified dts as well as a couple of required packages.
>
> QEMU can then be launched along these lines:
>
> qemu-system-arm \
> -nographic \
> -M ast2600-evb \
> -kernel output/images/zImage \
> -initrd output/images/rootfs.cpio \
> -dtb output/images/aspeed-ast2600-evb-nmi.dtb \
> -nic user,hostfwd=tcp::2222-:22 \
> -device nmi-i2c,address=0x3a \
> -serial mon:stdio
>
> From within the booted system,
>
> mctp addr add 8 dev mctpi2c15
> mctp link set mctpi2c15 up
> mctp route add 9 via mctpi2c15
> mctp neigh add 9 dev mctpi2c15 lladdr 0x3a
> mi-mctp 1 9 info
>
> Comments are very welcome!
>
> [1]: https://github.com/birkelund/hwtests/tree/main/br2-external
>
> Signed-off-by: Klaus Jensen <k.jensen@samsung.com>
Hi Klaus,
Silly question, but who is likely to pick this up? + likely to be soon?
I'm going to post the CXL stuff that makes use of the core support shortly
and whilst I can point at this patch set on list, I'd keen to see it upstream
to reduce the dependencies (it's got 2 sets ahead of it of CXL stuff
anyway but that will all hopefully go through Michael Tsirkin's tree
for PCI stuff in one go).
Jonathan
> ---
> Changes in v6:
> - Use nmi_scratch_append() directly where it makes sense. Fixes bug
> observed by Andrew.
> - Link to v5: https://lore.kernel.org/r/20230905-nmi-i2c-v5-0-0001d372a728@samsung.com
>
> Changes in v5:
> - Added a nmi_scratch_append() that asserts available space in the
> scratch buffer. This is a similar defensive strategy as used in
> hw/i2c/mctp.c
> - Various small fixups in response to review (Jonathan)
> - Link to v4: https://lore.kernel.org/r/20230823-nmi-i2c-v4-0-2b0f86e5be25@samsung.com
>
> ---
> Klaus Jensen (3):
> hw/i2c: add smbus pec utility function
> hw/i2c: add mctp core
> hw/nvme: add nvme management interface model
>
> MAINTAINERS | 7 +
> hw/arm/Kconfig | 1 +
> hw/i2c/Kconfig | 4 +
> hw/i2c/mctp.c | 432 ++++++++++++++++++++++++++++++++++++++++++
> hw/i2c/meson.build | 1 +
> hw/i2c/smbus_master.c | 26 +++
> hw/i2c/trace-events | 13 ++
> hw/nvme/Kconfig | 4 +
> hw/nvme/meson.build | 1 +
> hw/nvme/nmi-i2c.c | 407 +++++++++++++++++++++++++++++++++++++++
> hw/nvme/trace-events | 6 +
> include/hw/i2c/mctp.h | 125 ++++++++++++
> include/hw/i2c/smbus_master.h | 2 +
> include/net/mctp.h | 35 ++++
> 14 files changed, 1064 insertions(+)
> ---
> base-commit: 005ad32358f12fe9313a4a01918a55e60d4f39e5
> change-id: 20230822-nmi-i2c-d804ed5be7e6
>
> Best regards,
next prev parent reply other threads:[~2023-09-20 11:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 9:53 [PATCH v6 0/3] hw/{i2c,nvme}: mctp endpoint, nvme management interface model Klaus Jensen
2023-09-14 9:53 ` [PATCH v6 1/3] hw/i2c: add smbus pec utility function Klaus Jensen
2023-09-14 20:56 ` Corey Minyard
2023-09-21 7:11 ` Andrew Jeffery
2023-09-14 9:53 ` [PATCH v6 2/3] hw/i2c: add mctp core Klaus Jensen
2023-09-14 20:56 ` Corey Minyard
2023-09-21 7:10 ` Andrew Jeffery
2023-09-14 9:53 ` [PATCH v6 3/3] hw/nvme: add nvme management interface model Klaus Jensen
2023-09-14 21:01 ` Corey Minyard
2023-09-21 7:08 ` Andrew Jeffery
2023-09-20 11:48 ` Jonathan Cameron via [this message]
2023-09-20 12:54 ` [PATCH v6 0/3] hw/{i2c,nvme}: mctp endpoint, " Corey Minyard
2023-09-20 13:31 ` Klaus Jensen
2023-09-20 14:36 ` Corey Minyard
2024-10-14 9:36 ` Jonathan Cameron via
2024-10-30 6:01 ` Klaus Jensen
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=20230920124803.00005ae9@Huawei.com \
--to=qemu-devel@nongnu.org \
--cc=Jonathan.Cameron@Huawei.com \
--cc=andrew@codeconstruct.com.au \
--cc=cminyard@mvista.com \
--cc=its@irrelevant.dk \
--cc=jasowang@redhat.com \
--cc=jk@codeconstruct.com.au \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=liorw@pliops.com \
--cc=matt@codeconstruct.com.au \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peter@pjd.dev \
--cc=qemu-arm@nongnu.org \
--cc=qemu-block@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).