| /linux-6.1.9/block/ |
| 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
244 clearing |= ev->clearing; in disk_clear_events()
245 ev->clearing = 0; in disk_clear_events()
248 disk_check_events(ev, &clearing); in disk_clear_events()
253 __disk_unblock_events(disk, ev->clearing ? true : false); in disk_clear_events()
[all …]
|
| /linux-6.1.9/Documentation/devicetree/bindings/powerpc/opal/ |
| 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-6.1.9/Documentation/mm/ |
| D | mmu_notifier.rst | 6 When clearing a pte/pmd we are given a choice to notify the event through
13 those secondary TLB while holding page table lock when clearing a pte/pmd:
29 If clearing the page table entry is not followed by a notify before setting
|
| /linux-6.1.9/Documentation/x86/ |
| 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:
163 sibling threads are offline CPU buffer clearing is not required.
165 The idle clearing is enabled on CPUs which are only affected by MSBDS
169 idle clearing would be a window dressing exercise and is therefore not
|
| D | tsx_async_abort.rst | 29 b) Clear CPU buffers - similar to MDS, clearing the CPU buffers mitigates this
|
| /linux-6.1.9/drivers/scsi/ |
| D | sr.c | 119 unsigned int clearing, int slot);
203 unsigned int clearing, int slot) in sr_check_events() argument
240 if (!(clearing & DISK_EVENT_MEDIA_CHANGE)) in sr_check_events()
553 unsigned int clearing) in sr_block_check_events() argument
559 return cdrom_check_events(&cd->cdi, clearing); in sr_block_check_events()
|
| /linux-6.1.9/include/linux/ |
| D | cdrom.h | 76 unsigned int clearing, int slot);
110 unsigned int clearing);
|
| /linux-6.1.9/Documentation/translations/zh_CN/admin-guide/ |
| D | index.rst | 67 clearing-warn-once
|
| /linux-6.1.9/Documentation/translations/zh_TW/admin-guide/ |
| D | index.rst | 67 clearing-warn-once
|
| /linux-6.1.9/drivers/block/paride/ |
| D | pcd.c | 176 unsigned int clearing, int slot_nr);
265 unsigned int clearing) in pcd_block_check_events() argument
268 return cdrom_check_events(&cd->info, clearing); in pcd_block_check_events()
485 unsigned int clearing, int slot_nr) in pcd_check_events() argument
|
| D | pf.c | 251 unsigned int clearing);
365 static unsigned int pf_check_events(struct gendisk *disk, unsigned int clearing) in pf_check_events() argument
|
| /linux-6.1.9/Documentation/admin-guide/hw-vuln/ |
| D | mds.rst | 109 - The processor is vulnerable and the CPU buffer clearing mitigation is
153 CPU buffer clearing
255 for the MDS vulnerability, CPU buffer clearing on exit to
306 - Enable CPU buffer clearing
|
| D | processor_mmio_stale_data.rst | 160 Kernel reuses the MDS function to invoke the buffer clearing:
200 full If the CPU is vulnerable, enable mitigation; CPU buffer clearing
231 - The processor is vulnerable and the CPU buffer clearing mitigation is
|
| /linux-6.1.9/drivers/cdrom/ |
| D | gdrom.c | 379 unsigned int clearing, int ignore) in gdrom_check_events() argument
497 unsigned int clearing) in gdrom_bdops_check_events() argument
499 return cdrom_check_events(gd.cd_info, clearing); in gdrom_bdops_check_events()
|
| /linux-6.1.9/Documentation/ABI/testing/ |
| D | sysfs-firmware-gsmi | 53 clearing though, and this writes to this file
|
| D | sysfs-class-watchdog | 107 clearing those bits does nothing for both versions of the SoC.
|
| /linux-6.1.9/drivers/firmware/google/ |
| D | Kconfig | 18 clearing the event log. If CONFIG_EFI is also enabled this
|
| /linux-6.1.9/Documentation/admin-guide/ |
| D | index.rst | 78 clearing-warn-once
|
| /linux-6.1.9/arch/sparc/lib/ |
| D | M7memset.S | 151 inccc %o3 ! byte clearing loop
187 ! initial cache-clearing stores
|
| /linux-6.1.9/Documentation/devicetree/bindings/clock/ti/ |
| D | gate.txt | 43 gates the clock and clearing the bit ungates the clock.
|
| /linux-6.1.9/Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 20 respectively __GFP_IO (note the latter implies clearing the first as well) in
|
| /linux-6.1.9/Documentation/virt/kvm/s390/ |
| D | s390-pv-boot.rst | 73 non-clearing IPL subcodes are not allowed.
|
| /linux-6.1.9/Documentation/spi/ |
| D | butterfly.rst | 44 by clearing PORTB.[0-3]); (b) configure the mtd_dataflash driver; and
|
| /linux-6.1.9/Documentation/virt/kvm/x86/ |
| D | msr.rst | 240 event and to write 1' to MSR_KVM_ASYNC_PF_ACK after clearing the location;
321 EOI by clearing the bit in guest memory - this location will
338 clearing it to signal EOI to the hypervisor,
|
| /linux-6.1.9/Documentation/s390/ |
| D | vfio-ap-locking.rst | 94 needs to access the KVM pointer only for the purposes of setting or clearing IRQ
|