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 737111AF0B7; Tue, 15 Apr 2025 13:55:24 +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=1744725327; cv=none; b=sXs+yRPHS7VD2STrD/vewucNDvHWjr+B2v6Mzcawtl/VnYB1i91rdW7qjd+VT4YegjY/8ape8YHh9y0ePbwjGcvlNoglygATcMb1jgma3XE3UaSs8lcdK5cSxGAG7AObgvVzwhrHy/vEUgB1AOn48asQC7fRDBY4OQIXQv6wfOQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1744725327; c=relaxed/simple; bh=OgXt3YTFuCikn/Ukxq7Nr5RG+ywV4ML6/dJuCSKeS+I=; h=Date:From:To:CC:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=WsZNVA5xnvpuBMDMUfWXj5Qt9UkiF7cmfvfIBoR4L2+qed4Msw01oNKvCiLGSCzxyVkga/CBIJgZyW/P+bphNVZUajnXV/cNvhHT4riH52Qb6GIveUEpeMkTc1iU0ER7AbY2LMvR/uVlsUnsAa8xRIDRmlcJ5nTCDTbnRxsPdAY= 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.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4ZcQYB3xmhz6K9YH; Tue, 15 Apr 2025 21:51:10 +0800 (CST) Received: from frapeml500008.china.huawei.com (unknown [7.182.85.71]) by mail.maildlp.com (Postfix) with ESMTPS id 07E4E14050D; Tue, 15 Apr 2025 21:55:22 +0800 (CST) Received: from localhost (10.203.177.66) 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; Tue, 15 Apr 2025 15:55:21 +0200 Date: Tue, 15 Apr 2025 14:55:19 +0100 From: Jonathan Cameron To: CC: , , , , , , , , , Alejandro Lucero Subject: Re: [PATCH v13 18/22] cxl: allow region creation by type2 drivers Message-ID: <20250415145519.00006f96@huawei.com> In-Reply-To: <20250414151336.3852990-19-alejandro.lucero-palau@amd.com> References: <20250414151336.3852990-1-alejandro.lucero-palau@amd.com> <20250414151336.3852990-19-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: lhrpeml100002.china.huawei.com (7.191.160.241) To frapeml500008.china.huawei.com (7.182.85.71) On Mon, 14 Apr 2025 16:13:32 +0100 wrote: > From: Alejandro Lucero > > Creating a CXL region requires userspace intervention through the cxl > sysfs files. Type2 support should allow accelerator drivers to create > such cxl region from kernel code. > > Adding that functionality and integrating it with current support for > memory expanders. > > Based on https://lore.kernel.org/linux-cxl/168592159835.1948938.1647215579839222774.stgit@dwillia2-xfh.jf.intel.com/ > > Signed-off-by: Alejandro Lucero Reviewed-by: Jonathan Cameron