From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9D52E152E04 for ; Mon, 22 Apr 2024 15:07:45 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.176.79.56 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1713798469; cv=none; b=ny8KvvzTouRQjkmdTeqCMK+DkVsXswiukpSkXS7ltJiS87OX/CjLze3u0erFCC2I2DFAnjWeEvg9Xlf5wjfPEGVi0vnKH47NuVFeo47lqF446pQEIU3pK7W90hqFzkKRg2w6MqmFBLzgZpFCi1PyL//fE1YTlm9TMZzUKX5gYC4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1713798469; c=relaxed/simple; bh=5bgonCb2OxkjhgzheYEKNdR512KUi+U0PomMSb4+Od0=; h=Date:From:To:CC:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=IxoOcjA6AIX/VXJVXRKYYM+qbf+jVHOrOyzCXyAuFBvsmjiXHks/EeG/G4AlWvKJ8LjRl7dExpzH1EwzA1RxHAmBLMoNFq4Yms0kmQtrRiN179wVdopcA23r9snTPcF23eBAtDX8cE4x2+eu7VDXqeSM9sDTAD5M7JBzANo9xPE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=185.176.79.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.18.186.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4VNTBc3Ykwz6D9Bc; Mon, 22 Apr 2024 23:07:36 +0800 (CST) Received: from lhrpeml500005.china.huawei.com (unknown [7.191.163.240]) by mail.maildlp.com (Postfix) with ESMTPS id 653BA140B18; Mon, 22 Apr 2024 23:07:42 +0800 (CST) Received: from localhost (10.122.247.231) by lhrpeml500005.china.huawei.com (7.191.163.240) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Mon, 22 Apr 2024 16:07:41 +0100 Date: Mon, 22 Apr 2024 16:07:40 +0100 From: Jonathan Cameron To: Gregory Price CC: fan , , , , , , , , , , , Subject: Re: [PATCH v7 00/12] Enabling DCD emulation support in Qemu Message-ID: <20240422160740.0000625b@huawei.com> In-Reply-To: <20240422152316.00005e1a@Huawei.com> References: <20240418232902.583744-1-fan.ni@samsung.com> <20240422130448.000057ec@huawei.com> <20240422152316.00005e1a@Huawei.com> Organization: Huawei Technologies R&D (UK) Ltd. X-Mailer: Claws Mail 4.0.0 (GTK+ 3.24.29; x86_64-w64-mingw32) Precedence: bulk X-Mailing-List: linux-cxl@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-ClientProxiedBy: lhrpeml500004.china.huawei.com (7.191.163.9) To lhrpeml500005.china.huawei.com (7.191.163.240) On Mon, 22 Apr 2024 15:23:16 +0100 Jonathan Cameron wrote: > On Mon, 22 Apr 2024 13:04:48 +0100 > Jonathan Cameron wrote: > > > On Sat, 20 Apr 2024 16:35:46 -0400 > > Gregory Price wrote: > > > > > On Fri, Apr 19, 2024 at 11:43:14AM -0700, fan wrote: > > > > On Fri, Apr 19, 2024 at 02:24:36PM -0400, Gregory Price wrote: > > > > > > > > > > added review to all patches, will hopefully be able to add a Tested-by > > > > > tag early next week, along with a v1 RFC for MHD bit-tracking. > > > > > > > > > > We've been testing v5/v6 for a bit, so I expect as soon as we get the > > > > > MHD code ported over to v7 i'll ship a tested-by tag pretty quick. > > > > > > > > > > The super-set release will complicate a few things but this doesn't > > > > > look like a blocker on our end, just a change to how we track bits in a > > > > > shared bit/bytemap. > > > > > > > > > > > > > Hi Gregory, > > > > Thanks for reviewing the patches so quickly. > > > > > > > > No pressure, but look forward to your MHD work. :) > > > > > > > > Fan > > > > > > Starting to get into versioniong hell a bit, since the Niagara work was > > > based off of jonathan's branch and the mhd-dcd work needs some of the > > > extentions from that branch - while this branch is based on master. > > > > > > Probably we'll need to wait for a new cxl dated branch to try and sus > > > out the pain points before we push an RFC. I would not want to have > > > conflicting commits for something like this for example: > > > > > > https://lore.kernel.org/qemu-devel/20230901012914.226527-2-gregory.price@memverge.com/ > > > > > > We get merge conflicts here because this is behind that patch. So > > > pushing up an RFC in this state would be mostly useless to everyone > > > > Subtle hint noted ;) > > > > I'll build a fresh tree - any remaining rebases until QEMU 9.0 should be > > straight forward anyway. My ideal is that the NUMA GP series lands early > > in 9.1 cycle and this can go in parallel. I'd really like to > > get this in early if possible so we can start clearing some of the other > > stuff that ended up built on top of it! > > I've pushed to gitlab.com/jic23/qemu cxl-2024-04-22-draft > Its extremely lightly tested so far. > > To save time, I've temporarily dropped the fm-api DCD initiate > dynamic capacity add patch as that needs non trivial updates. > > I've not yet caught up with some other outstanding series, but > I will almost certainly put them on top of DCD. If anyone pulled in meantime... I failed to push down a fix from my working tree on top of this. Goes to show I shouldn't ignore patches simply named "Push down" :( Updated on same branch. Jonathan > > Jonathan > > > > > Jonathan > > > > > > > > ~Gregory > > > > > >