From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Ravi Kanth <mvrravikanth@gmail.com>
Cc: <linux-cxl@vger.kernel.org>
Subject: Re: Support for CXL v3.0 spec with QEMU
Date: Thu, 10 Aug 2023 17:33:22 +0100 [thread overview]
Message-ID: <20230810173322.0000543c@Huawei.com> (raw)
In-Reply-To: <CAEvOrRz9s8CumbuMbkCU+eCHgAp20X6q0i1D6fi5vfa5_F6JnA@mail.gmail.com>
On Thu, 10 Aug 2023 21:42:12 +0530
Ravi Kanth <mvrravikanth@gmail.com> wrote:
> Hello,
Hi Ravi,
>
> I am writing this mail to know if the latest QEMU has support for CXL
> spec v3.0? I understand from the older tutorials that QEMU has support
> for CXL v2.0. Is there any update to QEMU to support the CXL v3.0? I
> would like to specifically test the CCI mailbox functionality which
> has been added to CXL v3.0 spec.
The nature of the CXL specification and the QEMU support is that for
devices there isn't a clear divide between different generations of
the specification. By that I mean, that a device based on the CXL 2.0
specification is compatible with the CXL 3.0 specification. As such,
the QEMU emulation has focused on features of interest - it is a far
from complete implementation of all the options in the CXL 2.0
specification but conversely there are some parts of CXL 3.0 are supported.
Note that the particular CCI functionality is not yet ready for CXL upstream,
but we do have some support in the staging tree I maintain.
https://gitlab.com/jic23/qemu/-/commits/cxl-2023-08-07/
specifically
https://gitlab.com/jic23/qemu/-/commit/2eb7e6402a45b359c304cea894a1d27625a4b80c
Note at this stage we only support subset of commands.
Contributions of more support welcomed!
Intent of the current support and related MCTP CCI access (over I2C) is
to enable ecosystem development, particularly of fabric managers.
For that a tiny subset of commands was sufficient to be sure the architecture
inside QEMU worked and that the proposed kernel code functions correctly.
Jonathan
>
> Thank you in advance for your assistance.
>
> Ravi
next prev parent reply other threads:[~2023-08-10 16:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 16:12 Support for CXL v3.0 spec with QEMU Ravi Kanth
2023-08-10 16:33 ` Jonathan Cameron [this message]
2023-08-10 16:40 ` Ravi Kanth
2023-08-11 12:04 ` Ravi Kanth
2023-08-11 13:52 ` Jonathan Cameron
2023-08-16 11:41 ` Ravi Kanth
2023-08-23 17:03 ` Jonathan Cameron
2023-09-01 14:03 ` Ravi Kanth
2023-09-01 14:18 ` Gregory Price
2023-09-01 14:37 ` Ravi Kanth
2023-09-01 16:19 ` Ravi Kanth
[not found] ` <SJ0PR17MB5512449C5FFD76AD50B3D3AF83E4A@SJ0PR17MB5512.namprd17.prod.outlook.com>
2023-09-02 14:58 ` Ravi Kanth
2023-10-18 10:30 ` Ravi Kanth
2023-10-19 17:08 ` Ravi Kanth
2023-10-20 20:38 ` Ira Weiny
2023-10-22 6:45 ` Ravi Kanth
2023-10-23 13:50 ` Jonathan Cameron
2023-10-26 1:52 ` Ravi Kanth
2023-10-26 8:59 ` Jonathan Cameron
2023-10-23 13:44 ` Jonathan Cameron
2023-08-11 13:49 ` Jonathan Cameron
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=20230810173322.0000543c@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=mvrravikanth@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox