From nobody Tue Feb 10 00:58:45 2026 Received: from mail-qt1-f175.google.com (mail-qt1-f175.google.com [209.85.160.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C01E02951C9 for ; Mon, 12 May 2025 16:22:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.160.175 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1747066933; cv=none; b=Fex2j79YunO9qiLBquooih2WWocuodHXlBvakZceVPQSFdr22/jDFRWVGbMrzzX/P/pgZezzEsL7d127/SBntH4SKUztlhCLlL8BZrRnxKxFPcvZjZBaQPKSzSyTiapTJvC8lKMHh/xDxmC8BNyn0D25sX9A/b6G6nAAihsja3Q= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1747066933; c=relaxed/simple; bh=A6Mies9hUhfrCMV4P20s2B5vlbK+fHovsvjiHQdVYCE=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=cJ/mY6/4c7cB9Nu+RgO+66y9j4KwhdgCHr2cAu/3+RLT8kbCk7xzV0rCbBnCeEjP4CuEkSPbL2Qj724x7av2hlcqZQmaq17XOwJnNJdF6shUMqGBReN9k8nNkMA5v/I6NIjBfh+lYWC2/EC4nNB5ny4lrso/7Eo3jPVuJakbq5g= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=gourry.net; spf=pass smtp.mailfrom=gourry.net; dkim=pass (2048-bit key) header.d=gourry.net header.i=@gourry.net header.b=WHZUZlq+; arc=none smtp.client-ip=209.85.160.175 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=gourry.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gourry.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gourry.net header.i=@gourry.net header.b="WHZUZlq+" Received: by mail-qt1-f175.google.com with SMTP id d75a77b69052e-476f4e9cf92so38856911cf.3 for ; Mon, 12 May 2025 09:22:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gourry.net; s=google; t=1747066928; x=1747671728; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=Ci6f1K89LsZ+DF6ZgFYZsgSAOzS56KH3yJTL4ef3rh0=; b=WHZUZlq+1rTSFZZPWvR1HjwnFQqgSG3OpqUrEt2xKc150AA+9Qj33nRvvGMLLg44YZ TM5csfL4HO9k/iW3wBUT5Ka1omzgO5kVKmNMRqYFDxpRWAnkiNYXigersQl8JmrktOAZ gdGmyMU5tmijl/Ov+l6i0mIydMzZt3r1u0LQPer9wV/QTGT1N3YXHnVmU8c9hbojzHAN P9cwMQ86r0a9728uYlFP4LHAARZRACZCQZxd4fDzVAFfYJH9tUy6y5WATEIM5i/l2nVS Zcy2JDgiHMGnWusOVWtQt/h/j1XH22cfgwbcRDboGZh0IURpUimWtN2QgFUPZerIukcp a5JA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1747066928; x=1747671728; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Ci6f1K89LsZ+DF6ZgFYZsgSAOzS56KH3yJTL4ef3rh0=; b=LFxQHlkNAZ2GBacNvfFiHo0nD48+ryALBoUWABx71fdrDpy2NlVBnfFmViIHrzvkR1 q5T4gvME8lIK7D7ifWxBdNoglj0I2hFSd1i/fAxNehaJcFzpihNlvTAvh0v/UDdXURiC DegKKU7MISOqVpFeXv5R2ILLXZFHsWTfpu7YDFQiUl74J3y4yrjTavAVCGhlJ/JdW18p vrMX9TVhxrtlaZX03qsoC3goHWRb3HC362VkpG8GutwMRlI3jzhH1ilxaiIx4VD12dN3 cvIN6TN5Bi1dBLedMYSP7YltTDHghOqb/4naWDgJJolqtpTOpsRNBmv9Lim7RuyTxZdG 8cVQ== X-Forwarded-Encrypted: i=1; AJvYcCV7fgonqg0yw0VLwzaMK/fGiLX1p/ICxzvuJjNptc8B2rs9qeVIUzOzw/6atJWLxQdP5BC2zoYUvzWRtE0=@vger.kernel.org X-Gm-Message-State: AOJu0YxLyy9FZNdFPReRqmk6Np9UfyXISiehmFG5/Y2O+eh3nzJk1jdK m31vQoQ4euBvDDt2Ts5AxQqkKQ81zInOnGbPsqnij8t0jAHckuxcRh1/gNotza1gK4VOGsGHTg9 G X-Gm-Gg: ASbGncs7rWtRAsje0khhpHhAuHaPIO390Eqt8Yehav40oTaP/RLikq+GOG3uRtQ79CF 3uqWTjyN2NFWUmIBtxJxvtqLvffupqvpKbk4pyDSGU90UK0icFGynaWOeKKenZyBG2Zw8dFrsn+ 0xk2Ku6bUmktIvPakA5fLI8N0FQGqPf2N/f0PrNHVMwOpKdX2sVp4Lbfaoe9s4QNV8ZUUdI9+vM cojlKuJCRfVpFuSCpeWCn8s5P4YujPVN0sNkzKivwAj7eyyRZuw2z9ZrAfDFS9BBTxkgt8Ij3Kr UHbB3lgIFpDDutwBqZ6pcWTNjc1YkduboSZ2/c1lzDB6UhDe0qK9Jj9cdcIEhGpVd1LHe7g/6Wt ENqXAtCX75Q+kP0VzV7pM+tGJt0Jwa9gT39Lj6VbjCVd6LoM= X-Google-Smtp-Source: AGHT+IE6kifyyq68JXmdCyyHqCef0H7CrWN95iUQ8mmLv4UnZnRRmN3QUvUDR9Mvy0G1oQqLngMKog== X-Received: by 2002:a05:622a:1984:b0:476:ac73:c3f3 with SMTP id d75a77b69052e-494527162demr247105181cf.1.1747066928404; Mon, 12 May 2025 09:22:08 -0700 (PDT) Received: from gourry-fedora-PF4VCD3F.lan (pool-96-255-20-42.washdc.ftas.verizon.net. [96.255.20.42]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-49452583961sm52461791cf.58.2025.05.12.09.22.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 12 May 2025 09:22:08 -0700 (PDT) From: Gregory Price To: linux-cxl@vger.kernel.org Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-team@meta.com, dave@stgolabs.net, jonathan.cameron@huawei.com, dave.jiang@intel.com, alison.schofield@intel.com, vishal.l.verma@intel.com, ira.weiny@intel.com, dan.j.williams@intel.com, corbet@lwn.net, Bagas Sanjaya Subject: [PATCH v3 17/17] cxl: docs - add self-referencing cross-links Date: Mon, 12 May 2025 12:21:34 -0400 Message-ID: <20250512162134.3596150-18-gourry@gourry.net> X-Mailer: git-send-email 2.49.0 In-Reply-To: <20250512162134.3596150-1-gourry@gourry.net> References: <20250512162134.3596150-1-gourry@gourry.net> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Add some crosslinks between pages in the CXL docs - mostly to the ACPI tables. Suggested-by: Bagas Sanjaya Signed-off-by: Gregory Price --- .../driver-api/cxl/devices/device-types.rst | 2 +- .../cxl/linux/access-coordinates.rst | 7 ++-- .../driver-api/cxl/linux/cxl-driver.rst | 35 ++++++++++--------- .../driver-api/cxl/linux/early-boot.rst | 32 ++++++++++------- .../driver-api/cxl/platform/bios-and-efi.rst | 12 +++---- .../example-configurations/flexible.rst | 10 +++--- .../example-configurations/hb-interleave.rst | 10 +++--- .../multi-dev-per-hb.rst | 10 +++--- .../example-configurations/one-dev-per-hb.rst | 10 +++--- 9 files changed, 69 insertions(+), 59 deletions(-) diff --git a/Documentation/driver-api/cxl/devices/device-types.rst b/Docume= ntation/driver-api/cxl/devices/device-types.rst index c70564cf0be3..f5e4330c1cfe 100644 --- a/Documentation/driver-api/cxl/devices/device-types.rst +++ b/Documentation/driver-api/cxl/devices/device-types.rst @@ -115,7 +115,7 @@ A Multi-Headed Single-Logical Device (MHSLD) exposes a = single logical device to multiple heads which may be connected to one or more discrete hosts. An example of this would be a simple memory-pool which may be statically configured (prior to boot) to expose portions of its memory -to Linux via the CEDT ACPI table. +to Linux via :doc:`CEDT <../platform/acpi/cedt>`. =20 MHMLD ~~~~~ diff --git a/Documentation/driver-api/cxl/linux/access-coordinates.rst b/Do= cumentation/driver-api/cxl/linux/access-coordinates.rst index e408ecbc4038..71024fa0f561 100644 --- a/Documentation/driver-api/cxl/linux/access-coordinates.rst +++ b/Documentation/driver-api/cxl/linux/access-coordinates.rst @@ -24,7 +24,7 @@ asymmetry in properties does not happen and all paths to = EPs are equal. =20 There can be multiple switches under an RP. There can be multiple RPs under a CXL Host Bridge (HB). There can be multiple HBs under a CXL Fixed Memory -Window Structure (CFMWS). +Window Structure (CFMWS) in the :doc:`CEDT <../platform/acpi/cedt>`. =20 An example hierarchy:: =20 @@ -83,8 +83,9 @@ also the index for the resulting xarray. =20 The next step is to take the min() of the per host bridge bandwidth and the bandwidth from the Generic Port (GP). The bandwidths for the GP are retrie= ved -via ACPI tables SRAT/HMAT. The minimum bandwidth are aggregated under the = same -ACPI0017 device to form a new xarray. +via ACPI tables (:doc:`SRAT <../platform/acpi/srat>` and +:doc:`HMAT <../platform/acpi/hmat>`). The minimum bandwidth are aggregated +under the same ACPI0017 device to form a new xarray. =20 Finally, the cxl_region_update_bandwidth() is called and the aggregated bandwidth from all the members of the last xarray is updated for the diff --git a/Documentation/driver-api/cxl/linux/cxl-driver.rst b/Documentat= ion/driver-api/cxl/linux/cxl-driver.rst index cf6b397abdb1..9759e90c3cf1 100644 --- a/Documentation/driver-api/cxl/linux/cxl-driver.rst +++ b/Documentation/driver-api/cxl/linux/cxl-driver.rst @@ -77,11 +77,11 @@ Root Object` Device Class is found. =20 The Root contains links to: =20 -* `Host Bridge Ports` defined by ACPI CEDT CHBS. +* `Host Bridge Ports` defined by CHBS in the :doc:`CEDT<../platform/acpi/c= edt>` =20 * `Downstream Ports` typically connected to `Host Bridge Ports`. =20 -* `Root Decoders` defined by ACPI CEDT CFMWS. +* `Root Decoders` defined by CFMWS the :doc:`CEDT<../platform/acpi/cedt>` =20 :: =20 @@ -150,9 +150,8 @@ An `endpoint` is a terminal port in the fabric. This i= s a `logical device`, and may be one of many `logical devices` presented by a memory device. It is still considered a type of `port` in the fabric. =20 -An `endpoint` contains `endpoint decoders` available for use and the -*Coherent Device Attribute Table* (CDAT) used to describe the capabilities -of the device. :: +An `endpoint` contains `endpoint decoders` and the device's Coherent Device +Attribute Table (which describes the device's capabilities). :: =20 # ls /sys/bus/cxl/devices/endpoint5 CDAT decoders_committed modalias uevent @@ -247,17 +246,18 @@ parameter. Root Decoder ~~~~~~~~~~~~ A `Root Decoder` is logical construct of the physical address and interlea= ve -configurations present in the ACPI CEDT CFMWS. Linux presents this inform= ation -as a decoder present in the `CXL Root`. We consider this a `Root Decoder`, -though technically it exists on the boundary of the CXL specification and -platform-specific CXL root implementations. +configurations present in the CFMWS field of the :doc:`CEDT +<../platform/acpi/cedt>`. +Linux presents this information as a decoder present in the `CXL Root`. We +consider this a `Root Decoder`, though technically it exists on the bounda= ry +of the CXL specification and platform-specific CXL root implementations. =20 Linux considers these logical decoders a type of `Routing Decoder`, and is= the first decoder in the CXL fabric to receive a memory access from the platfo= rm's memory controllers. =20 `Root Decoders` are created during :code:`cxl_acpi_probe`. One root decod= er -is created per CFMWS entry in the ACPI CEDT. +is created per CFMWS entry in the :doc:`CEDT <../platform/acpi/cedt>`. =20 The :code:`target_list` parameter is filled by the CFMWS target fields. Ta= rgets of a root decoder are `Host Bridges`, which means interleave done at the r= oot @@ -267,9 +267,11 @@ Only root decoders are capable of `Inter-Host-Bridge I= nterleave`. =20 Such interleaves must be configured by the platform and described in the A= CPI CEDT CFMWS, as the target CXL host bridge UIDs in the CFMWS must match the= CXL -host bridge UIDs in the ACPI CEDT CHBS and ACPI DSDT. +host bridge UIDs in the CHBS field of the :doc:`CEDT +<../platform/acpi/cedt>` and the UID field of CXL Host Bridges defined in +the :doc:`DSDT <../platform/acpi/dsdt>`. =20 -Interleave settings in a rootdecoder describe how to interleave accesses a= mong +Interleave settings in a root decoder describe how to interleave accesses = among the *immediate downstream targets*, not the entire interleave set. =20 The memory range described in the root decoder is used to @@ -531,10 +533,11 @@ granularity configuration. =20 At Root ~~~~~~~ -Root decoder interleave is defined by the ACPI CEDT CFMWS. The CEDT -may actually define multiple CFMWS configurations to describe the same -physical capacity - with the intent to allow users to decide at runtime -whether to online memory as interleaved or non-interleaved. :: +Root decoder interleave is defined by CFMWS field of the :doc:`CEDT +<../platform/acpi/cedt>`. The CEDT may actually define multiple CFMWS +configurations to describe the same physical capacity, with the intent to = allow +users to decide at runtime whether to online memory as interleaved or +non-interleaved. :: =20 Subtable Type : 01 [CXL Fixed Memory Window Structure] Window base address : 0000000100000000 diff --git a/Documentation/driver-api/cxl/linux/early-boot.rst b/Documentat= ion/driver-api/cxl/linux/early-boot.rst index 8c1c497bc772..a7fc6fc85fbe 100644 --- a/Documentation/driver-api/cxl/linux/early-boot.rst +++ b/Documentation/driver-api/cxl/linux/early-boot.rst @@ -12,8 +12,9 @@ read EFI and ACPI information throughout this process to = configure logical representations of the devices. =20 During Linux Early Boot stage (functions in the kernel that have the __init -decorator), the system takes the resources created by EFI/BIOS (ACPI table= s) -and turns them into resources that the kernel can consume. +decorator), the system takes the resources created by EFI/BIOS +(:doc:`ACPI tables <../platform/acpi>`) and turns them into resources that= the +kernel can consume. =20 =20 BIOS, Build and Boot Options @@ -70,13 +71,14 @@ significant impact performance depending on the memory = capacity of the system. NUMA Node Reservation =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 -Linux refers to the proximity domains (:code:`PXM`) defined in the SRAT to -create NUMA nodes in :code:`acpi_numa_init`. Typically, there is a 1:1 rel= ation -between :code:`PXM` and NUMA node IDs. +Linux refers to the proximity domains (:code:`PXM`) defined in the :doc:`S= RAT +<../platform/acpi/srat>` to create NUMA nodes in :code:`acpi_numa_init`. +Typically, there is a 1:1 relation between :code:`PXM` and NUMA node IDs. =20 -SRAT is the only ACPI defined way of defining Proximity Domains. Linux cho= oses -to, at most, map those 1:1 with NUMA nodes. CEDT adds a description of SPA -ranges which Linux may wish to map to one or more NUMA nodes. +The SRAT is the only ACPI defined way of defining Proximity Domains. Linux +chooses to, at most, map those 1:1 with NUMA nodes. +:doc:`CEDT <../platform/acpi/cedt>` adds a description of SPA ranges which +Linux may map to one or more NUMA nodes. =20 If there are CXL ranges in the CFMWS but not in SRAT, then a fake :code:`P= XM` is created (as of v6.15). In the future, Linux may reject CFMWS not descri= bed @@ -89,7 +91,8 @@ data for Linux to identify NUMA nodes their associated me= mory regions. =20 The relevant code exists in: :code:`linux/drivers/acpi/numa/srat.c`. =20 -See the Example Platform Configurations section for more information. +See :doc:`Example Platform Configurations <../platform/example-configs>` +for more info. =20 Memory Tiers Creation =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D @@ -108,10 +111,13 @@ Tier membership can be inspected in :: /sys/devices/virtual/memory_tiering/memory_tierN/nodelist 0-1 =20 -If nodes are grouped which have clear difference in performance, check the= HMAT -and CDAT information for the CXL nodes. All nodes default to the DRAM tie= r, -unless HMAT/CDAT information is reported to the memory_tier component via -`access_coordinates`. +If nodes are grouped which have clear difference in performance, check the +:doc:`HMAT <../platform/acpi/hmat>` and CDAT information for the CXL nodes= . All +nodes default to the DRAM tier, unless HMAT/CDAT information is reported t= o the +memory_tier component via `access_coordinates`. + +For more, see :doc:`CXL access coordinates documentation +<../linux/access-coordinates>`. =20 Contiguous Memory Allocation =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D diff --git a/Documentation/driver-api/cxl/platform/bios-and-efi.rst b/Docum= entation/driver-api/cxl/platform/bios-and-efi.rst index 552a83992bcc..645322632cc9 100644 --- a/Documentation/driver-api/cxl/platform/bios-and-efi.rst +++ b/Documentation/driver-api/cxl/platform/bios-and-efi.rst @@ -22,7 +22,7 @@ At a high level, this is what occurs during this phase of= configuration. =20 Much of what this section is concerned with is ACPI Table production and static memory map configuration. More detail on these tables can be found -under Platform Configuration -> ACPI Table Reference. +at :doc:`ACPI Tables `. =20 .. note:: Platform Vendors should read carefully, as this sections has recommenda= tions @@ -175,9 +175,9 @@ to implement driver support for your platform. =20 Interleave and Configuration Flexibility ---------------------------------------- -If providing cross-host-bridge interleave, a CFMWS entry in the CEDT must = be -presented with target host-bridges for the interleaved device sets (there = may -be multiple behind each host bridge). +If providing cross-host-bridge interleave, a CFMWS entry in the :doc:`CEDT +` must be presented with target host-bridges for the interleaved +device sets (there may be multiple behind each host bridge). =20 If providing intra-host-bridge interleaving, only 1 CFMWS entry in the CED= T is required for that host bridge - if it covers the entire capacity of the de= vices @@ -193,8 +193,8 @@ different purposes. For example, you may want to consi= der adding: =20 A platform may choose to add all of these, or change the mode based on a B= IOS setting. For each CFMWS entry, Linux expects descriptions of the described -memory regions in the SRAT to determine the number of NUMA nodes it should -reserve during early boot / init. +memory regions in the :doc:`SRAT ` to determine the number of +NUMA nodes it should reserve during early boot / init. =20 As of v6.14, Linux will create a NUMA node for each CEDT CFMWS entry, even= if a matching SRAT entry does not exist; however, this is not guaranteed in t= he diff --git a/Documentation/driver-api/cxl/platform/example-configurations/f= lexible.rst b/Documentation/driver-api/cxl/platform/example-configurations/= flexible.rst index e39daba65fa0..dab704b6fcc2 100644 --- a/Documentation/driver-api/cxl/platform/example-configurations/flexible= .rst +++ b/Documentation/driver-api/cxl/platform/example-configurations/flexible= .rst @@ -18,7 +18,7 @@ Things to note: * This SRAT describes one node for each of the above CFMWS. * The HMAT describes performance for each node in the SRAT. =20 -CEDT :: +:doc:`CEDT <../acpi/cedt>`:: =20 Subtable Type : 00 [CXL Host Bridge Structure] Reserved : 00 @@ -137,7 +137,7 @@ CEDT :: QtgId : 0001 First Target : 00000006 =20 -SRAT :: +:doc:`SRAT <../acpi/srat>`:: =20 Subtable Type : 01 [Memory Affinity] Length : 28 @@ -223,7 +223,7 @@ SRAT :: Hot Pluggable : 1 Non-Volatile : 0 =20 -HMAT :: +:doc:`HMAT <../acpi/hmat>`:: =20 Structure Type : 0001 [SLLBI] Data Type : 00 [Latency] @@ -263,7 +263,7 @@ HMAT :: Entry : 0100 Entry : 0100 =20 -SLIT :: +:doc:`SLIT <../acpi/slit>`:: =20 Signature : "SLIT" [System Locality Information Table] Localities : 0000000000000003 @@ -276,7 +276,7 @@ SLIT :: Locality 6 : FF FF FF FF FF FF 0A FF Locality 7 : FF FF FF FF FF FF FF 0A =20 -DSDT :: +:doc:`DSDT <../acpi/dsdt>`:: =20 Scope (_SB) { diff --git a/Documentation/driver-api/cxl/platform/example-configurations/h= b-interleave.rst b/Documentation/driver-api/cxl/platform/example-configurat= ions/hb-interleave.rst index ce07e6162f26..c474dcf09fb0 100644 --- a/Documentation/driver-api/cxl/platform/example-configurations/hb-inter= leave.rst +++ b/Documentation/driver-api/cxl/platform/example-configurations/hb-inter= leave.rst @@ -13,7 +13,7 @@ Things to note: * This SRAT describes one node for both host bridges. * The HMAT describes a single node's performance. =20 -CEDT :: +:doc:`CEDT <../acpi/cedt>`:: =20 Subtable Type : 00 [CXL Host Bridge Structure] Reserved : 00 @@ -48,7 +48,7 @@ CEDT :: First Target : 00000007 Second Target : 00000006 =20 -SRAT :: +:doc:`SRAT <../acpi/srat>`:: =20 Subtable Type : 01 [Memory Affinity] Length : 28 @@ -62,7 +62,7 @@ SRAT :: Hot Pluggable : 1 Non-Volatile : 0 =20 -HMAT :: +:doc:`HMAT <../acpi/hmat>`:: =20 Structure Type : 0001 [SLLBI] Data Type : 00 [Latency] @@ -80,14 +80,14 @@ HMAT :: Entry : 1200 Entry : 0400 =20 -SLIT :: +:doc:`SLIT <../acpi/slit>`:: =20 Signature : "SLIT" [System Locality Information Table] Localities : 0000000000000003 Locality 0 : 10 20 Locality 1 : FF 0A =20 -DSDT :: +:doc:`DSDT <../acpi/dsdt>`:: =20 Scope (_SB) { diff --git a/Documentation/driver-api/cxl/platform/example-configurations/m= ulti-dev-per-hb.rst b/Documentation/driver-api/cxl/platform/example-configu= rations/multi-dev-per-hb.rst index 6adf7c639490..a7854a79dbbd 100644 --- a/Documentation/driver-api/cxl/platform/example-configurations/multi-de= v-per-hb.rst +++ b/Documentation/driver-api/cxl/platform/example-configurations/multi-de= v-per-hb.rst @@ -14,7 +14,7 @@ Things to note: * This CEDT/SRAT describes one node for both devices. * There is only one proximity domain the HMAT for both devices. =20 -CEDT :: +:doc:`CEDT <../acpi/cedt>`:: =20 Subtable Type : 00 [CXL Host Bridge Structure] Reserved : 00 @@ -39,7 +39,7 @@ CEDT :: QtgId : 0001 First Target : 00000007 =20 -SRAT :: +:doc:`SRAT <../acpi/srat>`:: =20 Subtable Type : 01 [Memory Affinity] Length : 28 @@ -53,7 +53,7 @@ SRAT :: Hot Pluggable : 1 Non-Volatile : 0 =20 -HMAT :: +:doc:`HMAT <../acpi/hmat>`:: =20 Structure Type : 0001 [SLLBI] Data Type : 00 [Latency] @@ -69,14 +69,14 @@ HMAT :: Entry : 1200 Entry : 0200 =20 -SLIT :: +:doc:`SLIT <../acpi/slit>`:: =20 Signature : "SLIT" [System Locality Information Table] Localities : 0000000000000003 Locality 0 : 10 20 Locality 1 : FF 0A =20 -DSDT :: +:doc:`DSDT <../acpi/dsdt>`:: =20 Scope (_SB) { diff --git a/Documentation/driver-api/cxl/platform/example-configurations/o= ne-dev-per-hb.rst b/Documentation/driver-api/cxl/platform/example-configura= tions/one-dev-per-hb.rst index b89ba3cab98f..aebda0eb3e17 100644 --- a/Documentation/driver-api/cxl/platform/example-configurations/one-dev-= per-hb.rst +++ b/Documentation/driver-api/cxl/platform/example-configurations/one-dev-= per-hb.rst @@ -14,7 +14,7 @@ Things to note: * This CEDT/SRAT describes one node per device * The expanders have the same performance and will be in the same memory t= ier. =20 -CEDT :: +:doc:`CEDT <../acpi/cedt>`:: =20 Subtable Type : 00 [CXL Host Bridge Structure] Reserved : 00 @@ -62,7 +62,7 @@ CEDT :: QtgId : 0001 First Target : 00000006 =20 -SRAT :: +:doc:`SRAT <../acpi/srat>`:: =20 Subtable Type : 01 [Memory Affinity] Length : 28 @@ -88,7 +88,7 @@ SRAT :: Hot Pluggable : 1 Non-Volatile : 0 =20 -HMAT :: +:doc:`HMAT <../acpi/hmat>`:: =20 Structure Type : 0001 [SLLBI] Data Type : 00 [Latency] @@ -108,7 +108,7 @@ HMAT :: Entry : 0200 Entry : 0200 =20 -SLIT :: +:doc:`SLIT <../acpi/slit>`:: =20 Signature : "SLIT" [System Locality Information Table] Localities : 0000000000000003 @@ -116,7 +116,7 @@ SLIT :: Locality 1 : FF 0A FF Locality 2 : FF FF 0A =20 -DSDT :: +:doc:`DSDT <../acpi/dsdt>`:: =20 Scope (_SB) { --=20 2.49.0