Searched full:access (Results 1 – 25 of 917) sorted by relevance
12345678910>>...37
| /Documentation/admin-guide/LSM/ |
| D | Smack.rst | 9 Smack is the Simplified Mandatory Access Control Kernel.
10 Smack is a kernel based implementation of mandatory access
13 Smack is not the only Mandatory Access Control scheme
14 available for Linux. Those new to Mandatory Access Control
33 access to systems that use them as Smack does.
50 load the Smack access rules
53 report if a process with one label has access
85 Used to make access control decisions. In almost all cases
95 label does not allow all of the access permitted to a process
102 the Smack rule (more below) that permitted the write access
[all …]
|
| /Documentation/core-api/ |
| D | unaligned-memory-access.rst | 14 when it comes to memory access. This document presents some details about
19 The definition of an unaligned access
26 access.
28 The above may seem a little vague, as memory access can happen in different
32 which will compile to multiple-byte memory access instructions, namely when
47 of memory access. However, we must consider ALL supported architectures;
52 Why unaligned access is bad
55 The effects of performing an unaligned memory access vary from architecture
62 happen. The exception handler is able to correct the unaligned access,
66 unaligned access to be corrected.
[all …]
|
| D | protection-keys.rst | 23 bits (Access Disable and Write Disable) for each key. Being a CPU
30 permissions are enforced on data access only and have no effect on
45 directly in order to change access permissions to memory covered
57 gain access, do the update, then remove its write access::
88 That should be true whether something() is a direct access to 'ptr'
93 or when the kernel does the access on the application's behalf like
|
| D | this_cpu_ops.rst | 8 this_cpu operations are a way of optimizing access to per cpu
31 Access to the variable without the lock prefix is not synchronized but
144 access local per cpu data in a critical section. When preemption
273 Remote access to per cpu data
278 be "atomic" as no other CPU has access to these data structures.
280 There are special cases where you might need to access per cpu data
281 structures remotely. It is usually safe to do a remote read access
282 and that is frequently done to summarize counters. Remote write access
291 To access per-cpu data structure remotely, typically the per_cpu_ptr()
299 This makes it explicit that we are getting ready to access a percpu
[all …]
|
| /Documentation/arm/ |
| D | mem_alignment.rst | 5 Too many problems popped up because of unnoticed misaligned memory access in
14 unaligned memory access in general. If those access are predictable, you
16 alignment trap can fixup misaligned access for the exception cases, but at
20 trap to SIGBUS any code performing unaligned access (good for debugging bad
21 code), or even fixup the access by software like for kernel code. The later
36 0 A user process performing an unaligned memory access
42 performing the unaligned access. This is of course
47 performing the unaligned access.
59 information on unaligned access occurrences plus the current mode of
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-power | 9 Access: Read
18 Access: Read
27 Access: Read
36 Access: Read
58 Access: Read
76 Access: Read
89 Access: Read
98 Access: Read, Write
118 Access: Read
142 Access: Read
[all …]
|
| D | sysfs-bus-event_source-devices-hv_gpci | 36 '0' if the hypervisor is configured to forbid access to event
40 '1' if that access is allowed.
46 0 or 1. Indicates whether we have access to "GA" events (listed
53 0 or 1. Indicates whether we have access to "EXPANDED" events (listed
60 0 or 1. Indicates whether we have access to "LAB" events (listed
|
| D | sysfs-driver-input-exc3000 | 6 Access: Read
15 Access: Read
|
| /Documentation/driver-api/mmc/ |
| D | mmc-dev-parts.rst | 15 Read and write access is provided to the two MMC boot partitions. Due to
18 platform, write access is disabled by default to reduce the chance of
21 To enable write access to /dev/mmcblkXbootY, disable the forced read-only
22 access with::
26 To re-enable read-only access::
|
| /Documentation/devicetree/bindings/spi/ |
| D | spi-sprd-adi.txt | 3 ADI is the abbreviation of Anolog-Digital interface, which is used to access
9 48 hardware channels to access analog chip. For 2 software read/write channels,
10 users should set ADI registers to access analog chip. For hardware channels,
13 then users can access the mapped analog chip address by this hardware channel
19 the analog chip address where user want to access by hardware components.
21 Since we have multi-subsystems will use unique ADI to access analog chip, when
48 value specifies the analog chip address where user want to access
|
| /Documentation/admin-guide/mm/ |
| D | numaperf.rst | 36 pair may be organized into different ranked access classes to represent
39 the highest access class, 0. Any given target may have one or more
45 relationship for the access class "0" memory initiators and targets::
53 A memory initiator may have multiple memory targets in the same access
55 nodes' access characteristics share the same performance relative to other
56 linked initiator nodes. Each target within an initiator's access class,
59 The access class "1" is used to allow differentiation between initiators
61 IO initiators such as GPUs and NICs. Unlike access class 0, only
72 memory node's access class 0 initiators as follows::
77 are linked under the this access's inititiators.
[all …]
|
| /Documentation/sound/cards/ |
| D | hdspm.rst | 64 * access-mode -- MMAP (memory mapped), Not interleaved (PCM_NON-INTERLEAVED)
125 * Access -- Read Write
141 * Access -- Read Write
159 * Access -- Read Write
178 * Access -- Read Write
195 * Access -- Read Write
207 * Access -- Read Write
220 * Access -- Read Write
235 * Access -- Read Write
255 * Access -- Read Write
[all …]
|
| /Documentation/bpf/ |
| D | prog_cgroup_sysctl.rst | 22 ``BPF_PROG_TYPE_CGROUP_SYSCTL`` provides access to the following context from
39 value to the field can be used to access part of sysctl value starting from
40 specified ``file_pos``. Not all sysctl support access with ``file_pos !=
52 * ``0`` means "reject access to sysctl";
53 * ``1`` means "proceed with access".
62 helpers focus on providing access to these properties:
98 See `test_sysctl_prog.c`_ for an example of BPF program in C that access
100 the result to make decision whether to allow or deny access to sysctl.
|
| /Documentation/powerpc/ |
| D | cxlflash.rst | 27 user space application direct access to Flash storage.
33 special path for user space access, and performing error recovery. It
46 either raw access to the entire LUN (referred to as direct
47 or physical LUN access) or access to a kernel/AFU-mediated
48 partition of the LUN (referred to as virtual LUN access). The
90 access to the Flash from user space (without requiring a system call).
93 block library to enable this user space access. The driver supports
115 Applications intending to get access to the CXL Flash from user
121 specifically for devices (LUNs) operating in user space access
135 device (LUN) via user space access need to use the services provided
[all …]
|
| /Documentation/vm/ |
| D | split_page_table_lock.rst | 13 access to the table. At the moment we use split lock for PTE and PMD
14 tables. Access to higher level tables protected by mm->page_table_lock.
83 page->ptl is used to access split page table lock, where 'page' is struct
91 can avoid indirect access and save a cache line.
95 one more cache line for indirect access;
100 Please, never access page->ptl directly -- use appropriate helper.
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | devices.rst | 9 on device files. A device cgroup associates a device access
13 either an integer or * for all. Access is a composition of r
19 never receive a device access which is denied by its parent.
61 access permissions than its parent. Every time an entry is written to
65 more access than the cgroup's parent, it'll be removed from the whitelist.
129 implementation. Removal or addition of exceptions that will reduce the access
132 on current parent's access rules.
|
| /Documentation/block/ |
| D | pr.rst | 8 access to block devices to specific initiators in a shared storage
30 Only the initiator that owns the reservation can access the
38 Only initiators with a registered key can access the device.
50 Only initiators with a registered key can access the device.
75 This ioctl command reserves the device and thus restricts access for other
85 and thus removes any access restriction implied by it.
|
| /Documentation/driver-api/ |
| D | dma-buf.rst | 5 hardware (DMA) access across multiple device drivers and subsystems, and
6 for synchronizing asynchronous hardware access.
14 one device has finished access, and (3) reservation, which manages the
44 - and needs a mechanism to get access to the scatterlist that makes up this
45 buffer in memory, mapped into its own address space, so it can access the
71 access to buffers, via the leaked fd, to which it should otherwise
72 not be permitted access.
86 discussion below on `CPU Access to DMA Buffer Objects`_ for the full details.
91 Basic Operation and Device DMA Access
95 :doc: dma buf device access
[all …]
|
| /Documentation/misc-devices/ |
| D | c2port.rst | 57 access flash_block_size flash_erase rev_id
61 Initially the C2port access is disabled since you hardware may have
62 such lines multiplexed with other devices so, to get access to the
65 # echo 1 > /sys/class/c2port/c2port0/access
75 However, for security reasons, the in-system flash access in not
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | ecm.txt | 6 Local Access Window (LAW) Node
8 The LAW node represents the region of CCSR space where local access
11 number of local access windows as specified by fsl,num-laws.
30 Definition: The value specifies the number of local access
|
| D | mcm.txt | 6 Local Access Window (LAW) Node
8 The LAW node represents the region of CCSR space where local access
11 number of local access windows as specified by fsl,num-laws.
30 Definition: The value specifies the number of local access
|
| /Documentation/dev-tools/ |
| D | kasan.rst | 15 validity checks before every memory access, and therefore require a compiler
53 A typical out-of-bounds access generic KASAN report looks like this::
115 page dumped because: kasan: bad access detected
127 and what kind of access caused it. It's followed by a stack trace of the bad
128 access, a stack trace of where the accessed memory was allocated (in case bad
129 access happens on a slab object), and a stack trace of where the object was
166 Synchronous mode: a bad access is detected immediately when a tag
168 Asynchronous mode: a bad access detection is delayed. When a tag check
206 memory is safe to access, and use compile-time instrumentation to insert checks
207 of shadow memory on each memory access.
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | brcm,iproc-mhb.txt | 5 interface; 3) access to the Nitro (network processing) engine
7 This node allows access to these MHB registers via syscon.
|
| /Documentation/devicetree/bindings/gpio/ |
| D | nvidia,tegra186-gpio.txt | 14 a) Security registers, which allow configuration of allowed access to the GPIO
19 Access to this set of registers is not necessary in all circumstances. Code
20 that wishes to configure access to the GPIO registers needs access to these
22 need access to these registers.
26 address space, each of which access the same underlying state. See the hardware
27 documentation for rationale. Any particular GPIO client is expected to access
|
| /Documentation/ABI/stable/ |
| D | sysfs-devices-node | 99 The node's relationship to other nodes for access class "Y".
106 nodes that have class "Y" access to this target node's
116 this initiator node has class "Y" access.
123 nodes found in this access class's linked initiators.
130 from nodes found in this access class's linked initiators.
137 found in this access class's linked initiators.
143 This node's write latency in nanoseconds when access
|
12345678910>>...37