From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-10.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_2 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 06AB5C4361B for ; Wed, 16 Dec 2020 13:48:40 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id A45342255F for ; Wed, 16 Dec 2020 13:48:39 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org A45342255F Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=Huawei.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:42916 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kpXAU-0005V1-LP for qemu-devel@archiver.kernel.org; Wed, 16 Dec 2020 08:48:38 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:38118) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kpX5j-0000Ti-0p for qemu-devel@nongnu.org; Wed, 16 Dec 2020 08:43:43 -0500 Received: from frasgout.his.huawei.com ([185.176.79.56]:2073) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kpX5e-0005GN-6C for qemu-devel@nongnu.org; Wed, 16 Dec 2020 08:43:42 -0500 Received: from fraeml736-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Cwx8W2lWcz67QjS; Wed, 16 Dec 2020 21:40:27 +0800 (CST) Received: from lhreml710-chm.china.huawei.com (10.201.108.61) by fraeml736-chm.china.huawei.com (10.206.15.217) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Wed, 16 Dec 2020 14:43:19 +0100 Received: from localhost (10.47.78.133) by lhreml710-chm.china.huawei.com (10.201.108.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Wed, 16 Dec 2020 13:43:19 +0000 Date: Wed, 16 Dec 2020 13:42:51 +0000 From: Jonathan Cameron To: Thomas Huth Subject: Re: CXL support in QEMU Message-ID: <20201216134251.000052d0@Huawei.com> In-Reply-To: <07f753bd-45d8-d65d-6195-25f9dfb74795@redhat.com> References: <07f753bd-45d8-d65d-6195-25f9dfb74795@redhat.com> Organization: Huawei Technologies Research and Development (UK) Ltd. X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; i686-w64-mingw32) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.47.78.133] X-ClientProxiedBy: lhreml742-chm.china.huawei.com (10.201.108.192) To lhreml710-chm.china.huawei.com (10.201.108.61) X-CFilter-Loop: Reflected Received-SPF: pass client-ip=185.176.79.56; envelope-from=jonathan.cameron@huawei.com; helo=frasgout.his.huawei.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Prashant V Agarwal , Ben Widawsky , QEMU Developers Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Wed, 16 Dec 2020 10:53:34 +0100 Thomas Huth 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 > > > > > > 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