Home
last modified time | relevance | path

Searched +full:event +full:- +full:specific (Results 1 – 25 of 1076) sorted by relevance

12345678910>>...44

/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DEvent.v1_11_1.json2 "$id": "http://redfish.dmtf.org/schemas/v1/Event.v1_11_1.json",
3 "$ref": "#/definitions/Event",
4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
37 "description": "Details for a CPER section or record associated with an event.",
38 …his object shall contain the details for a CPER section or record that is the source of an event.",
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
H A DLogEntry.v1_19_0.json4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
57 … "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
68 …operties contained in this object shall conform to the Redfish Specification-described requirement…
74 … "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
118 …"longDescription": "This Redfish Specification-described type shall contain links to resources tha…
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A DEvent.v1_11_1.json2 "$id": "http://redfish.dmtf.org/schemas/v1/Event.v1_11_1.json",
3 "$ref": "#/definitions/Event",
4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
37 "description": "Details for a CPER section or record associated with an event.",
38 …his object shall contain the details for a CPER section or record that is the source of an event.",
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
H A DLogEntry.v1_19_0.json4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
57 … "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
68 …operties contained in this object shall conform to the Redfish Specification-described requirement…
74 … "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
118 …"longDescription": "This Redfish Specification-described type shall contain links to resources tha…
[all …]
/openbmc/phosphor-buttons/inc/
H A Dbutton_interface.hpp7 #include <phosphor-logging/elog-errors.hpp>
13 ButtonIface(sdbusplus::bus_t& bus, EventPtr& event, ButtonConfig& buttonCfg, in ButtonIface() argument
15 bus(bus), event(event), config(buttonCfg), callbackHandler(handler) in ButtonIface()
17 int ret = -1; in ButtonIface()
44 * @brief This method is called from sd-event provided callback function
45 * callbackHandler if platform specific event handling is needed then a
46 * derived class instance with its specific evend handling logic along with
47 * init() function can be created to override the default event handling.
57 buttonIface->handleEvent(es, fd, revents); in EventHandler()
70 * @brief oem specific initialization can be done under init function.
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Logging/
H A DIPMI.interface.yaml2 Implement to provide an IPMI System Event Log (SEL) logging interface under
5 SEL records store system event information and will contain a record ID and
6 type followed by type-specific information. The type-specific information
8 adding the SEL record), sensor number, event direction and event-specific
12 events it requires a generator ID (0x20 for BMC), sensor D-Bus path, event
13 direction (assertion or de-assertion), and event specific data. For OEM type
19 - name: IpmiSelAdd
21 Log a system event record type SEL entry.
23 - name: Message
26 The text to log for the event.
[all …]
/openbmc/linux/Documentation/devicetree/bindings/perf/
H A Driscv,pmu.yaml1 # SPDX-License-Identifier: BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: RISC-V SBI PMU events
10 - Atish Patra <atishp@rivosinc.com>
18 The platform must provide information about PMU event to counter mappings
19 either via device tree or another way, specific to the platform.
20 Without the event to counter mappings, the SBI PMU extension cannot be used.
22 Platforms should provide information about the PMU event selector values
24 MHPMCOUNTERx for that specific event. The can either be done via device tree
[all …]
/openbmc/linux/Documentation/timers/
H A Dhighres.rst8 https://www.kernel.org/doc/ols/2006/ols2006v1-pages-333-346.pdf
11 http://www.cs.columbia.edu/~nahum/w6998/papers/ols2006-hrtimers-slides.pdf
18 Note: the paper and the slides are talking about "clock event source", while we
19 switched to the name "clock event devices" in meantime.
23 - hrtimer base infrastructure
24 - timeofday and clock source management
25 - clock event management
26 - high resolution timer functionality
27 - dynamic ticks
31 ---------------------------
[all …]
/openbmc/linux/drivers/perf/
H A Dfsl_imx9_ddr_perf.c1 // SPDX-License-Identifier: GPL-2.0
32 * 32bit counters monitor counter-specific events in addition to counting reference events
75 {.compatible = "fsl,imx93-ddr-pmu", .data = &imx93_devtype_data},
86 return sysfs_emit(page, "%s\n", pmu->devtype_data->identifier); in ddr_perf_identifier_show()
106 return cpumap_print_to_pagebuf(true, buf, cpumask_of(pmu->cpu)); in ddr_perf_cpumask_show()
127 return sysfs_emit(page, "event=0x%02llx\n", pmu_attr->id); in ddr_pmu_event_show()
137 /* counter0 cycles event */
161 /* counter1 specific events */
171 /* counter2 specific events */
183 /* counter3 specific events */
[all …]
/openbmc/linux/include/uapi/linux/
H A Dnfc.h14 * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
33 * enum nfc_commands - supported nfc commands
49 * @NFC_EVENT_TARGETS_FOUND: event emitted when a new target is found
51 * @NFC_EVENT_DEVICE_ADDED: event emitted when a new device is registred
54 * @NFC_EVENT_DEVICE_REMOVED: event emitted when a device is removed
56 * @NFC_EVENT_TM_ACTIVATED: event emitted when the adapter is activated in
58 * @NFC_EVENT_DEVICE_DEACTIVATED: event emitted when the adapter is deactivated
62 * a device. LTO must be set before the link is up otherwise -EINPROGRESS
65 * If one of the passed parameters is wrong none is set and -EINVAL is
67 * @NFC_CMD_ENABLE_SE: Enable the physical link to a specific secure element.
[all …]
/openbmc/intel-ipmi-oem/docs/
H A DIntel_IPMI_Platform_Events.md3 In many cases Manufacturers-specific IPMI Platfrom Events are stored in binary
4 form in System Event Log making it very difficult to easily understand platfrom
8 events originating from Intel Management Engine (ME) is used as a case-study.
9 General design of the solution is followed by tailored-down implementation for
14 - **IPMI** - Intelligent Platform Management Interface; standarized binary
16 - **Platform Event** - specific type of IPMI binary payload, used for encoding
17 and sending asynchronous one-way messages to recipient `[1]-29.3`
18 - **ME** - Intel Management Engine, autonomous subsystem used for remote
20 - **Redfish** - modern datacenter management protocol, built around REST
22 - **OpenBMC** - open-source BMC implementation with Redfish-oriented interface
[all …]
/openbmc/phosphor-debug-collector/
H A Dwatch.hpp6 #include <systemd/sd-event.h>
19 // User specific call back function input map(path:event) type.
22 // User specific callback function wrapper type.
29 * The inotify watch is hooked up with sd-event, so that on call back,
36 /** @brief ctor - hook inotify watch with sd-event
38 * @param[in] eventObj - Event loop object
39 * @param[in] flags - inotify flags
40 * @param[in] mask - Mask of events
41 * @param[in] events - Events to be watched
42 * @param[in] path - File path to be watched
[all …]
/openbmc/linux/Documentation/admin-guide/perf/
H A Dcxl.rst1 .. SPDX-License-Identifier: GPL-2.0
12 the devices. The specification provides event definitions for all CXL protocol
28 In common with other CXL bus devices, the id has no specific meaning and the
29 relationship to specific CXL device should be established via the device parent
34 The "format" directory describes all formats of the config (event vendor id,
40 bit of the event mask set. More general events may be enable by setting
53 cxl_pmu_mem0.0/clock_ticks/ [Kernel PMU event]
54 cxl_pmu_mem0.0/d2h_req_rdshared/ [Kernel PMU event]
55 cxl_pmu_mem0.0/h2d_req_snpcur/ [Kernel PMU event]
56 cxl_pmu_mem0.0/h2d_req_snpdata/ [Kernel PMU event]
[all …]
H A Dxgene-pmu.rst2 APM X-Gene SoC Performance Monitoring Unit (PMU)
5 X-Gene SoC PMU consists of various independent system device PMUs such as
12 -----------------
14 The xgene-pmu driver registers several perf PMU drivers. Each of the perf
18 The "format" directory describes format of the config (event ID),
20 directory provides configuration templates for all supported event types that
21 can be used with perf tool. For example, "l3c0/bank-fifo-full/" is an
24 Most of the SoC PMU has a specific list of agent ID used for monitoring
25 performance of a specific datapath. For example, agents of a L3 cache can be
26 a specific CPU or an I/O bridge. Each PMU has a set of 2 registers capable of
[all …]
/openbmc/openpower-proc-control/extensions/phal/
H A Dclock_logger.hpp8 * http://www.apache.org/licenses/LICENSE-2.0
13 * See the License for the specific language governing permissions and
27 /* Dbus event timer */
31 * @class Manager - Represents the clock daily management functions
48 * @param[in] event - sdeventplus event loop
50 Manager(const sdeventplus::Event& event);
68 * @brief Add processor specific CFAM data to daily logger.
70 * @param[in] proc - pdbg processor target
71 * @param[out] ffdcData - reference to clock data log
77 * @brief Add clock specific register data to daily logger.
[all …]
/openbmc/linux/tools/perf/Documentation/
H A Dperf-list.txt1 perf-list(1)
5 ----
6 perf-list - List all symbolic event types
9 --------
11 'perf list' [--no-desc] [--long-desc]
15 -----------
16 This command displays the symbolic event types which can be selected in the
17 various perf commands with the -e option.
20 -------
21 -d::
[all …]
/openbmc/phosphor-gpio-monitor/
H A DREADME.md5 ### `phosphor-gpio-monitor`
12 ### `phosphor-multi-gpio-monitor`
14 This daemon accepts command line parameter as a well-defined GPIO configuration
20 New implementation (phosphor-multi-gpio-monitor) provides multiple gpio line
21 monitoring in single instance of phosphor-mult
[all...]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Dump/
H A DCreate.interface.yaml7 /xyz/openbmc_project/dump/<dump type>. On multi-host or on multi-BMC systems
9 /xyz/openbmc_project/dump/<dump type><instance-id>.
12 - name: CreateDump
16 - name: AdditionalData
20 this case should be an implementation specific enum defined for
21 the specific type of dump either in xyz or in a domain. The
23 enum-format string is required to come from a parallel class
24 with this specific Enum name. All of the Enum strings should be
34 - name: Path
41 - xyz.openbmc_project.Common.File.Error.Open
[all …]
/openbmc/linux/Documentation/devicetree/bindings/pci/
H A Dsnps,dw-pcie.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
16 # Please create a separate DT-schema for your DWC PCIe Root Port controller
17 # and make sure it's assigned with the vendor-specific compatible string.
21 const: snps,dw-pcie
23 - compatible
[all …]
/openbmc/linux/drivers/scsi/mpt3sas/
H A Dmpt3sas_trigger_diag.h7 * Copyright (C) 2012-2014 LSI Corporation
8 * Copyright (C) 2013-2014 Avago Technologies
9 * (mailto: MPT-FusionLinux.pdl@avagotech.com)
24 * LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT,
43 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
72 /* fake firmware event for trigger */
82 * 4. Device Remove Event sent by FW
90 * struct SL_WH_EVENT_TRIGGER_T - Definition of an event trigger element
91 * @EventValue: Event Code to trigger on
92 * @LogEntryQualifier: Type of FW event that logged (Log Entry Added Event only)
[all …]
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DNet-SNMP1 ---- Part 1: CMU/UCD copyright notice: (BSD like) -----
5 …Derivative Work - 1996, 1998-2000 Copyright 1996, 1998-2000 The Regents of the University of Calif…
9 …rtising or publicity pertaining to distribution of the software without specific written permissio…
11 …E, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE R…
13 ---- Part 2: Networks Associates Technology, Inc copyright notice (BSD) -----
15 Copyright (c) 2001-2003, Networks Associates Technology, Inc All rights reserved. Redistribution an…
19 … used to endorse or promote products derived from this software without specific prior written per…
21 …ERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGH…
23 ---- Part 3: Cambridge Broadband Ltd. copyright notice (BSD) -----
25 Portions of this code are copyright (c) 2001-2003, Cambridge Broadband Ltd. All rights reserved. Re…
[all …]
/openbmc/linux/Documentation/driver-api/surface_aggregator/
H A Dclient.rst1 .. SPDX-License-Identifier: GPL-2.0+
35 client-api
45 are non-discoverable and instead need to be explicitly provided by some
49 Non-SSAM Client Drivers
53 representing that EC to the kernel. Drivers targeting a non-SSAM device (and
67 .. code-block:: c
73 ctrl = ssam_client_bind(&pdev->dev);
75 return PTR_ERR(ctrl) == -ENODEV ? -EPROBE_DEFER : PTR_ERR(ctrl);
103 setup provided through the parent-child relation, are preserved. If
104 necessary, by use of |ssam_client_link| as is done for non-SSAM client
[all …]
/openbmc/linux/Documentation/driver-api/
H A Dswitchtec.rst12 * Event and Error logs
23 through the Memory-mapped Remote Procedure Call (MRPC) interface.
24 Commands are submitted to the interface with a 4-byte command
25 identifier and up to 1KB of command specific data. The firmware will
26 respond with a 4-byte return code and up to 1KB of command-specific
48 the 4-byte Command Return Value plus up to 1024 bytes of output
50 call -- reading less than 4 bytes will produce an error.)
57 * SWITCHTEC_IOCTL_FLASH_INFO - Retrieve firmware length and number
60 * SWITCHTEC_IOCTL_FLASH_PART_INFO - Retrieve address and lengeth for
63 * SWITCHTEC_IOCTL_EVENT_SUMMARY - Read a structure of bitmaps
[all …]
/openbmc/linux/tools/perf/arch/x86/tests/
H A Dsample-parsing.c1 // SPDX-License-Identifier: GPL-2.0-only
10 #include "event.h"
14 #include "util/synthetic-events.h"
17 #include "arch-tests.h"
20 if (s1->m != s2->m) { \
49 union perf_event *event; in do_test() local
57 int err, ret = -1; in do_test()
61 event = malloc(bufsz); in do_test()
62 if (!event) { in do_test()
64 return -1; in do_test()
[all …]
/openbmc/linux/tools/perf/
H A Ddesign.txt3 ------------------------------
7 as instructions executed, cachemisses suffered, or branches mis-predicted -
9 trigger interrupts when a threshold number of events have passed - and can
14 groups, and it provides event capabilities on top of those. It
15 provides "virtual" 64-bit counters, regardless of the width of the
40 * specific (raw) counter configuration data, if unset, the next
41 * 7 bits are an event type and the rest of the bits are the event
72 is divided into 3 bit-fields:
78 If 'raw_type' is 1, then the counter will count a hardware event
80 machine-specific.
[all …]

12345678910>>...44