Home
last modified time | relevance | path

Searched full:records (Results 1 – 25 of 290) sorted by relevance

12345678910>>...12

/openbmc/openbmc-test-automation/redfish/systems/
H A Dtest_thermal_ambient_temperatures.robot2 Documentation Getting the systems thermal records for temperature.
20 Get Ambient Temperature Records
21 [Documentation] Get the ambient temperature records.
23 [Template] Get Thermal Records and Verify
29 Reboot And Check Ambient Temperature Records Are Valid
30 [Documentation] Check the ambient temperature records are valid after a reboot.
39 Get Thermal Records and Verify Temperatures ReadingCelsius
44 Get Thermal Records and Verify
45 [Documentation] Get the thermal records for temperatures.
52 ${records}= Verify Valid Records ${record_type}
[all …]
H A Dtest_powersupply_readings.robot18 [Documentation] Verify there are no invalid power supply input watt records.
27 [Documentation] Verify there are no invalid power supply voltage records.
29 [Template] Verify Voltage Records
40 # records:
56 … ${records}= Verify Valid Records PowerSupplies ${REDFISH_CHASSIS_POWER_URI} EfficiencyPercent
57 ${efficiency_percentages}= Nested Get EfficiencyPercent ${records}
64 [Documentation] Verify the power watt records.
72 Verify Valid Records ${record_type} ${redfish_uri} ${reading_type}
75 Verify Voltage Records
76 [Documentation] Verify the power voltage records.
[all …]
H A Dtest_power_voltage_readings.robot17 Get Power Sensor Voltage Records
18 [Documentation] Get the power voltage records.
20 [Template] Get Voltage Records and Verify
28 Get Voltage Records and Verify
29 [Documentation] Get the power records for voltages.
37 ${records}= Redfish.Get Attribute
40 ${num_records}= Get Length ${records}
41 Rprint Vars num_records records fmt=terse
43 ${invalid_records}= Filter Struct ${records}
52 ${cmd} Catenate [x for x in ${records}
H A Dtest_power_control_metrics.robot18 [Documentation] Verify there are no invalid power control consumed watt records.
20 [Template] Verify Power Metric Records
28 Verify Power Metric Records
29 [Documentation] Verify the power metric records.
37 Verify Valid Records ${record_type} ${redfish_uri} ${reading_type}
39 ${records}= Redfish.Get Attribute ${redfish_uri} ${record_type}
42 … ... [x for x in ${records} if not x['${reading_type}'] <= x['PowerMetrics']['MaxConsumedWatts']]
/openbmc/docs/designs/
H A Dguard-on-bmc.md21 **Guard Records**: A file in the persistent storage with the list of permanently
38 These records will be created when an error is encountered on an element that
45 hardware resources in a server system. The BMC creates guard records on a
48 be controlled by BMC. The BMC retrieves the guard records for presenting to an
63 - An option should be given to list the guard records.
64 - An option should be given to delete all guard records
66 on the guard records.
70 - The guard records on the units which are owned by the host will be applied
74 - The clearing of the records after the replacement of the faulty component
75 should be done by the component owning the guard records.
[all …]
H A Dcper-records.md1 # CPER records - CPER
9 Server CPUs expose a managability interface refered to as CPER records. A user
10 outside of the BMC would like to read these records in a decoded state, rather
21 In Redfish specification drop 2021.3, Redfish added support for CPER records
27 ARM has developed a reference library for decoding CPER records that does not
38 - A BMC should be able to decode binary CPER records originated from a CPER
41 - BMC should be able to recieve and decode CPER records from a CPU per the [CPER
45 end that added records do not require manual effort to implement in each
60 this time. It is expected that the ubiquity of CPER records in the BMC ecosystem
/openbmc/openbmc/poky/scripts/tiny/
H A Ddirsize.py27 r.records.append(Record.create(pathname))
28 r.size += r.records[-1].size
29 r.records.sort(reverse=True)
39 self.records = []
46 if len(this.records) > 0 and len(that.records) == 0:
57 for r in self.records:
59 if len(self.records) == 0:
/openbmc/phosphor-power/power-supply/
H A Drecord_manager.hpp37 * This class manages the records for the input power history of
46 * from the PS, it will clear out the old records and start over.
70 * records to keep at a time
80 * records to keep at a time
99 * history records that needs to be
136 * @brief Returns the number of records
138 * @return size_t - the number of records
143 return records.size(); in getNumRecords()
147 * @brief Deletes all records
151 records.clear(); in clear()
[all …]
H A Drecord_manager.cpp37 records.clear(); in add()
46 if (!records.empty()) in add()
48 auto previousID = std::get<recIDPos>(records.front()); in add()
62 // then it was a sync so clear the old records. in add()
76 records.clear(); in add()
86 records.push_front(std::move(createRecord(rawRecord))); in add()
90 if (records.size() > maxRecords) in add()
92 records.pop_back(); in add()
107 for (const auto& r : records) in getAverageRecords()
119 for (const auto& r : records) in getMaximumRecords()
H A Dmain.cpp35 std::string records{}; in main() local
48 "-r,--num-history-records", records, in main()
49 "Number of input power history records to provide on D-Bus\n") in main()
94 // Get the number of input power history records to keep in D-Bus. in main()
96 if (!records.empty()) in main()
98 numRecords = std::stol(records); in main()
101 std::cerr << "Invalid number of history records specified.\n"; in main()
/openbmc/witherspoon-pfault-analysis/power-supply/
H A Drecord_manager.hpp37 * This class manages the records for the input power history of
46 * from the PS, it will clear out the old records and start over.
70 * records to keep at a time
78 * records to keep at a time
97 * history records that needs to be
134 * @brief Returns the number of records
136 * @return size_t - the number of records
141 return records.size(); in getNumRecords()
145 * @brief Deletes all records
149 records.clear(); in clear()
[all …]
H A Drecord_manager.cpp39 records.clear(); in add()
48 if (!records.empty()) in add()
50 auto previousID = std::get<recIDPos>(records.front()); in add()
64 // then it was a sync so clear the old records. in add()
78 records.clear(); in add()
83 records.push_front(std::move(createRecord(rawRecord))); in add()
86 if (records.size() > maxRecords) in add()
88 records.pop_back(); in add()
103 for (const auto& r : records) in getAverageRecords()
115 for (const auto& r : records) in getMaximumRecords()
H A Dmain.cpp88 // Get the number of input power history records to keep in D-Bus. in main()
90 auto records = (options)["num-history-records"]; in main() local
91 if (records != ArgumentParser::emptyString) in main()
93 numRecords = std::stol(records); in main()
96 std::cerr << "Invalid number of history records specified.\n"; in main()
/openbmc/openbmc/poky/scripts/pybootchartgui/pybootchartgui/
H A Dsamples.py80 self.records = {}
84 self.records[name] = value
87 keys = self.records.keys()
100 self.buffers = mem_sample.records['MemTotal'] - mem_sample.records['MemFree']
101 …self.used = mem_sample.records['MemTotal'] - mem_sample.records['MemFree'] - mem_sample.records['B…
102 self.cached = mem_sample.records['Cached']
103 self.swap = mem_sample.records['SwapTotal'] - mem_sample.records['SwapFree']
110 self.records = {}
113 self.records[name] = value
116 return bool(self.records)
/openbmc/phosphor-host-ipmid/app/
H A Dchannel.cpp33 /** @brief Get the supported Cipher records
35 * The cipher records are read from the JSON file and converted into
37 * records can be either OEM or standard cipher. Each json entry is parsed and
41 * @return pair of vector containing 1. all the cipher suite records. 2.
120 * - rspRecords - cipher suite records.
123 std::vector<uint8_t> // Cipher Records
161 const std::vector<uint8_t>& records = in getChannelCipherSuites() local
179 std::min(static_cast<size_t>(listIndex) * respSize, records.size()); in getChannelCipherSuites()
181 records.size()); in getChannelCipherSuites()
185 std::copy_n(records.data() + start, size, std::back_inserter(rspRecords)); in getChannelCipherSuites()
/openbmc/qemu/tests/qemu-iotests/
H A D294.out12 1+0 records in
13 1+0 records out
21 1+0 records in
22 1+0 records out
/openbmc/u-boot/include/
H A Ds_record.h11 * Motorola S-Records are an industry-standard format for
31 * 5 number of data records in preceding block
33 * 7 ending record for S3 records
34 * 8 ending record for S2 records
35 * 9 ending record for S1 records
44 * 32-bit address. The address field for S4 records is
71 * The S0 record starts the file. The S3 records contain the
/openbmc/u-boot/doc/
H A DREADME.log65 CONFIG_LOG_CONSOLE - Enable writing log records to the console
170 records that pass through the filter make it to the driver.
179 limits output to records with a level less than CONFIG_LOG_MAX_LEVEL.
189 Also debug() and error() will generate log records - these use LOG_CATEGORY
246 Add a way to browse log records
248 Add a way to record log records for browsing using an external tool
254 Allow sharing of printf format strings in log records to reduce storage size
255 for large numbers of log records
266 Passing log records through to linux (e.g. via device tree /chosen)
268 Provide a command to access the number of log records generated, and the
[all …]
/openbmc/phosphor-logging/extensions/openpower-pels/
H A Dphal_service_actions.cpp53 * @brief Helper function to create guard records.
59 * "Guarded": boolean, true to create gurad records.
136 * @brief Helper function to create deconfig records.
140 * "Deconfigured": boolean, true to create deconfigure records.
142 * libphal api is used for creating deconfigure records, which includes
195 "Deconfig: Failed to create records, exception:({EXCEPTION})", in createDeconfigRecords()
204 // Create Guard records. in createServiceActions()
206 // Create Deconfigure records. in createServiceActions()
/openbmc/qemu/docs/specs/
H A Dacpi_erst.rst6 storing error records in persistent storage for future reference
11 method for storing error records into persistent storage.
13 The format of error records is described in the UEFI specification[2],
75 - record_size: Specifies the size of the records (or slots) in the
104 The ability to clear/erase specific records allows for the formation
108 as ERST and also facilitates efficient access to the records.
111 the slot 0 header can accommodate 1021 records. Thus a storage size
114 header, and records can be stored starting at slot 2.
118 and contains N number of slots to store records. The example below
119 shows two records (in CPER format) in the backend storage, while the
[all …]
/openbmc/openpower-debug-collector/dump/tools/bmcdump/plugins/
H A Dguardlist10 desc="GUARD Records"
27 desc="Guard resolved records"
31 desc="Guard ephemeral records"
/openbmc/u-boot/common/
H A Dbootstage.c8 * This module records the progress of boot and arbitrary commands, and
45 uint32_t count; /* Number of records */
59 debug("Relocating %d records\n", data->rec_count); in bootstage_relocate()
314 printf("Timer summary in microseconds (%d records):\n", in bootstage_report()
320 /* Sort records by increasing time */ in bootstage_report()
379 /* Count the number of records, and write that value first */ in bootstage_stash()
390 /* Write the records, silently stopping when we run out of space */ in bootstage_stash()
411 debug("Stashed %d records\n", hdr->count); in bootstage_stash()
444 debug("%s: Bootstage has %d records needing %lu bytes, but " in bootstage_unstash()
457 debug("%s: Bootstage has %d records, we have space for %d\n" in bootstage_unstash()
[all …]
/openbmc/pldm/libpldmresponder/examples/fru/
H A DFRU_Master.json1 // This is the master config file for generating PLDM FRU records from the D-Bus
5 // FRU records are created in the FRU table. FRU Record Set PDR and Entity
7 // records will be created for all FRU's of type Board and CPU. The "entity_type"
/openbmc/qemu/tests/migration-stress/guestperf/
H A Dtimings.py2 # Migration test timing records
46 def __init__(self, records): argument
48 self._records = records
/openbmc/openbmc/meta-phosphor/recipes-phosphor/sel-logger/
H A Dphosphor-sel-logger_git.bb1 # SEL Logger has the ability to monitor and automatically log SEL records for
7 # Monitors and logs SEL records for threshold sensor events
9 DESCRIPTION = "Utility to write IPMI SEL records to the journal"

12345678910>>...12