diff options
author | Danilo Krummrich <dakr@kernel.org> | 2025-04-28 16:00:28 +0200 |
---|---|---|
committer | Danilo Krummrich <dakr@kernel.org> | 2025-05-04 17:54:04 +0200 |
commit | f301cb978c068faa8fcd630be2cb317a2d0ec063 (patch) | |
tree | 5df868f71820c6841dca164b69eac8c57355b071 /rust/kernel/str.rs | |
parent | 46f91addfabbd4109fb64876a032ae4a4a924919 (diff) |
rust: devres: implement Devres::access()
Implement a direct accessor for the data stored within the Devres for
cases where we can prove that we own a reference to a Device<Bound>
(i.e. a bound device) of the same device that was used to create the
corresponding Devres container.
Usually, when accessing the data stored within a Devres container, it is
not clear whether the data has been revoked already due to the device
being unbound and, hence, we have to try whether the access is possible
and subsequently keep holding the RCU read lock for the duration of the
access.
However, when we can prove that we hold a reference to Device<Bound>
matching the device the Devres container has been created with, we can
guarantee that the device is not unbound for the duration of the
lifetime of the Device<Bound> reference and, hence, it is not possible
for the data within the Devres container to be revoked.
Therefore, in this case, we can bypass the atomic check and the RCU read
lock, which is a great optimization and simplification for drivers.
Reviewed-by: Christian Schrefl <chrisi.schrefl@gmail.com>
Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>
Acked-by: Boqun Feng <boqun.feng@gmail.com>
Reviewed-by: Joel Fernandes <joelagnelf@nvidia.com>
Link: https://lore.kernel.org/r/20250428140137.468709-3-dakr@kernel.org
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
Diffstat (limited to 'rust/kernel/str.rs')
0 files changed, 0 insertions, 0 deletions