| /linux/block/ |
| H A D | disk-events.c | 18 unsigned int clearing; /* events being cleared */ member
159 ev->clearing |= mask; in disk_flush_events()
188 unsigned int clearing = *clearing_ptr; in disk_check_events() local
193 events = disk->fops->check_events(disk, clearing); in disk_check_events()
200 *clearing_ptr &= ~clearing; in disk_check_events()
231 unsigned int clearing = mask; in disk_clear_events() local
239 * store the union of mask and ev->clearing on the stack so that the in disk_clear_events()
240 * race with disk_flush_events does not cause ambiguity (ev->clearing in disk_clear_events()
244 clearing |= ev->clearing; in disk_clear_events()
245 ev->clearing = 0; in disk_clear_events()
[all …]
|
| H A D | badblocks.c | 335 * Clearing a bad blocks range from the bad block table has similar idea as
337 * when the clearing range hits middle of a bad block range, the existing bad
341 * clearing bad blocks range is naming with prefix C)
343 * 1) A clearing range is not overlapped to any already set ranges in bad block
353 * 2) The clearing range hits middle of an already setting bad blocks range in
366 * 3) The clearing range starts exactly at same LBA as an already set bad block range
390 * 4) The clearing range exactly ends at same LBA as an already set bad block
404 * 5) The clearing range is partially overlapped with an already set bad block
406 * 5.1) The already set bad block range is front overlapped with the clearing
414 * For such situation, the clearing range C can be treated as two parts. The
[all …]
|
| /linux/tools/testing/selftests/powerpc/dexcr/ |
| H A D | dexcr_test.c | 32 "clearing aspect across exec not applied"); in dexcr_prctl_onexec_test_child()
35 "clearing aspect across exec not inherited"); in dexcr_prctl_onexec_test_child()
37 FAIL_IF_EXIT_MSG(aspect & dexcr, "clearing aspect across exec did not take effect"); in dexcr_prctl_onexec_test_child()
87 FAIL_IF_MSG(aspect & mfspr(SPRN_DEXCR_RO), "clearing aspect did not take effect"); in dexcr_prctl_aspect_test()
158 "clearing aspect on exec not copied across fork"); in dexcr_prctl_aspect_test()
161 "clearing aspect on exec wrongly applied to fork"); in dexcr_prctl_aspect_test()
|
| /linux/Documentation/arch/x86/ |
| H A D | mds.rst | 81 clearing. Either the modified VERW instruction or via the L1D Flush
94 The kernel provides a function to invoke the buffer clearing:
179 sibling threads are offline CPU buffer clearing is not required.
181 The idle clearing is enabled on CPUs which are only affected by MSBDS
185 idle clearing would be a window dressing exercise and is therefore not
|
| /linux/Documentation/devicetree/bindings/powerpc/opal/ |
| H A D | sensor-groups.txt | 17 operations like clearing the min/max history of all
26 sensor groups like clearing min/max, enabling/disabling sensor
|
| /linux/drivers/net/wwan/iosm/ |
| H A D | iosm_ipc_pm.c | 99 /* Complete all memory stores before clearing bit */ in ipc_pm_wait_for_device_active()
107 /* Complete all memory stores after clearing bit */ in ipc_pm_wait_for_device_active()
319 /* Complete all memory stores before clearing bit */ in ipc_pm_init()
324 /* Complete all memory stores after clearing bit */ in ipc_pm_init()
|
| /linux/kernel/bpf/ |
| H A D | range_tree.c | 147 /* Overlaps with the entire clearing range */ in range_tree_clear()
162 /* Overlaps with the left side of the clearing range */ in range_tree_clear()
167 /* Overlaps with the right side of the clearing range */ in range_tree_clear()
173 /* in the middle of the clearing range */ in range_tree_clear()
|
| /linux/drivers/net/ipa/ |
| H A D | ipa_interrupt.c | 88 * away, "to avoid clearing unhandled interrupts." in ipa_interrupt_process()
95 /* Clearing the SUSPEND_TX interrupt also clears the in ipa_interrupt_process()
97 * caused the interrupt, so defer clearing until after in ipa_interrupt_process()
146 dev_dbg(dev, "clearing disabled IPA interrupts 0x%08x\n", in ipa_isr_thread()
|
| /linux/Documentation/mm/ |
| H A D | mmu_notifier.rst | 4 When clearing a pte/pmd we are given a choice to notify the event through
11 those secondary TLB while holding page table lock when clearing a pte/pmd:
27 If clearing the page table entry is not followed by a notify before setting
|
| /linux/include/uapi/linux/ |
| H A D | dm-log-userspace.h | 88 * dm_ulog_request to the kernel - setting the 'error' field and clearing
220 * dm_ulog_request to the kernel - setting the 'error' field and clearing
239 * dm_ulog_request to the kernel - setting the 'error' field and clearing
258 * dm_ulog_request to the kernel - setting the 'error' field and clearing
295 * dm_ulog_request to the kernel - setting the 'error' field and clearing
|
| /linux/arch/arm/mach-berlin/ |
| H A D | platsmp.c | 20 * There are two reset registers, one with self-clearing (SC)
21 * reset and one with non-self-clearing reset (NON_SC).
|
| /linux/arch/x86/lib/ |
| H A D | clear_page_64.S | 117 * so we can just go to the tail clearing to
120 * The unrolled case might end up clearing
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | mds.rst | 119 - The processor is vulnerable and the CPU buffer clearing mitigation is
145 CPU buffer clearing
247 for the MDS vulnerability, CPU buffer clearing on exit to
298 - Enable CPU buffer clearing
|
| H A D | reg-file-data-sampling.rst | 72 on If the CPU is vulnerable, enable mitigation; CPU buffer clearing
98 - The processor is vulnerable and the CPU buffer clearing mitigation is
|
| /linux/drivers/mfd/ |
| H A D | 88pm886.c | 65 /* Set interrupt clearing mode to clear on write. */ in pm886_setup_irq()
70 dev_err(dev, "Failed to set interrupt clearing mode: %d\n", err); in pm886_setup_irq()
|
| /linux/arch/mips/pci/ |
| H A D | pci-ip32.c | 71 printk("MACEPCI: Signaled target abort (clearing)\n"); in macepci_error()
75 printk("MACEPCI: Interrupt test triggered (clearing)\n"); in macepci_error()
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-watchdog | 117 Clearing the boot code selection and timeout counter also
120 clearing those bits does nothing for both versions of the SoC.
|
| /linux/drivers/rtc/ |
| H A D | rtc-fsl-ftm-alarm.c | 90 * the TOF bit, the process of clearing the TOF bit in ftm_irq_acknowledge()
99 * In one word: software clearing TOF bit not works when in ftm_irq_acknowledge()
103 * The workaround is clearing TOF bit until it works in ftm_irq_acknowledge()
|
| /linux/drivers/gpu/drm/xe/tests/ |
| H A D | xe_migrate.c | 111 if (!sanity_fence_failed(xe, fence, big ? "Clearing remote big bo" : in test_copy()
112 "Clearing remote small bo", test)) { in test_copy()
281 kunit_info(test, "Clearing small buffer object\n"); in xe_migrate_sanity_test()
286 if (sanity_fence_failed(xe, fence, "Clearing small bo", test)) in xe_migrate_sanity_test()
303 kunit_info(test, "Clearing big buffer object\n"); in xe_migrate_sanity_test()
308 if (sanity_fence_failed(xe, fence, "Clearing big bo", test)) in xe_migrate_sanity_test()
|
| /linux/kernel/trace/ |
| H A D | trace_recursion_record.c | 37 /* nr_records is -1 when clearing records */ in ftrace_record_recursion()
91 * It's still possible that we could race with the clearing in ftrace_record_recursion()
|
| /linux/fs/btrfs/ |
| H A D | fs.c | 176 "clearing incompat feature flag for %s (0x%llx)", in __btrfs_clear_fs_incompat()
222 "clearing compat-ro feature flag for %s (0x%llx)", in __btrfs_clear_fs_compat_ro()
|
| /linux/Documentation/admin-guide/ |
| H A D | clearing-warn-once.rst | 1 Clearing WARN_ONCE
|
| /linux/arch/x86/kernel/ |
| H A D | irq.c | 385 * for checking and clearing posted interrupt request (PIR), a 256 bit field
404 * as much as possible. e.g. when making a copy and clearing the PIR
458 * after clearing the outstanding notification bit. Hence, at most in DEFINE_IDTENTRY_SYSVEC()
473 * There could be a race of PI notification and the clearing of ON bit, in DEFINE_IDTENTRY_SYSVEC()
|
| /linux/arch/microblaze/kernel/ |
| H A D | setup.c | 111 /* Move ROMFS out of BSS before clearing it */ in machine_early_init()
118 /* clearing bss section */ in machine_early_init()
|
| /linux/drivers/irqchip/ |
| H A D | irq-aspeed-scu-ic.c | 95 * operation from clearing the status bits, they should be under the in aspeed_scu_ic_irq_mask()
110 * operation from clearing the status bits, they should be under the in aspeed_scu_ic_irq_unmask()
|