Home
last modified time | relevance | path

Searched refs:clearing (Results 1 – 25 of 92) sorted by relevance

1234

/Linux-v6.6/block/
Ddisk-events.c18 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-v6.6/Documentation/devicetree/bindings/powerpc/opal/
Dsensor-groups.txt17 operations like clearing the min/max history of all
26 sensor groups like clearing min/max, enabling/disabling sensor
/Linux-v6.6/Documentation/mm/
Dmmu_notifier.rst4 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-v6.6/drivers/scsi/
Dsr.c119 unsigned int clearing, int slot);
206 unsigned int clearing, int slot) in sr_check_events() argument
243 if (!(clearing & DISK_EVENT_MEDIA_CHANGE)) in sr_check_events()
556 unsigned int clearing) in sr_block_check_events() argument
562 return cdrom_check_events(&cd->cdi, clearing); in sr_block_check_events()
/Linux-v6.6/Documentation/arch/x86/
Dmds.rst81 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
Dtsx_async_abort.rst29 b) Clear CPU buffers - similar to MDS, clearing the CPU buffers mitigates this
/Linux-v6.6/include/linux/
Dcdrom.h77 unsigned int clearing, int slot);
110 unsigned int clearing);
/Linux-v6.6/Documentation/translations/zh_CN/admin-guide/
Dindex.rst67 clearing-warn-once
/Linux-v6.6/Documentation/translations/zh_TW/admin-guide/
Dindex.rst67 clearing-warn-once
/Linux-v6.6/Documentation/admin-guide/hw-vuln/
Dmds.rst109 - 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
Dprocessor_mmio_stale_data.rst160 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-v6.6/drivers/cdrom/
Dgdrom.c379 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-v6.6/Documentation/ABI/testing/
Dsysfs-firmware-gsmi53 clearing though, and this writes to this file
Dsysfs-class-watchdog120 clearing those bits does nothing for both versions of the SoC.
/Linux-v6.6/arch/sparc/lib/
DM7memset.S151 inccc %o3 ! byte clearing loop
187 ! initial cache-clearing stores
/Linux-v6.6/Documentation/admin-guide/
Dindex.rst89 clearing-warn-once
/Linux-v6.6/drivers/firmware/google/
DKconfig18 clearing the event log. If CONFIG_EFI is also enabled this
/Linux-v6.6/Documentation/devicetree/bindings/clock/ti/
Dgate.txt43 gates the clock and clearing the bit ungates the clock.
/Linux-v6.6/Documentation/core-api/
Dgfp_mask-from-fs-io.rst20 respectively __GFP_IO (note the latter implies clearing the first as well) in
/Linux-v6.6/Documentation/virt/kvm/s390/
Ds390-pv-boot.rst73 non-clearing IPL subcodes are not allowed.
/Linux-v6.6/Documentation/spi/
Dbutterfly.rst44 by clearing PORTB.[0-3]); (b) configure the mtd_dataflash driver; and
/Linux-v6.6/Documentation/virt/kvm/x86/
Dmsr.rst240 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-v6.6/Documentation/userspace-api/media/v4l/
Dvidioc-subdev-g-routing.rst46 setting or clearing flags of the ``flags`` field of a
/Linux-v6.6/Documentation/bpf/
Dcpumasks.rst207 3.1.1 Setting and clearing CPUs
272 In addition to setting and clearing individual CPUs in a single cpumask,
/Linux-v6.6/Documentation/arch/s390/
Dvfio-ap-locking.rst94 needs to access the KVM pointer only for the purposes of setting or clearing IRQ

1234