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 40EC61FECAA; Fri, 4 Apr 2025 16:25:36 +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=1743783939; cv=none; b=shMUdlTw3CRyIo02HQSHMhbRIhfDrhg7bblT+Hlb8f9shy47tJciHwOJPkC05PM84buFw64K4WAqNVTK3fQe1/G5ouLjyzaSTnTB+AJPxwwMlK3n5MU4x4hUkCQb1XzkOcoHxAKg8pUWf14paZSN+TgpvR3k7SNlKBzWeY+e158= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1743783939; c=relaxed/simple; bh=5ECvxGs/0p2opqhSS/HdXbV+s0UOrmiu06g1flAn8LM=; h=Date:From:To:CC:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=K3JiDA7AGNuhiUAMOslPngmGAIOtVMKf1w59pBGl+XEGtu1oIiHSDZq7pkaAkF42io18HnTD0uUlU6tyKrkNE52H/fmnOATXfkZ2Ts+RrY9A7dh5RsDtkg84zejl6f2AvPuuhcj31PVfAMN1tCln0OodjE1nhIFg4tdlj2SLVNU= 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 4ZTkQ90nLqz6K9Gs; Sat, 5 Apr 2025 00:21:53 +0800 (CST) Received: from frapeml500008.china.huawei.com (unknown [7.182.85.71]) by mail.maildlp.com (Postfix) with ESMTPS id 19C051402C7; Sat, 5 Apr 2025 00:25:34 +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; Fri, 4 Apr 2025 18:25:33 +0200 Date: Fri, 4 Apr 2025 17:25:32 +0100 From: Jonathan Cameron To: CC: , , , , , , , , , Alejandro Lucero , Ben Cheatham Subject: Re: [PATCH v12 09/23] cxl: prepare memdev creation for type2 Message-ID: <20250404172532.00001e04@huawei.com> In-Reply-To: <20250331144555.1947819-10-alejandro.lucero-palau@amd.com> References: <20250331144555.1947819-1-alejandro.lucero-palau@amd.com> <20250331144555.1947819-10-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: lhrpeml500005.china.huawei.com (7.191.163.240) To frapeml500008.china.huawei.com (7.182.85.71) On Mon, 31 Mar 2025 15:45:41 +0100 alejandro.lucero-palau@amd.com wrote: > From: Alejandro Lucero > > Current cxl core is relying on a CXL_DEVTYPE_CLASSMEM type device when > creating a memdev leading to problems when obtaining cxl_memdev_state > references from a CXL_DEVTYPE_DEVMEM type. > > Modify check for obtaining cxl_memdev_state adding CXL_DEVTYPE_DEVMEM > support. > > Make devm_cxl_add_memdev accesible from a accel driver. > > Signed-off-by: Alejandro Lucero > Reviewed-by: Ben Cheatham Reviewed-by: Jonathan Cameron