| /openbmc/openpower-occ-control/ |
| H A D | occ_errors.cpp | 62 if (!watching) in addWatch()
74 watching = true; in addWatch()
81 if (watching) in removeWatch()
94 watching = false; in removeWatch()
|
| H A D | occ_errors.hpp | 114 bool watching = false; member in open_power::occ::Error
|
| H A D | powermode.cpp | 1094 watching = false; in openIpsFile()
1107 if ((!watching) && poll) in addIpsWatch()
1130 watching = false; in removeIpsWatch()
1164 watching = true; in registerIpsStatusCallBack()
1195 if (watching) in analyzeIpsEvent()
|
| H A D | powermode.hpp | 395 bool watching = false; member in open_power::occ::powermode::PowerMode
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-inotify_git.bb | 1 SUMMARY = "An adapter to Linux kernel support for inotify directory-watching."
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/watchdog/ |
| H A D | phosphor-watchdog_git.bb | 33 # For now, watching PowerOn is the only usecase
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | entry.rst | 22 for entry code before RCU starts watching and exit code after RCU stops
23 watching. In addition, many architectures must save and restore register state,
140 already be watching. Lockdep and tracing have to be updated unconditionally.
|
| H A D | errseq.rst | 115 to do a one-off job for him. He's not really watching the worker
|
| /openbmc/linux/Documentation/trace/ |
| H A D | ftrace-uses.rst | 34 RCU is watching. These are explained below.
148 protection, it is best to make sure that RCU is "watching", otherwise
210 where RCU is "watching". This is required if the callback function
213 RCU stops watching when the system goes idle, the time when a CPU
|
| /openbmc/linux/Documentation/sound/cards/ |
| H A D | bt87x.rst | 23 you want to do is just watching TV...
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | debugfs-cros-ec | 50 system due to a timeout when watching for SLP_S0 transitions.
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | iostats.rst | 41 if you are watching a known, small set of disks. ``/proc/diskstats`` may
42 be a better choice if you are watching a large number of disks because
|
| H A D | reporting-regressions.rst | 378 Regzbot works by watching for replies to reports of tracked regressions.
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A D | cache-policies.rst | 22 for each tick. The core ticks by watching bios complete, and so
|
| /openbmc/linux/drivers/staging/greybus/Documentation/ |
| H A D | sysfs-bus-greybus | 208 process watching the file will be woken up, and the new
|
| /openbmc/linux/Documentation/driver-api/media/drivers/ |
| H A D | dvb-usb.rst | 301 but watching a channel while recording another channel on the same
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | eeh-pci-error-recovery.rst | 293 trigger any user-space daemon that was watching /sysfs,
|
| /openbmc/linux/Documentation/process/ |
| H A D | handling-regressions.rst | 375 Regzbot is watching the most important Linux mailing lists as well as the git
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | debugging.rst | 1207 - When adding new packages, it is worth watching for undesirable items
|
| /openbmc/linux/init/ |
| H A D | Kconfig | 531 dynticks systems. This accounting is implemented by watching every
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | path-lookup.rst | 637 and carefully watching where it is, to be sure it doesn't trip. If it
|
| /openbmc/linux/Documentation/ |
| H A D | memory-barriers.txt | 1641 But please note that the compiler is also closely watching what you
|
| /openbmc/linux/Documentation/RCU/Design/Requirements/ |
| H A D | Requirements.rst | 2628 not watching. This means that synchronize_rcu() is insufficient, and
|