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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id A1C8EC282DE for ; Mon, 10 Mar 2025 14:19:58 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 0C63C280003; Mon, 10 Mar 2025 10:19:57 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 07669280001; Mon, 10 Mar 2025 10:19:57 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id E7FC4280003; Mon, 10 Mar 2025 10:19:56 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0012.hostedemail.com [216.40.44.12]) by kanga.kvack.org (Postfix) with ESMTP id CC6F1280001 for ; Mon, 10 Mar 2025 10:19:56 -0400 (EDT) Received: from smtpin13.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id 899E5810E3 for ; Mon, 10 Mar 2025 14:19:57 +0000 (UTC) X-FDA: 83205850434.13.82D1C62 Received: from mail-qv1-f44.google.com (mail-qv1-f44.google.com [209.85.219.44]) by imf14.hostedemail.com (Postfix) with ESMTP id 834C8100017 for ; Mon, 10 Mar 2025 14:19:55 +0000 (UTC) Authentication-Results: imf14.hostedemail.com; dkim=pass header.d=gourry.net header.s=google header.b=Zm8fXI7J; dmarc=none; spf=pass (imf14.hostedemail.com: domain of gourry@gourry.net designates 209.85.219.44 as permitted sender) smtp.mailfrom=gourry@gourry.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1741616395; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=ZFZo8zPwzqdWQJxqcj4qgZS2PvMRMOgjbkxudd5sQoM=; b=F2EhKuDNP9GVsgP2OYWnvgYgnx8jUz1QuWpyQGjGnXh5caWj5oEsmt10EeLUHXgkAzXXdi nnCgvZ7X1J+pqFfcO53IIk92Q8qWczTcDTIdlVm1bWXKL6WcfWBVZhVNYSDZSUybhkk042 BtQnsA/We3wf5NFlnDuk2s2Ssl4XFg8= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1741616395; a=rsa-sha256; cv=none; b=7TlDAzH/lnhIqcMyJMvBFGhf6KtiJXMcqSs2PYZvq+WR4JI+MBV77SqBH3jstollb0myQV iwGbnht4VzkmOLY9IA9C0f4/GfTY7xz7MZw5iVH9oW6/sftwqM6BXChcOqaZu1k7H7Y1g8 6bh5/JLrN9b9jVS8BJOsLRi98+lFwUY= ARC-Authentication-Results: i=1; imf14.hostedemail.com; dkim=pass header.d=gourry.net header.s=google header.b=Zm8fXI7J; dmarc=none; spf=pass (imf14.hostedemail.com: domain of gourry@gourry.net designates 209.85.219.44 as permitted sender) smtp.mailfrom=gourry@gourry.net Received: by mail-qv1-f44.google.com with SMTP id 6a1803df08f44-6e8f254b875so34287296d6.1 for ; Mon, 10 Mar 2025 07:19:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gourry.net; s=google; t=1741616394; x=1742221194; darn=kvack.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=ZFZo8zPwzqdWQJxqcj4qgZS2PvMRMOgjbkxudd5sQoM=; b=Zm8fXI7JtRiUnvsDrzTTnP+jEb2xAUmDRamyPqdf2/zAwoOziM5byTc8Nd2vQU3cXU T4vQRIACyuIrUkyLcIugBMlJBwpIqY5OlAM1bIUK3DUaa9StgCrmkOLlVRAPZMks75eF iSzdFQcB8Pcu44sZeSXy/aib4YOfaap3vb5CqJGziq/WUzjVcqyWOqmbm+iWFvnfxGIV IFVl3sD/Y0MamznH6kLCdx7ZP2MLD91OS0CwytGzqYYvxzgw5bGQkDJVlmW8eR8f431Z lwuxWbGR0P6U/xJmj0sXB3Ie0IQtb4idLvmNtyODNtCo8SYMDdMNoU/cD+UkExbp3wb4 kFZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741616394; x=1742221194; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=ZFZo8zPwzqdWQJxqcj4qgZS2PvMRMOgjbkxudd5sQoM=; b=kGcnRgvd9F4LD12n1mwl8FWJcNw9NXMjTnbcHay8dvNwjJW4RIW3ohSz6lqwNcN7H6 o/Rs8FAW6bkCjuCkuPT2WtwvhFjgf6x0TthIc6xzvts0HISlLS+QPmO5HcmZ8JOrIkfL 04FFhSPXLZcUV8U3lqlBgOTlrEhqEFUjMPI8wNQJznE8QWNCRKRBxBaGDuDp3q68ihhg g7ih50U+aUiYv7ZzxAFXlWfP7lK0KSWIpz9Qw6Roftyq+Gs46rSn/b66W7zeaE3vw9qF uMJtZeo9hqISGto2jdNjv/Jc5k7T2uiv1td/sm99rvRFe1/vn8dtJzOJ10CshnallJ62 EmFw== X-Forwarded-Encrypted: i=1; AJvYcCVUzH4hvy5SJwMcBUVbWjcfj98s/RC3R1DEQcNVYOCzJcTWuCRvvMOPfedwM5EaT9E4MxnGfXBsqQ==@kvack.org X-Gm-Message-State: AOJu0YwqrdGsOekDZhTyJpphXTQJtxFtZv/qPLP5A8tC1wiCKv5jkpX9 5pSTEbHqtQYp0Wp9aJ0OVisfXFO6Jz6egoZDkdeFVHDOcvTzz1xJFoT5eqpVSlc= X-Gm-Gg: ASbGncs4jnENkAR9vRig43NLdLkzMxxRu0XBOYAJk8hQmtjAJQyerS6yxp4qeXW39SC 9d0KFy5Gm+1gu3Db79IRKPHLz/8ukmLo8HQWpnJ6r8q+I+6vyLMhDn6hVO/o3vE1KynwAGQss31 wvCciUMN3D4XGrJgiACruz8KIFpKBQ9XUfRGHaGNGbu3S13+5X1DHK2tKGmu6r8+035J1pyoImD GLtxHHgdKTDgu9Np+/KNIALYVdrIn3cmflgCisZ2axd7Vs1/r/bVSTouzPlZkXktqbOJ7pQ9WEk 3Qa2uhCTnPACGW4nb5S7exY5jrb8iLlYXWLUMKTPoBt9A4eRf89gEdpTSkPTtUYbNvOQGDq4Zuo psXSOZks1cDSb4SyjQ1JyuxzGDYk= X-Google-Smtp-Source: AGHT+IGMJpR5j6TAtQib68qhOoxtIvV+O/W/i3w2HAax+rxX7rMLW1/8B437NQlpd0ajBQv1DIt3fQ== X-Received: by 2002:ad4:5d49:0:b0:6e8:fbb7:6764 with SMTP id 6a1803df08f44-6e9006ba2fbmr185600916d6.45.1741616393666; Mon, 10 Mar 2025 07:19:53 -0700 (PDT) Received: from gourry-fedora-PF4VCD3F (pool-173-79-56-208.washdc.fios.verizon.net. [173.79.56.208]) by smtp.gmail.com with ESMTPSA id 6a1803df08f44-6e8f707c4cbsm58904436d6.22.2025.03.10.07.19.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 10 Mar 2025 07:19:53 -0700 (PDT) Date: Mon, 10 Mar 2025 10:19:51 -0400 From: Gregory Price To: Yuquan Wang Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org, linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [LSF/MM] CXL Boot to Bash - Section 1: BIOS, EFI, and Early Boot Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspam-User: X-Rspamd-Queue-Id: 834C8100017 X-Rspamd-Server: rspam08 X-Stat-Signature: t1jy9zwyefd588nqs68o3f16k1raf91o X-HE-Tag: 1741616395-67225 X-HE-Meta: U2FsdGVkX1+AUFiIpi6Qw3Rhdl1HhJLyenm2xi2f9MWf4gZQ7GyZ0Ok0D9pMC6eIxDDmdMQCr29MqcQknUeQKtJh4+lt85SmcY21CwDO1cS8DoSc7BgyE9lFaPHJrYakdAp6tk0vdJeMYFbMuR/bwSP0eHawzViMYjbpnkEQaftwTDiTKPP9kX+w+meBWc4ijhTWpc6MzckzARBfKxuL8PCrtQds37ZWW/N8bCV1jp7pgStIZ9ci1xAcK/QoKJEUzuAufEn1CpVFLBQwAiKjXeimP6PB8HTVNVw8APQoiHl+3aFmsZLA/PhEN+ZiLffUso9gDL0RwlZSyJHgBrqhpiWfbihENa8zf9YPxiTe9Z8t59nrHzadMgmf5d2DWrkSF5acI9cmmRAF3FWXjQRoNtnVC82sOX5P8Gd04CQ3mcrXkBx+1YYiDlA32AdMFFg4hXP1vuU0T37706+4dTICCuIcn4mt5Vt1+E3wC9wmEWFDmEkoROU9I/W7s2iPYs0ZXmgSkZanFDVP6jGT5rWL1PYgUf6643EXvJKkDldLA6U/8dhBIeW73voHf2YdeIow2Y4Kmmt9G3hQ/aCG7dXW8lsMra+5XVsvKWl3Xm13Sf6tFaW4VgSlanVOzycSEQoCVbaXxtHyeK3H5eLyFp2QDn9LBT+rVtmm0v9/3gOUakUQ7FZqmB2npMikssLXCbbZf5Kx65oe3FjIcGXmnmOQUMOHXyJA3B9mEoruJEkChFtlG9ScV1noglcykQej9EFITdyikUN6uz3U+B9hLEeKiG5VHhGSKa67YYZPU0niqwd+o909AITyNZEEYYG54SyqhV5Gwp6qwBD3TLVa9gK6af7mjKMAN+Q11YzvTZ5gz25n1cC7KMBe6jhvOzgeWF7V4OJkWOJ2u8t2BAJrIIzryOKEQ/yHZsDNmW5RZy3ukDz+vM0SEmeBL78jvr0bfzcOc4rjg+VNJSArn/5yLNA UDV9ONum kEiY4mhnVHGokUbNXyQmQeN0wAvBPIBcgVxdIcjn4OslO4SLmxF1MjjBFfUqRjuiFNfF9IKKdOWPlzPZVnHQtquW0PCmEoRUkjVidZ8qiZBJ9/55bpcWdy92z0jaqNDiiCvPwG3krg1PKo5Af9cjXufNrZBPe9IG+bkvEyt0hPt5CrDPw1fYDkcLy2FZYGpx81hxZJWAE1NOYwK/qnUZ19jTE/WHVisOqTH2f6aiIHy/xmZsbijqOm5SDbk6934AsY4iDHE01x14EGVEsUE3y/smZHEvX2MKaTye9J9K7o07F4XoYEO0b3pUapaULEDdrbe2lG6BpRM1aba8= X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: On Mon, Mar 10, 2025 at 06:45:12PM +0800, Yuquan Wang wrote: > On Tue, Feb 04, 2025 at 09:17:09PM -0500, Gregory Price wrote: > > > > Platform / BIOS / EFI Configuraiton > > =================================== > > --------------------------------------- > > Step 1: BIOS-time hardware programming. > > --------------------------------------- > > > > I don't want to focus on platform specifics, so really all you need > > to know about this phase for the purpose of MM is that platforms may > > program the CXL device heirarchy and lock the configuration. > > > This question can be very naive, what's the meaning of 'MM' here? > Memory Management - linux/mm > And since I am not familiar with cxl bios configurations, based on my > understanding of its acpi results, there are roughly two configuration > schemes in my analysis: a) users should enter some configuration > information manually (like region base/size). b) bios could provide a > recommendatory configuration by device information. > The BIOS must produce ACPI tables to set aside system physical memory address space. *How* BIOS produces these ACPI tables (CEDT + SRAT vs CEDT only) dictates whether this configuration is static or dynamic. The devices will provide a CDAT (coherent device attribute table) used by BIOS to generate these ACPI tables. All of this dictates how linux configures its NUMA topology, programs CXL HDM decoders, and how it associates device physical memory with numa nodes and such. ~Gregory