Searched refs:Invalidate (Results 1 – 14 of 14) sorted by relevance
| /Linux-v5.10/arch/arm/mm/ |
| D | proc-xscale.S | 215 mcrne p15, 0, ip, c7, c5, 0 @ Invalidate I cache & BTB
237 mcrne p15, 0, r0, c7, c5, 1 @ Invalidate I cache line
239 mcr p15, 0, r0, c7, c6, 1 @ Invalidate D cache line
244 mcrne p15, 0, ip, c7, c5, 6 @ Invalidate BTB
268 mcr p15, 0, r0, c7, c5, 0 @ Invalidate I cache & BTB
285 mcr p15, 0, r0, c7, c5, 1 @ Invalidate I cache entry
290 mcr p15, 0, r0, c7, c5, 6 @ Invalidate BTB
311 mcr p15, 0, r0, c7, c5, 0 @ Invalidate I cache & BTB
473 mcr p15, 0, ip, c7, c5, 0 @ Invalidate I cache & BTB
|
| D | Kconfig | 996 bool "PL310 errata: Clean & Invalidate maintenance operations do not invalidate clean lines"
999 Invalidate maintenance operations: by Physical Address
1008 bool "PL310 errata: Background Clean & Invalidate by Way operation can cause data corruption"
1010 PL310 implements the Clean & Invalidate by Way L2 cache maintenance
1015 Invalidate by Way operation. Revisions prior to r3p1 are affected by
|
| /Linux-v5.10/arch/arc/kernel/ |
| D | head.S | 40 bclr r5, r5, 6 ; Invalidate (discard w/o wback)
|
| /Linux-v5.10/Documentation/admin-guide/device-mapper/ |
| D | era.rst | 91 - Invalidate those blocks in the caching software
|
| /Linux-v5.10/Documentation/PCI/ |
| D | pci.rst | 225 If the PCI device can use the PCI Memory-Write-Invalidate transaction,
229 or chip-sets may support Memory-Write-Invalidate. Alternatively,
485 pci_set_mwi() Enable Memory-Write-Invalidate transactions.
486 pci_clear_mwi() Disable Memory-Write-Invalidate transactions.
|
| /Linux-v5.10/Documentation/scsi/ |
| 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
|
| D | ChangeLog.ncr53c8xx | 480 . Leave use of PCI Write and Invalidate under user control.
|
| /Linux-v5.10/Documentation/userspace-api/ |
| D | iommu.rst | 27 3. Invalidate IOMMU caches upon guest requests
|
| /Linux-v5.10/arch/sparc/mm/ |
| D | ultra.S | 232 stxa %g0, [%o2] ASI_DCACHE_TAG ! Invalidate TAG
|
| /Linux-v5.10/arch/arm/boot/compressed/ |
| D | head.S | 897 mcr p15, 0, r0, c7, c7, 0 @ Invalidate whole cache
|
| /Linux-v5.10/Documentation/filesystems/caching/ |
| D | backend-api.rst | 318 * Invalidate data object [mandatory]::
|
| /Linux-v5.10/Documentation/powerpc/ |
| D | ultravisor.rst | 403 Invalidate the Ultravisor mapping of a page.
|
| /Linux-v5.10/tools/perf/scripts/python/ |
| D | exported-sql-viewer.py | 3289 self.widget.textChanged.connect(self.Invalidate)
3316 def Invalidate(self): member in LineEditDataItem
|
| /Linux-v5.10/Documentation/security/keys/ |
| D | core.rst | 820 * Invalidate a key::
|
