Home
last modified time | relevance | path

Searched full:reliably (Results 1 – 25 of 277) sorted by relevance

12345678910>>...12

/linux/Documentation/livepatch/
H A Dreliable-stacktrace.rst144 state is in an inconsistent state, it may not be possible to reliably unwind,
173 unwinder can reliably determine the original return address and no unwind state
217 location of the return address cannot be reliably determined.
249 Architectures must either ensure that unwinders either reliably unwind
305 Due to cases such as the above, it may only be possible to reliably consume a
308 reliably identify when the LR or stack value should be used (e.g. using
/linux/arch/arm/kernel/
H A Dmachine_kexec.c45 * able to kexec reliably, so fail the prepare operation. in machine_kexec_prepare()
175 * reliably kexec anyway, so BUG_ON is appropriate. in machine_kexec()
/linux/tools/perf/trace/beauty/
H A Dfadvise.sh21 # reliably process on arch FOO a perf.data file collected by 'perf trace
/linux/Documentation/userspace-api/media/v4l/
H A Dquerycap.rst31 specific applications to reliably identify the driver.
/linux/arch/mips/include/asm/
H A Dsocket.h24 * @SOCK_RDM - reliably-delivered message
/linux/arch/s390/kernel/
H A Dkexec_image.c55 /* Can't reliably tell if an image is valid. Therefore give the in s390_image_probe()
/linux/Documentation/devicetree/bindings/display/bridge/
H A Danx6345.yaml47 May be omitted if EDID works reliably.
/linux/arch/mips/cavium-octeon/
H A DKconfig9 function reliably, select this option to enable them. These
/linux/Documentation/ABI/testing/
H A Dsysfs-bus-pci-devices-cciss72 to work reliably.
/linux/arch/arm/mach-pxa/
H A Dstandby.S57 * can be reliably accessed in the code following standby.
/linux/arch/arm/mach-versatile/
H A Dplatsmp.c34 * or not. This is necessary for the hotplug code to work reliably.
/linux/mm/
H A Dhwpoison-inject.c44 * memory_failure() will redo the check reliably inside page lock. in hwpoison_inject()
/linux/arch/arm64/kernel/
H A Dsmp_spin_table.c31 * reliably.
/linux/include/asm-generic/
H A Dword-at-a-time.h57 * that is architecture-specific. If you have a reliably fast
/linux/arch/arm/mach-spear/
H A Dplatsmp.c28 * or not. This is necessary for the hotplug code to work reliably.
/linux/tools/testing/selftests/proc/
H A Dsetns-dcache.c101 /* Reliably pin dentry into dcache. */ in main()
H A Dsetns-sysvipc.c100 /* Reliably pin dentry into dcache. */ in main()
/linux/arch/arm/mach-mstar/
H A Dmstarv7.c26 * ethernet doesn't work reliably for example.
/linux/Documentation/power/
H A Ds2ram.rst70 Reason for this is that the RTC is the only reliably available piece of
/linux/drivers/pci/msi/
H A Dmsi.h76 * reliably as devices without an INTx disable bit will then generate a
/linux/include/linux/
H A Dstacktrace.h43 * stack reliably
/linux/Documentation/misc-devices/
H A Dlis3lv02d.rst49 but interrupt behaviour is not guaranteed to work reliably. In test mode, the
/linux/arch/mips/include/asm/sgi/
H A Dhpc3.h195 * the status bits. The first reg can only reliably report
197 * reliably report bits 9:5 of the hpc3 irq status. I told
/linux/drivers/iommu/iommufd/
H A Dmain.c50 * in the xarray and visible to other threads we can't reliably destroy in _iommufd_object_alloc()
69 * to reliably destroy a single object. Thus all APIs that are creating objects
/linux/drivers/media/usb/uvc/
H A Duvc_isight.c120 * reliably detected when the first packet of the new frame in uvc_video_decode_isight()

12345678910>>...12