Home
last modified time | relevance | path

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

/Linux-v5.4/Documentation/process/
Dvolatile-considered-harmful.rst56 accesses are always done through accessor functions; accessing I/O memory
76 - The above-mentioned accessor functions might use volatile on
78 each accessor call becomes a little critical section on its own and
Dcoding-style.rst345 the proper accessor functions.
349 Opaqueness and ``accessor functions`` are not good in themselves.
/Linux-v5.4/Documentation/vm/
Dsplit_page_table_lock.rst16 There are helpers to lock/unlock a table and other accessor functions:
/Linux-v5.4/Documentation/admin-guide/hw-vuln/
Dspectre.rst155 potentially be influenced for Spectre attacks, new "nospec" accessor
269 where such kernel code has been identified, nospec accessor macros
425 basis to use nospec accessor macros for bounds clipping :ref:`[2]
510 uses nospec accessor macros for "bounds clipping", to avoid any
/Linux-v5.4/Documentation/core-api/
Dtimekeeping.rst6 using an accessor with a shorter name is preferred over one with a longer
/Linux-v5.4/Documentation/driver-api/
Ddevice-io.rst38 suitable for passing to the accessor functions described below, you
/Linux-v5.4/virt/kvm/
Dkvm_main.c3049 int (*accessor)(struct kvm_device *dev, in kvm_device_ioctl_attr()
3055 if (!accessor) in kvm_device_ioctl_attr()
3061 return accessor(dev, &attr); in kvm_device_ioctl_attr()
/Linux-v5.4/Documentation/
Dmemory-barriers.txt2448 Inside of the Linux kernel, I/O should be done through the appropriate accessor
2451 use of memory barriers unnecessary, if the accessor functions are used to refer
2515 series of accessor functions that provide various degrees of ordering
/Linux-v5.4/drivers/infiniband/hw/hfi1/
Dchip.c1208 #define CNTR_ELEM(name, csr, offset, flags, accessor) \ argument
1214 accessor \
/Linux-v5.4/Documentation/security/keys/
Dcore.rst1288 is that the accessor may be required to sleep.