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 425EB298CD7; Fri, 27 Jun 2025 09:13:49 +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=1751015631; cv=none; b=YCly6GbnJpehQSRnpBuacRUBEQzNwCF7u4wF98YpOH3OBm2WB2vQhCSwo+T8qq3DIcpYPsH0b+hcM8keNkFBDgeh+S1Yv3a7jzGiq3npg+ex6BU7N6l6+XrDDBtUNexQ40OU0Y3eBF1a5N5Bj0xUWVuepcqRQeWriEBuU5WX+Ik= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1751015631; c=relaxed/simple; bh=AQcoq2qZxJEuezCfVgUpMT9Nvr0nzks5AnC9mJN0jmA=; h=Date:From:To:CC:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=Sq02XPkjIZdDd2Q31fnRD83jTZaqehNLXmkmzVC4hAUDizhcN91hixiF72KFK8642IjmRHZB0whusVx8fkbR5zcIX3HclHNw3+MqF1JrQ8UUnImH0fzxpqn0B21Qv1wn2omGwso08mgqKszflS+2/fo0Orn1NXH73Ie/Tj0Kyyg= 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.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4bT8tQ2TP6z6L5LH; Fri, 27 Jun 2025 17:11:10 +0800 (CST) Received: from frapeml500008.china.huawei.com (unknown [7.182.85.71]) by mail.maildlp.com (Postfix) with ESMTPS id 58D3D140417; Fri, 27 Jun 2025 17:13:48 +0800 (CST) Received: from localhost (10.48.153.213) by frapeml500008.china.huawei.com (7.182.85.71) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Fri, 27 Jun 2025 11:13:47 +0200 Date: Fri, 27 Jun 2025 10:13:45 +0100 From: Jonathan Cameron To: CC: , , , , , , , , , Alejandro Lucero , Zhi Wang , Ben Cheatham Subject: Re: [PATCH v17 16/22] cxl/region: Factor out interleave ways setup Message-ID: <20250627101345.00002524@huawei.com> In-Reply-To: <20250624141355.269056-17-alejandro.lucero-palau@amd.com> References: <20250624141355.269056-1-alejandro.lucero-palau@amd.com> <20250624141355.269056-17-alejandro.lucero-palau@amd.com> X-Mailer: Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32) Precedence: bulk X-Mailing-List: netdev@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: lhrpeml100012.china.huawei.com (7.191.174.184) To frapeml500008.china.huawei.com (7.182.85.71) On Tue, 24 Jun 2025 15:13:49 +0100 wrote: > From: Alejandro Lucero > > Region creation based on Type3 devices is triggered from user space > allowing memory combination through interleaving. > > In preparation for kernel driven region creation, that is Type2 drivers > triggering region creation backed with its advertised CXL memory, factor > out a common helper from the user-sysfs region setup for interleave ways. > > Signed-off-by: Alejandro Lucero > Reviewed-by: Zhi Wang > Reviewed-by: Dave Jiang > Reviewed-by: Jonathan Cameron > Reviewed-by: Ben Cheatham As a heads up, this code changes a fair bit in Dan's ACQUIRE() series that may well land before this. Dave can ask for whatever resolution he wants when we get to that stage!