From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Prashant V Agarwal <agpr123@gmail.com>,
Ben Widawsky <ben.widawsky@intel.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: CXL support in QEMU
Date: Wed, 16 Dec 2020 13:42:51 +0000 [thread overview]
Message-ID: <20201216134251.000052d0@Huawei.com> (raw)
In-Reply-To: <07f753bd-45d8-d65d-6195-25f9dfb74795@redhat.com>
On Wed, 16 Dec 2020 10:53:34 +0100
Thomas Huth <thuth@redhat.com> wrote:
> On 16/12/2020 06.05, Prashant V Agarwal wrote:
> > Hi,
> > Is there a way to know the support plans for CXL protocol in QEMU?
> > I see that there is side branch development going on:
> >
> > https://gitlab.com/bwidawsk/qemu/-/tree/cxl-2.0v2
> > <https://gitlab.com/bwidawsk/qemu/-/tree/cxl-2.0v2>
> >
> > But when does it get merged and gets released in QEMU formally?
> > Is there a way to know a rough timeline?
>
> You should rather the authors of that repository whether and when they plan
> to contribute their changes to the QEMU project. It's certainly not going to
> happen automatically that these patches get merged into the main repository.
>
> Thomas
>
Worth noting that they have posted an RFC, so I would suggest replying to
that thread to make sure you get all the right people.
https://lore.kernel.org/qemu-devel/20201111054724.794888-1-ben.widawsky@intel.com/#r
+CC Ben
next prev parent reply other threads:[~2020-12-16 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 5:05 CXL support in QEMU Prashant V Agarwal
2020-12-16 9:53 ` Thomas Huth
2020-12-16 13:42 ` Jonathan Cameron [this message]
2020-12-16 16:03 ` Ben Widawsky
2020-12-16 17:08 ` Thomas Huth
2020-12-16 17:40 ` Ben Widawsky
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=20201216134251.000052d0@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=agpr123@gmail.com \
--cc=ben.widawsky@intel.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).