From: Thomas Huth <thuth@redhat.com>
To: Ben Widawsky <ben.widawsky@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: Prashant V Agarwal <agpr123@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: CXL support in QEMU
Date: Wed, 16 Dec 2020 18:08:54 +0100 [thread overview]
Message-ID: <9e4747fe-c166-e5aa-55b2-ac58be7f0268@redhat.com> (raw)
In-Reply-To: <20201216160314.m72v7ynqnv3opu6s@intel.com>
On 16/12/2020 17.03, Ben Widawsky wrote:
> On 20-12-16 13:42:51, Jonathan Cameron wrote:
>> 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
>>
>
> I haven't posted v2 yet because I have a few more changes I wanted to make
> before doing so, however v2 has all of Jonathan's feedback plus a few minor
> things.
>
> Thomas, it's been CC'd to a few folks outside of the list itself, but I couldn't
> get much in the way of reviewers. Advice on that is welcome.
Maybe add some more people on CC: who are familiar with x86? See the
MAINTAINERS file and look for "86" in there...
HTH,
Thomas
next prev parent reply other threads:[~2020-12-16 17:12 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
2020-12-16 16:03 ` Ben Widawsky
2020-12-16 17:08 ` Thomas Huth [this message]
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=9e4747fe-c166-e5aa-55b2-ac58be7f0268@redhat.com \
--to=thuth@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=agpr123@gmail.com \
--cc=ben.widawsky@intel.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).