Searched full:harmful (Results 1 – 25 of 43) sorted by relevance
12
56 volatile-considered-harmful
5 :Original: :ref:`Documentation/process/volatile-considered-harmful.rst
58 volatile-considered-harmful
7 :Original: :ref:`Documentation/process/volatile-considered-harmful.rst
61 volatile-considered-harmful
3 :Original: :ref:`Documentation/process/volatile-considered-harmful.rst <volatile_considered_harmful…
71 volatile-considered-harmful
52 offensive, or harmful.
11 Linux kernel module or driver to be harmful and undesirable. We have
50 unnecessary - and potentially harmful.
78 just as harmful as premature optimization. Abstraction should be used to
29 * into a control dependency and consequently allowing for harmful
38 https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/
20 different type. This prevents unpredictable, potentially harmful,
22 used in the system. Using another frequency may cause harmful effects
167 * being traced, the "move t0, ra" is not harmful.
52 There are two key factors for a harmful false sharing:
30 * I found it harmful because the mismatch resulted in a new in __dso_id__cmp()
56 * decrements are not harmful as the reference count still stays in the
193 * method which should not be harmful. in rockchip_pcie_phy_power_on()
386 * being traced, the MOV is not harmful given x9 is not live per the AAPCS.
568 * the hope that the core is doing nothing harmful & in cps_cleanup_dead_cpu()
148 patched state. This may be harmful to the system though. Sending a fake signal
576 * writing this data shouldn't be harmful even in those cases.
491 * harmful in general. in dma_get_required_mask()
