From: Ben Widawsky <ben.widawsky@intel.com>
To: Shreyas Shah <shreyas.shah@elastics.cloud>
Cc: Saransh Gupta1 <saransh@ibm.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: Follow-up on the CXL discussion at OFTC
Date: Thu, 18 Nov 2021 19:25:41 -0800 [thread overview]
Message-ID: <20211119032541.gr6berwu2ve4tkax@intel.com> (raw)
In-Reply-To: <BY5PR12MB4179AA1B062AEA75098E15D8E89C9@BY5PR12MB4179.namprd12.prod.outlook.com>
On 21-11-19 02:29:51, Shreyas Shah wrote:
> Hi Ben
>
> Are you planning to add the CXL2.0 switch inside QEMU or already added in one of the version?
>
From me, there are no plans for QEMU anything until/unless upstream thinks it
will merge the existing patches, or provide feedback as to what it would take to
get them merged. If upstream doesn't see a point in these patches, then I really
don't see much value in continuing to further them. Once hardware comes out, the
value proposition is certainly less.
Having said that, once I get the port/region patches merged for the Linux
driver, I do intend to go back and try to implement a basic switch so that we
can test those flows.
I admit, I'm curious why you're interested in switches.
> Regards,
> Shreyas
>
> -----Original Message-----
> From: Ben Widawsky <ben.widawsky@intel.com>
> Sent: Thursday, November 18, 2021 5:48 PM
> To: Shreyas Shah <shreyas.shah@elastics.cloud>
> Cc: Saransh Gupta1 <saransh@ibm.com>; Jonathan Cameron <Jonathan.Cameron@huawei.com>; linux-cxl@vger.kernel.org; qemu-devel@nongnu.org
> Subject: Re: Follow-up on the CXL discussion at OFTC
>
> On 21-11-18 22:52:56, Shreyas Shah wrote:
> > Hello Folks,
> >
> > Any plan to add CXL2.0 switch ports in QEMU?
>
> What's your definition of plan?
>
> >
> > Regards,
> > Shreyas
>
> [snip]
WARNING: multiple messages have this Message-ID (diff)
From: Ben Widawsky <ben.widawsky@intel.com>
To: Shreyas Shah <shreyas.shah@elastics.cloud>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
Saransh Gupta1 <saransh@ibm.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: Follow-up on the CXL discussion at OFTC
Date: Thu, 18 Nov 2021 19:25:41 -0800 [thread overview]
Message-ID: <20211119032541.gr6berwu2ve4tkax@intel.com> (raw)
In-Reply-To: <BY5PR12MB4179AA1B062AEA75098E15D8E89C9@BY5PR12MB4179.namprd12.prod.outlook.com>
On 21-11-19 02:29:51, Shreyas Shah wrote:
> Hi Ben
>
> Are you planning to add the CXL2.0 switch inside QEMU or already added in one of the version?
>
From me, there are no plans for QEMU anything until/unless upstream thinks it
will merge the existing patches, or provide feedback as to what it would take to
get them merged. If upstream doesn't see a point in these patches, then I really
don't see much value in continuing to further them. Once hardware comes out, the
value proposition is certainly less.
Having said that, once I get the port/region patches merged for the Linux
driver, I do intend to go back and try to implement a basic switch so that we
can test those flows.
I admit, I'm curious why you're interested in switches.
> Regards,
> Shreyas
>
> -----Original Message-----
> From: Ben Widawsky <ben.widawsky@intel.com>
> Sent: Thursday, November 18, 2021 5:48 PM
> To: Shreyas Shah <shreyas.shah@elastics.cloud>
> Cc: Saransh Gupta1 <saransh@ibm.com>; Jonathan Cameron <Jonathan.Cameron@huawei.com>; linux-cxl@vger.kernel.org; qemu-devel@nongnu.org
> Subject: Re: Follow-up on the CXL discussion at OFTC
>
> On 21-11-18 22:52:56, Shreyas Shah wrote:
> > Hello Folks,
> >
> > Any plan to add CXL2.0 switch ports in QEMU?
>
> What's your definition of plan?
>
> >
> > Regards,
> > Shreyas
>
> [snip]
next prev parent reply other threads:[~2021-11-19 3:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF255704A1.78FEF164-ON0025878E.00821084-0025878F.00015560@ibm.com>
2021-11-17 16:57 ` Follow-up on the CXL discussion at OFTC Ben Widawsky
2021-11-17 17:32 ` Jonathan Cameron
2021-11-17 17:32 ` Jonathan Cameron
2021-11-18 22:20 ` Saransh Gupta1
2021-11-18 22:20 ` Saransh Gupta1
2021-11-18 22:52 ` Shreyas Shah
2021-11-18 22:52 ` Shreyas Shah via
2021-11-19 1:48 ` Ben Widawsky
2021-11-19 1:48 ` Ben Widawsky
2021-11-19 2:29 ` Shreyas Shah
2021-11-19 2:29 ` Shreyas Shah via
2021-11-19 3:25 ` Ben Widawsky [this message]
2021-11-19 3:25 ` Ben Widawsky
2021-11-26 12:08 ` Alex Bennée
2021-11-26 12:08 ` Alex Bennée
2021-11-29 17:16 ` Ben Widawsky
2021-11-29 17:16 ` Ben Widawsky
2021-11-29 18:28 ` Alex Bennée
2021-11-29 18:28 ` Alex Bennée
2021-11-30 13:09 ` Jonathan Cameron
2021-11-30 13:09 ` Jonathan Cameron via
2021-11-30 17:21 ` Ben Widawsky
2021-11-30 17:21 ` Ben Widawsky
2021-12-01 9:55 ` Jonathan Cameron
2021-12-01 9:55 ` Jonathan Cameron via
2021-12-01 10:29 ` Alex Bennée
2021-12-01 10:29 ` Alex Bennée
2021-11-19 1:52 ` Ben Widawsky
2021-11-19 1:52 ` Ben Widawsky
2021-11-19 18:53 ` Jonathan Cameron
2021-11-19 18:53 ` Jonathan Cameron
2021-11-19 20:21 ` Ben Widawsky
2021-11-19 20:21 ` Ben Widawsky
2021-11-26 10:59 ` Jonathan Cameron
2021-11-26 10:59 ` Jonathan Cameron via
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=20211119032541.gr6berwu2ve4tkax@intel.com \
--to=ben.widawsky@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=saransh@ibm.com \
--cc=shreyas.shah@elastics.cloud \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.