Searched refs:accessor (Results 1 – 9 of 9) sorted by relevance
56 accesses are always done through accessor functions; accessing I/O memory76 - The above-mentioned accessor functions might use volatile on78 each accessor call becomes a little critical section on its own and
345 the proper accessor functions.349 Opaqueness and ``accessor functions`` are not good in themselves.
16 There are helpers to lock/unlock a table and other accessor functions:
6 using an accessor with a shorter name is preferred over one with a longer
38 suitable for passing to the accessor functions described below, you
2794 int (*accessor)(struct kvm_device *dev, in kvm_device_ioctl_attr()2800 if (!accessor) in kvm_device_ioctl_attr()2806 return accessor(dev, &attr); in kvm_device_ioctl_attr()
2533 Inside of the Linux kernel, I/O should be done through the appropriate accessor2543 (2) If the accessor functions are used to refer to an I/O memory window with2603 When accessing I/O memory, drivers should use the appropriate accessor
1156 is that the accessor may be required to sleep.
1208 #define CNTR_ELEM(name, csr, offset, flags, accessor) \ argument1214 accessor \
