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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id 2F07CC001DB for ; Fri, 11 Aug 2023 13:55:24 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qUSbl-0004bN-K5; Fri, 11 Aug 2023 09:55:18 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qUSbj-0004b5-C0 for qemu-devel@nongnu.org; Fri, 11 Aug 2023 09:55:15 -0400 Received: from frasgout.his.huawei.com ([185.176.79.56]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qUSbh-0003cZ-4a for qemu-devel@nongnu.org; Fri, 11 Aug 2023 09:55:15 -0400 Received: from lhrpeml500005.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4RMlfM5ppYz6HJTd; Fri, 11 Aug 2023 21:54:51 +0800 (CST) Received: from localhost (10.202.227.76) by lhrpeml500005.china.huawei.com (7.191.163.240) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Fri, 11 Aug 2023 14:54:59 +0100 Date: Fri, 11 Aug 2023 14:54:58 +0100 To: Maverickk 78 CC: Jonathan Cameron via , Subject: Re: CXL volatile memory is not listed Message-ID: <20230811145458.000029c7@Huawei.com> In-Reply-To: References: <20230810113512.00000516@Huawei.com> Organization: Huawei Technologies Research and Development (UK) Ltd. X-Mailer: Claws Mail 4.1.0 (GTK 3.24.33; x86_64-w64-mingw32) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.202.227.76] X-ClientProxiedBy: lhrpeml100001.china.huawei.com (7.191.160.183) To lhrpeml500005.china.huawei.com (7.191.163.240) 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: -41 X-Spam_score: -4.2 X-Spam_bar: ---- X-Spam_report: (-4.2 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-to: Jonathan Cameron From: Jonathan Cameron via Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org On Fri, 11 Aug 2023 08:04:26 +0530 Maverickk 78 wrote: > Jonathan, > > > More generally for the flow that would bring the memory up as system ram > > you would typically need the bios to have done the CXL enumeration or > > a bunch of scripts in the kernel to have done it. In general it can't > > be fully automated, because there are policy decisions to make on things like > > interleaving. > > BIOS CXL enumeration? is CEDT not enough? or BIOS further needs to > create an entry > in the e820 table? On intel platforms 'maybe' :) I know how it works on those that just use the nice standard EFI tables - less familiar with the e820 stuff :) CEDT says where to find the the various bits of system related CXL stuff. Nothing in there on the configuration that should be used such as interleaving as that depends on what the administrator wants. Or on what the BIOS has decided the users should have. > > > > > I'm not aware of any open source BIOSs that do it yet. So you have > > to rely on the same kernel paths as for persistent memory - manual configuration > > etc in the kernel. > > > Manual works with "cxl create regiton" :) Great. Jonathan > > On Thu, 10 Aug 2023 at 16:05, Jonathan Cameron > wrote: > > > > On Wed, 9 Aug 2023 04:21:47 +0530 > > Maverickk 78 wrote: > > > > > Hello, > > > > > > I am running qemu-system-x86_64 > > > > > > qemu-system-x86_64 --version > > > QEMU emulator version 8.0.92 (v8.1.0-rc2-80-g0450cf0897) > > > > > +Cc linux-cxl as the answer is more todo with linux than qemu. > > > > > qemu-system-x86_64 \ > > > -m 2G,slots=4,maxmem=4G \ > > > -smp 4 \ > > > -machine type=q35,accel=kvm,cxl=on \ > > > -enable-kvm \ > > > -nographic \ > > > -device pxb-cxl,id=cxl.0,bus=pcie.0,bus_nr=52 \ > > > -device cxl-rp,id=rp0,bus=cxl.0,chassis=0,port=0,slot=0 \ > > > -object memory-backend-file,id=mem0,mem-path=/tmp/mem0,size=1G,share=true \ > > > -device cxl-type3,bus=rp0,volatile-memdev=mem0,id=cxl-mem0 \ > > > -M cxl-fmw.0.targets.0=cxl.0,cxl-fmw.0.size=1G > > > > There are some problems upstream at the moment (probably not cxl related but > > I'm digging). So today I can't boot an x86 machine. (goody) > > > > > > More generally for the flow that would bring the memory up as system ram > > you would typically need the bios to have done the CXL enumeration or > > a bunch of scripts in the kernel to have done it. In general it can't > > be fully automated, because there are policy decisions to make on things like > > interleaving. > > > > I'm not aware of any open source BIOSs that do it yet. So you have > > to rely on the same kernel paths as for persistent memory - manual configuration > > etc in the kernel. > > > > There is support in ndctl for those enabling flows, so I'd look there > > for more information > > > > Jonathan > > > > > > > > > > > > > I was expecting the CXL memory to be listed in "System Ram", the lsmem > > > shows only 2G memory which is System RAM, it's not listing the CXL > > > memory. > > > > > > Do I need to pass any particular parameter in the kernel command line? > > > > > > Is there any documentation available? I followed the inputs provided in > > > > > > https://lore.kernel.org/linux-mm/Y+CSOeHVLKudN0A6@kroah.com/T/ > > > > > > Is there any documentation/blog listed? > >