Home
last modified time | relevance | path

Searched refs:accessor (Results 1 – 7 of 7) sorted by relevance

/linux-4.4.14/Documentation/
Dvolatile-considered-harmful.txt53 accesses are always done through accessor functions; accessing I/O memory
73 - The above-mentioned accessor functions might use volatile on
75 each accessor call becomes a little critical section on its own and
DCodingStyle294 the proper accessor functions.
296 NOTE! Opaqueness and "accessor functions" are not good in themselves.
Dmemory-barriers.txt2422 Inside of the Linux kernel, I/O should be done through the appropriate accessor
2432 (2) If the accessor functions are used to refer to an I/O memory window with
2492 When accessing I/O memory, drivers should use the appropriate accessor
/linux-4.4.14/Documentation/vm/
Dsplit_page_table_lock13 There are helpers to lock/unlock a table and other accessor functions:
/linux-4.4.14/virt/kvm/
Dkvm_main.c2585 int (*accessor)(struct kvm_device *dev, in kvm_device_ioctl_attr()
2591 if (!accessor) in kvm_device_ioctl_attr()
2597 return accessor(dev, &attr); in kvm_device_ioctl_attr()
/linux-4.4.14/drivers/staging/rdma/hfi1/
Dchip.c1152 #define CNTR_ELEM(name, csr, offset, flags, accessor) \ argument
1158 accessor \
/linux-4.4.14/Documentation/security/
Dkeys.txt1070 is that the accessor may be required to sleep.