From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Rodrigo Siqueira" <siqueira@igalia.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"'Christian König'" <christian.koenig@amd.com>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Melissa Wen" <mwen@igalia.com>,
"'André Almeida'" <andrealmeid@igalia.com>,
"'Timur Kristóf'" <timur.kristof@gmail.com>
Cc: amd-gfx@lists.freedesktop.org, linux-doc@vger.kernel.org,
kernel-dev@igalia.com
Subject: Re: [PATCH 4/6] Documentation/gpu: Add explanation about AMD Pipes and Queues
Date: Wed, 26 Mar 2025 08:53:43 +0700 [thread overview]
Message-ID: <Z-NeJwfu1Gyx_CeX@archie.me> (raw)
In-Reply-To: <20250325172623.225901-5-siqueira@igalia.com>
[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]
On Tue, Mar 25, 2025 at 11:18:45AM -0600, Rodrigo Siqueira wrote:
> +.. kernel-figure:: pipe_and_queue_abstraction.svg
> +
> +In the central part of this figure, you can see two elements, one called
Did you mean hardware block?
> +**Pipe** and another named **Queues**; it is important to highlight that Queues
> +must be associated with a Pipe and vice-versa. Every specific hardware may have
> +a different number of Pipes and, in turn, a different number of Queues; for
> +example, GFX 11 has two Pipes and two Queues per Pipe.
> +
> +Pipe is the hardware that processes the instructions available in the Queues;
> +in other words, it is a thread executing the operations inserted in the Queue.
> +One crucial characteristic of Pipes is that they can only execute one Queue at
> +a time; no matter if the hardware has multiple Queues in the Pipe, it only runs
> +one Queue per Pipe. When a queue is running in the Pipe, it is said that the
> +Queue is **Active**.
> +
> +Pipes have the mechanics of swapping between queues at the hardware level.
> +Nonetheless, they only make use of Queues that are considered mapped. Pipes can
> +switch between queues based on any of the following inputs:
> +
> +1. Command Stream;
> +2. Packet by Packet;
> +3. Other hardware requests the change (e.g., MES).
> +
> +Queues within Pipes are defined by the Hardware Queue Descriptors (HQD).
> +Associated with the HQD concept, we have the Memory Queue Descriptor (MQD),
Related to HQD, we have MQD?
> +which is responsible for storing information about the state of each of the
> +available Queues in the memory. The state of a Queue contains information such
> +as the GPU virtual address of the queue itself, save areas, doorbell, etc. The
> +MQD also stores the HQD registers, which are vital for activating or
> +deactivating a given Queue.
> +
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-03-26 1:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 17:18 [PATCH 0/6] Documentation/gpu/amdgpu: Add documentation about Pipes, Queues, MES, and others Rodrigo Siqueira
2025-03-25 17:18 ` [PATCH 1/6] Documentation/gpu: Add new acronyms Rodrigo Siqueira
2025-03-26 8:08 ` Christian König
2025-03-25 17:18 ` [PATCH 2/6] Documentation/gpu: Change index order to show driver core first Rodrigo Siqueira
2025-03-25 17:18 ` [PATCH 3/6] Documentation/gpu: Create a documentation entry just for hardware info Rodrigo Siqueira
2025-03-25 17:18 ` [PATCH 4/6] Documentation/gpu: Add explanation about AMD Pipes and Queues Rodrigo Siqueira
2025-03-26 1:53 ` Bagas Sanjaya [this message]
2025-03-26 9:04 ` Christian König
2025-03-25 17:18 ` [PATCH 5/6] Documentation/gpu: Create a GC entry in the amdgpu documentation Rodrigo Siqueira
2025-03-26 1:55 ` Bagas Sanjaya
2025-03-26 9:14 ` Christian König
2025-03-25 17:18 ` [PATCH 6/6] Documentation/gpu: Add an intro about MES Rodrigo Siqueira
2025-03-26 1:58 ` Bagas Sanjaya
2025-03-26 17:57 ` [PATCH 0/6] Documentation/gpu/amdgpu: Add documentation about Pipes, Queues, MES, and others Alex Deucher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z-NeJwfu1Gyx_CeX@archie.me \
--to=bagasdotme@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrealmeid@igalia.com \
--cc=christian.koenig@amd.com \
--cc=kernel-dev@igalia.com \
--cc=linux-doc@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mwen@igalia.com \
--cc=siqueira@igalia.com \
--cc=timur.kristof@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox