/openbmc/linux/Documentation/trace/rv/ |
H A D | runtime-verification.rst | 10 Instead of relying on a fine-grained model of a system (e.g., a 12 system's actual execution, comparing it against a formal specification of 13 the system behavior. 16 behavior of the monitored system, without the pitfalls of developing models 17 that require a re-implementation of the entire system in a modeling language. 19 *online* verification of a system, enabling the *reaction* for unexpected 26 A monitor is the central part of the runtime verification of a system. The 28 undesired) behavior, and the trace of the actual system. 57 action of taking a system down to avoid the propagation of a failure. 94 monitor's ability to process them in the same system, only the *offline* [all …]
|
/openbmc/linux/Documentation/power/ |
H A D | suspend-and-interrupts.rst | 12 Device interrupt request lines (IRQs) are generally disabled during system 29 Device IRQs are re-enabled during system resume, right before the "early" phase 37 There are interrupts that can legitimately trigger during the entire system 47 interrupt will wake the system from a suspended state -- for such cases it is 67 during system sleep so as to trigger a system wakeup when needed. For example, 83 re-enabled by resume_device_irqs() during the subsequent system resume. Also 84 the PM core is notified about the event which causes the system suspend in 89 system suspend currently in progress to be aborted or wake up the system if 92 IRQs at that time, but those IRQs should not be configured for system wakeup 105 IRQ subsystem to trigger a system wakeup. [all …]
|
/openbmc/phosphor-power/phosphor-regulators/src/ |
H A D | rail.cpp | 35 void Rail::configure(Services& services, System& system, Chassis& chassis, in configure() argument 41 configuration->execute(services, system, chassis, device, *this); in configure() 45 void Rail::monitorSensors(Services& services, System& system, Chassis& chassis, in monitorSensors() argument 51 sensorMonitoring->execute(services, system, chassis, device, *this); in monitorSensors()
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/openwsman/ |
H A D | openwsman_2.7.2.bb | 4 (WS-Management) and to expose system management information on the \ 5 Linux operating system using the WS-Management protocol. WS-Management \ 8 all system management aspects. \ 59 install -d ${D}/${systemd_unitdir}/system 60 install -m 644 ${WORKDIR}/openwsmand.service ${D}/${systemd_unitdir}/system 62 sed -i -e 's,@SBINDIR@,${sbindir},g' ${D}${systemd_unitdir}/system/openwsmand.service 63 sed -i -e 's,@SYSCONFDIR@,${sysconfdir},g' ${D}${systemd_unitdir}/system/openwsmand.service 64 … sed -i -e 's,@LOCALSTATEDIR@,${localstatedir},g' ${D}${systemd_unitdir}/system/openwsmand.service
|
/openbmc/openbmc/meta-amd/meta-ethanolx/recipes-phosphor/configuration/ethanolx-yaml-config/ |
H A D | ethanolx-ipmi-fru.yaml | 2 /system/chassis/bmc: 29 /system/chassis/motherboard/cpu0: 56 /system/chassis/motherboard/cpu1: 84 /system: 95 /system/chassis/motherboard: 117 /system/chassis/motherboard/dimm0: 145 /system/chassis/motherboard/dimm1: 173 /system/chassis/motherboard/dimm2: 201 /system/chassis/motherboard/dimm3: 229 /system/chassis/motherboard/dimm4: [all …]
|
/openbmc/openbmc/meta-amd/meta-daytonax/recipes-phosphor/configuration/daytonax-yaml-config/ |
H A D | daytonax-ipmi-fru.yaml | 2 /system/chassis/bmc: 29 /system/chassis/motherboard/cpu0: 56 /system/chassis/motherboard/cpu1: 84 /system: 95 /system/chassis/motherboard: 117 /system/chassis/motherboard/dimm0: 145 /system/chassis/motherboard/dimm1: 173 /system/chassis/motherboard/dimm2: 201 /system/chassis/motherboard/dimm3: 229 /system/chassis/motherboard/dimm4: [all …]
|
/openbmc/boost-dbus/include/dbus/detail/ |
H A D | queue.hpp | 22 typedef std::function<void(boost::system::error_code, Message)> handler_type; 42 boost::system::error_code error_; 47 boost::system::error_code e = boost::system::error_code()) in closure() 68 void(boost::system::error_code, in BOOST_ASIO_INITFN_RESULT_TYPE() 72 MessageHandler, void(boost::system::error_code, message_type)> in BOOST_ASIO_INITFN_RESULT_TYPE()
|
/openbmc/openbmc/meta-facebook/recipes-fb/packagegroups/ |
H A D | packagegroup-fb-apps.bb | 11 ${PN}-system \ 21 PROVIDES += "virtual/obmc-system-mgmt" 26 RPROVIDES:${PN}-system += "virtual-obmc-system-mgmt" 57 SUMMARY:${PN}-system = "Facebook System" 58 RDEPENDS:${PN}-system = " \
|
/openbmc/linux/Documentation/hwmon/ |
H A D | max16065.rst | 53 [From datasheets] The MAX16065/MAX16066 flash-configurable system managers 54 monitor and sequence multiple system voltages. The MAX16065/MAX16066 can also 56 current-sense amplifier. The MAX16065 manages up to twelve system voltages 59 The MAX16067 flash-configurable system manager monitors and sequences multiple 60 system voltages. The MAX16067 manages up to six system voltages simultaneously. 62 The MAX16068 flash-configurable system manager monitors and manages up to six 63 system voltages simultaneously. 65 The MAX16070/MAX16071 flash-configurable system monitors supervise multiple 66 system voltages. The MAX16070/MAX16071 can also accurately monitor (+/-2.5%) 68 MAX16070 monitors up to twelve system voltages simultaneously, and the MAX16071
|
/openbmc/openbmc/poky/meta/recipes-core/glib-2.0/glib-2.0/ |
H A D | 0001-Set-host_machine-correctly-when-building-with-mingw3.patch | 22 -if host_machine.system() == 'windows' 31 -if host_machine.system() != 'windows' 36 @@ -562,7 +562,7 @@ if host_machine.system() != 'windows' 40 -if host_machine.system() == 'windows' 49 -if host_machine.system() != 'windows' 62 -if host_machine.system() == 'windows' 74 host_system = host_machine.system()
|
/openbmc/openbmc/meta-ufispace/meta-ncplite/recipes-phosphor/configuration/ncplite-yaml-config/ |
H A D | ncplite-ipmi-fru-properties.yaml | 1 /system/chassis/motherboard: 8 /system: 15 /system/chassis: 22 /system/chassis/psu0: 29 /system/chassis/psu1:
|
H A D | ncplite-ipmi-sensors.yaml | 194 path: /system/chassis/motherboard/CPU_CATERR_L 208 path: /system/chassis/motherboard/PSU0_INT_L 215 path: /system/chassis/motherboard/PSU1_INT_L 222 path: /system/chassis/motherboard/PSU0_POWER_OK 229 path: /system/chassis/motherboard/PSU1_POWER_OK 237 path: /system/chassis/motherboard/PSU0_PRSNT_L 245 path: /system/chassis/motherboard/PSU1_PRSNT_L 252 path: /system/chassis/motherboard/FAN0_PRSNT_L 259 path: /system/chassis/motherboard/FAN1_PRSNT_L 266 path: /system/chassis/motherboard/FAN2_PRSNT_L [all …]
|
/openbmc/linux/fs/efs/ |
H A D | Kconfig | 3 tristate "EFS file system support (read only)" 7 EFS is an older file system used for non-ISO9660 CD-ROMs and hard 8 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer 9 uses the XFS file system for hard disk partitions however). 15 To compile the EFS file system support as a module, choose M here: the
|
/openbmc/openbmc-tools/expectedJsonChecker/ |
H A D | README.md | 68 "/xyz/openbmc_project/inventory/system/chassis": { 110 "endpoints": ["/xyz/openbmc_project/inventory/system/chassis"] 114 "/xyz/openbmc_project/inventory/system/chassis/motherboard/fan0" 130 "endpoints": ["/xyz/openbmc_project/inventory/system/chassis"] 151 "endpoints": ["/xyz/openbmc_project/inventory/system/chassis"] 171 "endpoints": ["/xyz/openbmc_project/inventory/system/chassis"] 195 "endpoints": ["/xyz/openbmc_project/inventory/system/chassis"] 219 "endpoints": ["/xyz/openbmc_project/inventory/system/chassis"] 253 "/xyz/openbmc_project/inventory/system": { 265 "/xyz/openbmc_project/inventory/system/chassis": { [all …]
|
/openbmc/openbmc/meta-ibm/meta-romulus/recipes-phosphor/configuration/romulus-yaml-config/ |
H A D | romulus-ipmi-fru.yaml | 2 /system/chassis/motherboard/cpu0: 29 /system/chassis/motherboard/cpu1: 57 /system: 68 /system/chassis/motherboard: 90 /system/chassis/motherboard/dimm0: 118 /system/chassis/motherboard/dimm1: 146 /system/chassis/motherboard/dimm2: 174 /system/chassis/motherboard/dimm3: 202 /system/chassis/motherboard/dimm4: 230 /system/chassis/motherboard/dimm5: [all …]
|
/openbmc/telemetry/tests/src/ |
H A D | test_trigger.cpp | 123 Matcher<boost::system::error_code> ec = 124 Eq(boost::system::errc::success); 186 Eq(boost::system::errc::success)); in TEST_F() 197 Eq(boost::system::errc::success)); in TEST_F() 215 Eq(boost::system::errc::success)); in TEST_F() 228 Eq(boost::system::errc::success)); in TEST_F() 310 Eq(boost::system::errc::success)); in TEST_F() 321 Eq(boost::system::errc::success)); in TEST_F() 413 EXPECT_THAT(ec, Eq(boost::system::errc::success)); in TEST_F() 423 EXPECT_THAT(ec, Eq(boost::system::errc::success)); in TEST_F() [all …]
|
/openbmc/openbmc/meta-ibm/recipes-phosphor/fans/phosphor-fan-monitor-config/swift/ |
H A D | monitor.yaml | 2 - inventory: /system/chassis/motherboard/fan0 11 - inventory: /system/chassis/motherboard/fan1 20 - inventory: /system/chassis/motherboard/fan2 29 - inventory: /system/chassis/motherboard/fan3
|
/openbmc/phosphor-fan-presence/monitor/ |
H A D | main.cpp | 75 System system(mode, bus, event); in main() local 79 phosphor::fan::JsonConfig config(std::bind(&System::start, &system)); in main() 85 &system, std::placeholders::_1, in main() 92 std::bind(&System::dumpDebugData, &system, std::placeholders::_1, in main() 97 system.start(); in main()
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/directfb/directfb/ |
H A D | 0001-os-linux-Fix-build-when-__NR_futex-is-not-available.patch | 14 lib/direct/os/linux/glibc/system.c | 8 ++++++-- 17 diff --git a/lib/direct/os/linux/glibc/system.c b/lib/direct/os/linux/glibc/system.c 19 --- a/lib/direct/os/linux/glibc/system.c 20 +++ b/lib/direct/os/linux/glibc/system.c 30 #include <direct/system.h>
|
/openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
H A D | chassis.md | 5 A chassis within the system. 9 rack-mounted system, each drawer may correspond to a chassis. 19 … | Chassis number within the system. Chassis numbers start at 1 because chassis 0 represent… 20 …z/openbmc_project/inventory". Specify the relative path below the root, such as "system/chassis". | 29 "inventory_path": "system/chassis",
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/User/ |
H A D | README.md | 16 - CreateUser - To create new user to the system. 17 - RenameUser - To rename existing user to new name in the system. 21 - AllGroups - To list all the groups supported in the system. 22 - AllPrivileges - To list all the privileges supported in the system. 26 - UserRenamed - Signal sent out when user is renamed in the system. 43 system under object path `/xyz/openbmc_project/user/<user name>`. Each user 60 - Delete - To delete the user object in the system.
|
/openbmc/linux/Documentation/admin-guide/cgroup-v1/ |
H A D | cpuacct.rst | 18 the system. /sys/fs/cgroup/tasks lists the tasks in this cgroup. 21 in the system. 35 CPU time obtained by the cgroup into user and system times. Currently 39 system: Time spent by tasks of the cgroup in kernel mode. 41 user and system are in USER_HZ unit. 44 system times. This has two side effects: 46 - It is theoretically possible to see wrong values for user and system times. 49 - It is possible to see slightly outdated values for user and system times
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools/ |
H A D | adbd.mk | 5 VPATH += $(SRCDIR)/system/core/adb 23 VPATH += $(SRCDIR)/system/core/liblog 31 VPATH += $(SRCDIR)/system/core/fs_mgr 35 VPATH += $(SRCDIR)/system/core/libcutils 105 VPATH += $(SRCDIR)/system/extras/ext4_utils 131 CFLAGS += -I$(SRCDIR)/system/core/adb 132 CFLAGS += -I$(SRCDIR)/system/core/include 133 CFLAGS += -I$(SRCDIR)/system/core/libsparse/include 134 CFLAGS += -I$(SRCDIR)/system/extras/ext4_utils 135 CFLAGS += -I$(SRCDIR)/system/core/fs_mgr/include
|
/openbmc/openbmc/meta-ibm/meta-system1/recipes-phosphor/packagegroups/ |
H A D | packagegroup-obmc-apps.bbappend | 2 ${PN}-system \ 6 virtual/obmc-system-mgmt \ 10 RPROVIDES:${PN}-system += "virtual-obmc-system-mgmt"
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/Security/ |
H A D | RestrictionMode.interface.yaml | 26 Indicate that system is in provisioning mode and all commands 27 are allowed in system interface in both pre and post BIOS boot. 30 Commands in the allowlist will only be executed through system 35 Commands through system interface are executed only till BIOS 36 POST complete notification, after which system interface
|