diff options
| author | Bjorn Helgaas <bhelgaas@google.com> | 2023-08-14 16:28:22 -0500 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2023-08-18 11:29:03 -0600 |
| commit | d56b699d76d1b352f7a3d3a0a3e91c79b8612d94 (patch) | |
| tree | 2a368f3e2e17f7a516bf39e055f79d8c79a74885 /Documentation/gpu/i915.rst | |
| parent | ebab9426cd73c45945b44344ca904b343f0ca070 (diff) | |
Documentation: Fix typos
Fix typos in Documentation.
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Link: https://lore.kernel.org/r/20230814212822.193684-4-helgaas@kernel.org
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/gpu/i915.rst')
| -rw-r--r-- | Documentation/gpu/i915.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/gpu/i915.rst b/Documentation/gpu/i915.rst index 60ea21734902..378e825754d5 100644 --- a/Documentation/gpu/i915.rst +++ b/Documentation/gpu/i915.rst @@ -304,10 +304,10 @@ reads of following commands. Actions issued between different contexts and the only way to synchronize across contexts (even from the same file descriptor) is through the use of fences. At least as far back as Gen4, also have that a context carries with it a GPU HW context; -the HW context is essentially (most of atleast) the state of a GPU. +the HW context is essentially (most of at least) the state of a GPU. In addition to the ordering guarantees, the kernel will restore GPU state via HW context when commands are issued to a context, this saves -user space the need to restore (most of atleast) the GPU state at the +user space the need to restore (most of at least) the GPU state at the start of each batchbuffer. The non-deprecated ioctls to submit batchbuffer work can pass that ID (in the lower bits of drm_i915_gem_execbuffer2::rsvd1) to identify what context to use with the command. |