| /openbmc/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
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 …]
|
| /openbmc/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
|
| /openbmc/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
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/ltrace/ltrace/ |
| H A D | 0001-Fix-type-of-single-bit-bitfields.patch | 33 * for clearing latent flag. */
39 * backend is responsible for clearing the delayed flag. See
|
| /openbmc/linux/drivers/scsi/ |
| H A D | sr.c | 119 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()
|
| /openbmc/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
|
| /openbmc/openpower-pnor-code-mgmt/vpnor/ |
| H A D | obmc-vpnor-enable-clearvolatile@.service | 2 Description=Enable the clearing of the Volatile PNOR partitions in host%I
|
| /openbmc/openbmc/meta-arm/meta-arm-systemready/recipes-test/arm-systemready-linux-distros/files/unattended-boot-conf/Fedora/ |
| H A D | ks.cfg | 28 # Partition clearing information
|
| /openbmc/qemu/target/s390x/kvm/ |
| H A D | trace-events | 5 kvm_clear_cmma(int rc) "CMMA: clearing with result code %d"
|
| /openbmc/linux/include/linux/ |
| H A D | cdrom.h | 77 unsigned int clearing, int slot);
110 unsigned int clearing);
|
| /openbmc/linux/Documentation/admin-guide/hw-vuln/ |
| 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
|
| H A 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
|
| H A 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
|
| /openbmc/qemu/tests/vm/ |
| H A D | centos-8-aarch64.ks | 11 # Partition clearing information
|
| /openbmc/linux/Documentation/translations/zh_CN/admin-guide/ |
| H A D | index.rst | 67 clearing-warn-once
|
| /openbmc/linux/Documentation/translations/zh_TW/admin-guide/ |
| H A D | index.rst | 67 clearing-warn-once
|
| /openbmc/openbmc/meta-openpower/classes/ |
| H A D | openpower-software-manager-virtual-pnor.bbclass | 13 # To handle warm reboot scenarios, the checking and clearing of
|
| /openbmc/linux/drivers/cdrom/ |
| H A 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()
|
| /openbmc/linux/arch/sparc/lib/ |
| H A D | M7memset.S | 151 inccc %o3 ! byte clearing loop
187 ! initial cache-clearing stores
|
| /openbmc/qemu/hw/misc/macio/ |
| H A D | trace-events | 36 pmu_debug_protocol_clear_treq(int state) "TREQ cleared, clearing TACK, state: %d"
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-gsmi | 53 clearing though, and this writes to this file
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | index.rst | 89 clearing-warn-once
|
| /openbmc/linux/drivers/firmware/google/ |
| H A D | Kconfig | 18 clearing the event log. If CONFIG_EFI is also enabled this
|
| /openbmc/linux/Documentation/devicetree/bindings/clock/ti/ |
| H A D | gate.txt | 43 gates the clock and clearing the bit ungates the clock.
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | gfp_mask-from-fs-io.rst | 20 respectively __GFP_IO (note the latter implies clearing the first as well) in
|