| /linux/arch/arm/mm/ |
| H A D | proc-xscale.S | 218 mcrne p15, 0, ip, c7, c5, 0 @ Invalidate I cache & BTB
241 mcrne p15, 0, r0, c7, c5, 1 @ Invalidate I cache line
243 mcr p15, 0, r0, c7, c6, 1 @ Invalidate D cache line
248 mcrne p15, 0, ip, c7, c5, 6 @ Invalidate BTB
273 mcr p15, 0, r0, c7, c5, 0 @ Invalidate I cache & BTB
291 mcr p15, 0, r0, c7, c5, 1 @ Invalidate I cache entry
296 mcr p15, 0, r0, c7, c5, 6 @ Invalidate BTB
318 mcr p15, 0, r0, c7, c5, 0 @ Invalidate I cache & BTB
454 mcr p15, 0, ip, c7, c5, 0 @ Invalidate I cache & BTB
|
| H A D | Kconfig | 1005 bool "PL310 errata: Clean & Invalidate maintenance operations do not invalidate clean lines"
1008 Invalidate maintenance operations: by Physical Address
1017 bool "PL310 errata: Background Clean & Invalidate by Way operation can cause data corruption"
1019 PL310 implements the Clean & Invalidate by Way L2 cache maintenance
1024 Invalidate by Way operation. Revisions prior to r3p1 are affected by
|
| /linux/Documentation/driver-api/cxl/allocation/ |
| H A D | dax.rst | 12 mechanisms must be employed unless the region supports Snoop Back-Invalidate.
|
| /linux/arch/arc/kernel/ |
| H A D | head.S | 40 bclr r5, r5, 6 ; Invalidate (discard w/o wback)
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | era.rst | 91 - Invalidate those blocks in the caching software
|
| /linux/Documentation/PCI/ |
| H A D | pci.rst | 226 If the PCI device can use the PCI Memory-Write-Invalidate transaction,
230 or chip-sets may support Memory-Write-Invalidate. Alternatively,
486 pci_set_mwi() Enable Memory-Write-Invalidate transactions.
487 pci_clear_mwi() Disable Memory-Write-Invalidate transactions.
|
| /linux/Documentation/arch/powerpc/ |
| H A D | elf_hwcaps.rst | 140 User's Manual, 4.6.2.2 Instruction Cache Block Invalidate (icbi))::
|
| H A D | ultravisor.rst | 403 Invalidate the Ultravisor mapping of a page.
|
| /linux/Documentation/scsi/ |
| H A D | ncr53c8xx.rst | 75 14.4 Possible data corruption during a Memory Write and Invalidate
773 specf:3 enabled except Memory Write And Invalidate
778 Invalidate.
1436 14.4 Possible data corruption during a Memory Write and Invalidate
1442 Write and Invalidate Command at a not cache-line-aligned 4 DWORDS boundary.
1447 When this situation occurs, the chip may complete the Write and Invalidate
1451 Not using Write And Invalidate obviously gets rid of this chip bug, and so
|
| H A D | ChangeLog.ncr53c8xx | 480 . Leave use of PCI Write and Invalidate under user control.
|
| /linux/arch/sparc/mm/ |
| H A D | ultra.S | 232 stxa %g0, [%o2] ASI_DCACHE_TAG ! Invalidate TAG
|
| /linux/Documentation/filesystems/caching/ |
| H A D | backend-api.rst | 354 * Invalidate a data storage object [mandatory]::
|
| /linux/arch/arm/boot/compressed/ |
| H A D | head.S | 910 mcr p15, 0, r0, c7, c7, 0 @ Invalidate whole cache
|
| /linux/tools/perf/scripts/python/ |
| H A D | exported-sql-viewer.py | 3299 self.widget.textChanged.connect(self.Invalidate)
3326 def Invalidate(self): member in LineEditDataItem
|
| /linux/tools/arch/x86/kcpuid/ |
| H A D | cpuid.csv | 199 0x7, 0, ebx, 10, invpcid , INVPCID instruction (Invalidate Processor Context ID)
|
| /linux/Documentation/security/keys/ |
| H A D | core.rst | 820 * Invalidate a key::
|