| /linux-4.1.27/Documentation/pcmcia/ |
| D | locking.txt | 53 protected by pcmcia_socket_list_rwsem;
58 The resource_ops and their data are protected by ops_mutex.
60 The "main" struct pcmcia_socket is protected as follows (read-only fields
99 The "main" struct pcmcia_devie is protected as follows (read-only fields
|
| /linux-4.1.27/scripts/kconfig/ |
| D | qconf.h | 62 protected:
268 protected:
292 protected:
325 protected:
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | files.txt | 7 Up until 2.6.12, the file descriptor table has been protected
9 ->file_lock protected accesses to all the file related fields
15 The files (struct file) themselves are protected using
55 2. Reading of the fdtable as described above must be protected
|
| D | path-lookup.txt | 84 The hash lists are RCU protected, so list walking is not serialised with
89 hash, and its inode are protected by the per-dentry d_lock spinlock. A
94 These members are also protected by d_seq seqlock, although this offers
100 Back to the rename case. In usual RCU protected lists, the only operations that
226 path string, rcu-walk uses a d_seq protected snapshot. When looking up a
307 * inode is also RCU protected so we can load d_inode and use the inode for
|
| D | porting | 92 protected.
215 ->d_parent changes are not protected by BKL anymore. Read access is safe
223 not protected by the conditions above is risky even in the old tree - you
248 exactly what needs to be protected.
|
| D | sysfs-pci.txt | 118 Legacy resources are protected by the HAVE_PCI_LEGACY define. Platforms
|
| D | xfs-delayed-logging-design.txt | 265 can we store state in any field that is protected by the AIL lock. Hence the
655 concurrently, the CIL needs to be protected separately from the above
|
| D | sharedsubtree.txt | 882 ->mnt_share, ->mnt_slave, ->mnt_slave_list, ->mnt_master are protected
|
| D | proc.txt | 1852 own. Sensitive files like cmdline, sched*, status are now protected against
1857 now protected against local eavesdroppers.
|
| D | vfs.txt | 559 Adding and removing pages to/from an address_space is protected by the
|
| /linux-4.1.27/arch/powerpc/boot/dts/ |
| D | mpc5121ads.dts | 43 protected@0 {
44 label = "protected";
45 reg = <0x00000000 0x00040000>; // first sector is protected
|
| D | p1020rdb-pc_camp_core0.dts | 57 protected-sources = <
|
| D | mpc8572ds_camp_core0.dts | 60 protected-sources = <
|
| D | mpc8572ds_camp_core1.dts | 83 protected-sources = <
|
| D | p1020rdb-pc_camp_core1.dts | 105 protected-sources = <
|
| /linux-4.1.27/Documentation/ |
| D | preempt-locking.txt | 37 RULE #2: CPU state must be protected.
40 Under preemption, the state of the CPU must be protected. This is arch-
131 is done. They may also be called within a spin-lock protected region, however,
134 are also protected by preemption locks and so may use the versions which do
|
| D | io_ordering.txt | 7 critical section of code protected by spinlocks. This would ensure that
|
| D | ramoops.txt | 54 kernel to use only the first 128 MB of memory, and place ECC-protected ramoops
|
| D | pwm.txt | 111 The PWM core list manipulations are protected by a mutex, so pwm_request()
|
| D | volatile-considered-harmful.txt | 50 registers. Within the kernel, register accesses, too, should be protected
|
| D | clk.txt | 286 of the two groups needs to be protected by the drivers. An example of such a
|
| D | Changes | 270 services be protected from the internet-at-large by a firewall where
|
| D | intel_txt.txt | 138 of the VT-d DMARs in a DMA-protected region of memory and verifies
|
| D | robust-futexes.txt | 35 prematurely - and the new owner can decide whether the data protected by
|
| D | media-framework.txt | 282 drivers. Access to the field must be protected by the media device graph_mutex
|
| D | vfio.txt | 9 a secure, IOMMU protected environment. In other words, this allows
|
| D | kobject.txt | 248 The end result is that a structure protected by a kobject cannot be freed
|
| D | memory-barriers.txt | 232 memory references that are not protected by ACCESS_ONCE(). Without
279 (*) Even in cases where bitfields are protected by locks, all fields
280 in a given bitfield must be protected by one lock. If two fields
281 in a given bitfield are protected by different locks, the compiler's
|
| D | kernel-parameters.txt | 825 be intentionally kept free (and hence protected) by the
2003 [KNL,X86] Mark specific memory as protected.
3831 medium is write-protected).
|
| /linux-4.1.27/Documentation/RCU/ |
| D | checklist.txt | 52 As a rough rule of thumb, any dereference of an RCU-protected
67 an RCU-protected list. Alternatively, use the other
68 RCU-protected data structures that have been added to
118 code know exactly which pointers are protected by RCU.
158 in their respective types of RCU-protected lists.
161 type of RCU-protected linked lists.
245 used by the RCU-protected data structure, including
294 critical section or must be protected by appropriate update-side
314 all currently executing rcu_read_lock()-protected RCU read-side
318 read-side critical sections are protected by something other
[all …]
|
| D | lockdep.txt | 53 This is useful in code that uses RCU-protected arrays
106 to use rcu_dereference_protected() if either the RCU-protected pointer
107 or the RCU-protected data that it points to can change concurrently.
|
| D | rcuref.txt | 1 Reference-count design for elements of lists/arrays protected by RCU.
12 Reference counting on elements of lists which are protected by traditional
|
| D | 00-INDEX | 22 - Reference-count design for elements of lists/arrays protected by RCU
|
| D | lockdep-splat.txt | 4 family to access an RCU-protected pointer without the proper protection.
8 RCU-protected data structure without either (1) being in the right kind of
|
| D | whatisRCU.txt | 141 read-side critical sections. Any RCU-protected data structure
217 RCU-protected pointer, in order to safely communicate the change
223 pointers are protected by RCU and (2) the point at which a
235 The reader uses rcu_dereference() to fetch an RCU-protected
245 RCU-protected pointer to a local variable, then dereferences
257 RCU-protected structure, using the local variable is of
281 rcu_dereference() is to document which pointers are protected by
420 to dereference RCU-protected pointers.
425 o Use rcu_assign_pointer() to update an RCU-protected pointer.
432 RCU-protected data structure, but -before- reclaiming/freeing
[all …]
|
| D | rcu_dereference.txt | 12 to load an RCU-protected pointer, otherwise CONFIG_PROVE_RCU
28 o Do not use single-element RCU-protected arrays. The compiler
148 RCU-protected circular linked lists.
|
| D | NMI-RCU.txt | 120 being protected by RCU-sched.
|
| D | RTFP.txt | 159 Robert Olsson described an RCU-protected trie-hash combination
179 The problem of resizeable RCU-protected hash tables may now be on a path
185 [PaulEMcKenney2010LockdepRCU], another resizeable RCU-protected hash
188 avoidance in the networking code), realization of the 2009 RCU-protected
193 [LinusTorvalds2011Linux2:6:38:rc1:NPigginVFS], an RCU-protected red-black
196 RCU-protected resizeable hash tables [Triplett:2011:RPHash], the 3.0 RCU
202 covering RCU-protected resizable hash tables and the relationship
1470 RCU-protected radix tree.
1517 Uses RCU-protected radix tree for a lockless page cache.
1545 RCU-protected dynamic trie-hash combination.
[all …]
|
| D | arrayRCU.txt | 19 has a linked-list hash chain. Each hash chain can be protected by RCU
|
| D | rcu.txt | 9 since dropped their references. For example, an RCU-protected deletion
|
| D | UP.txt | 101 Because the calling function is scanning an RCU-protected linked
|
| D | rcubarrier.txt | 32 rcu_head struct placed within the RCU-protected data structure and
|
| /linux-4.1.27/arch/parisc/ |
| D | Kconfig.debug | 9 Mark the kernel read-only data as write-protected in the pagetables,
|
| /linux-4.1.27/arch/powerpc/sysdev/ |
| D | mpic.c | 1026 if (mpic->protected && test_bit(hw, mpic->protected)) { in mpic_host_map()
1342 mpic->protected = kzalloc(mapsize*sizeof(long), GFP_KERNEL); in mpic_alloc()
1343 BUG_ON(mpic->protected == NULL); in mpic_alloc()
1347 __set_bit(psrc[i], mpic->protected); in mpic_alloc()
1630 if (mpic->protected && test_bit(i, mpic->protected)) in mpic_init()
1796 if (unlikely(mpic->protected && test_bit(src, mpic->protected))) { in _mpic_get_one_irq()
1835 if (unlikely(mpic->protected && test_bit(src, mpic->protected))) { in mpic_get_coreint_irq()
|
| /linux-4.1.27/Documentation/fb/ |
| D | vesafb.txt | 12 graphics mode. Switching mode later on (in protected mode) is
109 The VESA BIOS provides protected mode interface for changing
123 ypan enable display panning using the VESA protected mode
145 pmipal Use the protected mode interface for palette changes.
|
| D | uvesafb.txt | 59 ypan Enable display panning using the VESA protected mode
78 pmipal Use the protected mode interface for palette changes.
79 This is the default if the protected mode interface is
|
| /linux-4.1.27/arch/powerpc/kernel/vdso64/ |
| D | datapage.S | 24 .protected __get_datapage
|
| /linux-4.1.27/arch/powerpc/kernel/vdso32/ |
| D | datapage.S | 24 .protected __get_datapage
|
| /linux-4.1.27/Documentation/vm/ |
| D | split_page_table_lock | 4 Originally, mm->page_table_lock spinlock protected all page tables of the
11 tables. Access to higher level tables protected by mm->page_table_lock.
|
| D | ksm.txt | 10 can be replaced by a single write-protected page (which is automatically
|
| /linux-4.1.27/Documentation/locking/ |
| D | lglock.txt | 105 access to protected per_cpu object on this CPU
109 access to protected per_cpu object on other CPU cpu
113 access all protected per_cpu objects on all CPUs
|
| D | spinlocks.txt | 15 there is only one thread-of-control within the region(s) protected by that
|
| D | rt-mutex-design.txt | 208 has a plist to store these waiters by priority. This list is protected by
228 pi_list. This list is protected by a spin lock also in the task structure,
499 protected only by the task's pi_lock. But the code to unlock the mutex
|
| /linux-4.1.27/arch/x86/platform/olpc/ |
| D | xo1-wakeup.S | 15 # OFW lands us here, running in protected mode, with a
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | interlaken-lac.txt | 43 those LAC CCSR registers not protected in partitioned
54 "fsl,interlaken-lac-hv". This node represents the protected
61 Definition: Points to the non-protected LAC CCSR mapped register space
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | mmu.txt | 95 - access to missing or protected translations
228 emulations if the page needs to be write-protected (see "Synchronized
250 protected, and synchronize sptes to gptes when a gpte is written.
274 - access to a protected translation
275 - when logging dirty pages, memory is write protected
276 - synchronized shadow pages are write protected (*)
386 write-protected pages
390 arrays for each memory slot and large page size. Every write protected page
|
| D | locking.txt | 23 the gfn is writable on guest mmu and it is not write-protected by shadow
|
| /linux-4.1.27/Documentation/devicetree/bindings/c6x/ |
| D | dscr.txt | 9 more configuration registers often protected by a lock register where one or
45 possibly multiple tuples describing registers which are write protected by
|
| /linux-4.1.27/arch/powerpc/include/asm/ |
| D | mpic.h | 315 unsigned long *protected; member
|
| /linux-4.1.27/Documentation/x86/ |
| D | boot.txt | 36 Protocol 2.05: (Kernel 2.6.20) Make protected mode kernel relocatable.
92 When using bzImage, the protected-mode kernel was relocated to
261 The size of the protected-mode code in units of 16-byte paragraphs.
406 - If 0, the protected-mode code is loaded at 0x10000.
407 - If 1, the protected-mode code is loaded at 0x100000.
455 The address to jump to in protected mode. This defaults to the load
575 If this field is nonzero, the protected-mode part of the kernel can
663 of the protected-mode code to the payload.
1016 entering protected mode. The default routine disables NMI, so
1021 transition to protected mode, but before the kernel is
[all …]
|
| D | exception-tables.txt | 40 was not swapped in, write protected or something similar. However,
|
| /linux-4.1.27/Documentation/devicetree/bindings/power/ |
| D | renesas,sysc-rmobile.txt | 19 - the second block refers to the registers protected by the HPB
|
| /linux-4.1.27/drivers/net/ethernet/sfc/ |
| D | siena.c | 808 bool protected; in siena_mtd_probe_partition() local
820 rc = efx_mcdi_nvram_info(efx, type, &size, &erase_size, &protected); in siena_mtd_probe_partition()
823 if (protected) in siena_mtd_probe_partition()
|
| D | ef10.c | 3403 bool protected; in efx_ef10_mtd_probe_partition() local
3416 rc = efx_mcdi_nvram_info(efx, type, &size, &erase_size, &protected); in efx_ef10_mtd_probe_partition()
3419 if (protected) in efx_ef10_mtd_probe_partition()
|
| /linux-4.1.27/Documentation/security/ |
| D | keys-ecryptfs.txt | 24 kernel and protected by the parent master key.
|
| D | Smack.txt | 277 protected from each other. This scheme has been widely deployed as a component
|
| /linux-4.1.27/arch/arm/boot/dts/ |
| D | orion5x-maxtor-shared-storage-2.dts | 65 * a single, write-protected partition covering the whole
|
| D | orion5x-lacie-ethernet-disk-mini-v2.dts | 86 * a single, write-protected partition covering the whole
|
| D | orion5x-lacie-d2-network.dts | 105 * a single, write-protected partition covering the whole
|
| /linux-4.1.27/Documentation/scsi/ |
| D | dc395x.txt | 93 The driver is free software. It is protected by the GNU General Public
|
| D | st.txt | 108 device can be opened for writing even if there is a write protected
|
| /linux-4.1.27/Documentation/metag/ |
| D | kernel-ABI.txt | 40 Global registers are shared between threads and are privilege protected.
101 be used on SMP for this purpose. Since no protected local registers are
|
| /linux-4.1.27/include/scsi/ |
| D | libiscsi.h | 138 bool protected; member
|
| /linux-4.1.27/Documentation/misc-devices/ |
| D | eeprom | 72 bytes of the memory array are not write protected. Any byte data write to
|
| /linux-4.1.27/Documentation/cpu-freq/ |
| D | boost.txt | 82 on AMD CPUs, though it is now protected by a config switch
|
| /linux-4.1.27/Documentation/isdn/ |
| D | HiSax.cert | 47 files are protected by md5 checksums and the md5sum file is pgp signed by
|
| /linux-4.1.27/Documentation/i2c/busses/ |
| D | i2c-ali15x3 | 63 full data sheets on the web site are password protected, however if you
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | zl6100 | 83 to those registers are protected, this may result in power loss, board resets,
|
| /linux-4.1.27/security/ |
| D | Kconfig | 110 This is the portion of low virtual memory which should be protected
|
| /linux-4.1.27/arch/ |
| D | Kconfig | 421 wrapped as well. Irqs are already protected inside
423 irq exit still need to be protected.
|
| /linux-4.1.27/arch/metag/ |
| D | Kconfig | 131 memory in LOCK1 protected atomics and spinlocks.
|
| /linux-4.1.27/Documentation/misc-devices/mei/ |
| D | mei.txt | 7 The Intel Management Engine (Intel ME) is an isolated and protected computing
|
| /linux-4.1.27/fs/jffs2/ |
| D | README.Locking | 86 the list are protected by the file mutex f->sem. But the erase code
|
| /linux-4.1.27/drivers/mtd/nand/ |
| D | Kconfig | 295 partitioning to segregate write-protected blocks. On the Treo680, the
296 first five erase blocks (256KiB each) are write-protected, followed
|
| /linux-4.1.27/arch/x86/math-emu/ |
| D | README | 153 The emulator supports 16-bit protected mode, with one difference from
156 will not allow this in 16-bit protected mode: no instructions are
|
| /linux-4.1.27/Documentation/networking/ |
| D | udplite.txt | 76 RTP and UDP headers are to be protected, a receiver can enforce that only
|
| /linux-4.1.27/arch/x86/ |
| D | Kconfig.debug | 94 Mark the kernel read-only data as write-protected in the pagetables,
|
| D | Kconfig | 1011 protected mode legacy code on x86 processors. Disabling
1426 bool "Support non-standard NVDIMMs and ADR protected memory"
1429 by the Intel Sandy Bridge-EP reference BIOS as protected memory.
|
| /linux-4.1.27/Documentation/sysctl/ |
| D | fs.txt | 205 or otherwise protected/tainted binaries. The modes are
|
| D | vm.txt | 355 (should not be protected. = 0;
|
| /linux-4.1.27/Documentation/ia64/ |
| D | mca.txt | 9 asking for deadlock. Also the state of structures that are protected
|
| /linux-4.1.27/drivers/scsi/ |
| D | libiscsi.c | 392 task->protected = true; in iscsi_prep_scsi_cmd_pdu()
839 if (task->protected) { in iscsi_scsi_cmd_rsp()
1626 task->protected = false; in iscsi_alloc_task()
|
| /linux-4.1.27/scripts/ |
| D | spelling.txt | 739 procteted||protected
|
| /linux-4.1.27/arch/x86/kvm/ |
| D | mmu.c | 1967 bool protected = false; in mmu_sync_children() local
1970 protected |= rmap_write_protect(vcpu->kvm, sp->gfn); in mmu_sync_children()
1972 if (protected) in mmu_sync_children()
|
| /linux-4.1.27/Documentation/power/ |
| D | swsusp.txt | 290 encrypted and protected are retrieved and stolen from the swap device.
|
| D | devices.txt | 444 This may be the hardest part, and the one most protected by NDA'd documents
|
| /linux-4.1.27/mm/ |
| D | Kconfig | 349 This is the portion of low virtual memory which should be protected
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 4.Coding | 164 accessed concurrently by more than one thread must be protected by a lock.
|
| /linux-4.1.27/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 442 protected by the receiving host or if acceptance may result in violation of
|
| /linux-4.1.27/lib/ |
| D | Kconfig.debug | 1217 RCU-protected pointers. This annotation will cause sparse
1223 Say Y to make sparse flag questionable use of RCU-protected pointers
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | booting-without-of.txt | 277 entry point once it switched into protected mode). That entry point
|