Home
last modified time | relevance | path

Searched refs:Mutex (Results 1 – 25 of 25) sorted by relevance

/linux/samples/rust/
H A Drust_debugfs.rs54 Mutex,
77 inner: File<Mutex<Inner>>,
79 array_blob: File<Mutex<[u8; 4]>>,
81 vector_blob: File<Mutex<KVec<u8>>>,
145 fn build_inner(dir: &Dir) -> impl PinInit<File<Mutex<Inner>>> + '_ { in build_inner()
H A Drust_debugfs_scoped.rs20 Mutex, //
109 devices: Mutex<KVec<Pin<KBox<Scope<DeviceData>>>>>,
126 blob: Pin<KBox<Mutex<[u8; SZ_4K]>>>,
H A Drust_misc_device.rs106 sync::{aref::ARef, Mutex},
150 inner: Mutex<Inner>,
H A Drust_configfs.rs11 use kernel::sync::Mutex;
31 bar: Mutex<(KBox<[u8; PAGE_SIZE]>, usize)>,
/linux/rust/kernel/debugfs/
H A Dtraits.rs19 Mutex, //
53 impl<T: Writer> Writer for Mutex<T> { implementation
91 impl<T: BinaryWriter> BinaryWriter for Mutex<T> { implementation
180 impl<T: FromStr + Unpin> Reader for Mutex<T> { implementation
297 impl<T: BinaryReaderMut + Unpin> BinaryReader for Mutex<T> { implementation
/linux/rust/kernel/sync/lock/
H A Dmutex.rs7 /// Creates a [`Mutex`] initialiser with the given name and a newly-created lock class.
14 $crate::sync::Mutex::new(
26 /// Since it may block, [`Mutex`] needs to be used with care in atomic contexts.
28 /// Instances of [`Mutex`] need a lock class and to be pinned. The recommended way to create such
37 /// use kernel::sync::{new_mutex, Mutex};
48 /// d: Mutex<Inner>,
72 /// use kernel::sync::Mutex;
79 /// fn example(m: &Mutex<Example>) {
87 pub type Mutex<T> = super::Lock<T, MutexBackend>; typedef
89 /// A [`Guard`] acquired from locking a [`Mutex`]
[all...]
H A Dglobal.rs198 /// unsafe(uninit) static MY_COUNTER: Mutex<u32> = 0;
228 /// unsafe(uninit) static MY_MUTEX: Mutex<()> = ();
301 (backend Mutex) => {
/linux/drivers/android/binder/
H A Dcontext.rs11 sync::{Arc, Mutex},
19 pub(crate) unsafe(uninit) static CONTEXTS: Mutex<ContextList> = ContextList {
49 manager: Mutex<Manager>,
H A Dpage_range.rs33 sync::{aref::ARef, Mutex, SpinLock},
137 mm_lock: Mutex<()>,
H A Dprocess.rs33 Arc, ArcBorrow, CondVar, CondVarTimeoutResult, Mutex, SpinLock, UniqueArc,
457 node_refs: Mutex<ProcessNodeRefs>,
/linux/Documentation/translations/zh_CN/rust/
H A Dgeneral-information.rst58 例如,人们可以在Rust中写一个 ``Mutex`` 抽象,它从C端包装一个 ``Mutex结构体`` ,并
/linux/drivers/gpu/drm/tyr/
H A Ddriver.rs21 use kernel::sync::Mutex;
45 clks: Mutex<Clocks>,
48 regulators: Mutex<Regulators>,
/linux/drivers/block/rnull/
H A Dconfigfs.rs13 sync::Mutex,
114 data: Mutex<DeviceConfigInner>,
/linux/rust/kernel/
H A Dsync.rs29 pub use lock::mutex::{new_mutex, Mutex, MutexGuard};
/linux/drivers/hwspinlock/
H A DKconfig25 Say y here to support the Qualcomm Hardware Mutex functionality, which
/linux/Documentation/rust/
H A Dgeneral-information.rst76 For instance, one may write a ``Mutex`` abstraction in Rust which wraps
/linux/Documentation/locking/
H A Dmutex-design.rst2 Generic Mutex Subsystem
H A Drt-mutex-design.rst196 Mutex Waiters Tree
301 Mutex owner and flags
514 Unlocking the Mutex
H A Dww-mutex-design.rst2 Wound/Wait Deadlock-Proof Mutex Design
/linux/fs/jffs2/
H A DREADME.Locking40 File Mutex f->sem
/linux/Documentation/userspace-api/
H A Dntsync.rst294 - Mutex owner identifier. If any object in ``objs`` is a mutex,
/linux/Documentation/filesystems/
H A Dconfigfs.rst375 Hierarchy Navigation and the Subsystem Mutex
/linux/Documentation/kernel-hacking/
H A Dlocking.rst1343 Mutex API reference
/linux/Documentation/translations/it_IT/kernel-hacking/
H A Dlocking.rst1382 Riferimento per l'API dei Mutex
/linux/lib/
H A DKconfig.debug1528 bool "RT Mutex debugging, deadlock detection"
1545 bool "Mutex debugging: basic checks"