| /openbmc/openbmc-test-automation/lib/ |
| H A D | gen_plug_in.py | 4 This module provides functions which are useful for running plug-ins.
16 "This is a colon-separated list of plug-in directory paths. If one"
18 + " path info), it will be taken to be a native plug-in. In that case,"
19 + ' %(prog)s will search for the native plug-in in the "plug-ins"'
21 + " is found. Also, integrated plug-ins will automatically be appended"
22 + " to your plug_in_dir_paths list. An integrated plug-in is any plug-in"
36 Get plug-in base paths and return them as a list.
60 …Find and return the normalized directory path of the specified plug in. This is done by searching…
64 plug_in_name The unqualified name of the plug-in package.
80 Validate the plug in package and return the normalized plug-in directory path.
[all …]
|
| H A D | gen_plug_in_utils.py | 4 This module provides functions which are useful to plug-in call point programs.
23 Return the plug-in package name (e.g. "OS_Console", "DB_Logging").
41 …Return an OrderedDict which is sorted by key and which contains all of the plug-in environment var…
72 …general Return general plug-in parms (e.g. those beginning with "AUTOBOOT"…
74 …custom Return custom plug-in parms (i.e. those beginning with the upper c…
75 name of the plug-in package, for example "OBMC_SAMPLE_PARM1").
76 plug_in_package_name The name of the plug-in package for which custom parms are to be
77 returned. The default is the current plug in package name.
122 …# Create a list of plug-in environment variables by pre-pending <all caps plug-in package name>_<a…
137 # Initialize unset plug-in vars.
[all …]
|
| H A D | gen_robot_plug_in.py | 4 This module provides functions which are useful for running plug-ins from a robot program.
20 …Call the external validate_plug_ins.py program which validates the plug-in dir paths given to it. …
21 a list containing a normalized path for each plug-in selected.
24 plug_in_dir_paths A colon-separated list of plug-in directory paths.
34 "Validate plug ins call failed. See"
59 …Call the external process_plug_in_packages.py to process the plug-in packages. Return the followi…
62 failed_plug_in_name The failed plug in name (if any).
65 plug_in_packages_list A python list of plug-in directory paths.
66 … call_point The call point program to be called for each plug-in package (e.g.
70 … means that for each plug-in call point that runs, a 0x00000200 will not
[all …]
|
| H A D | obmc_boot_test.py | 47 # Setting master_pid correctly influences the behavior of plug-ins like
128 When a plug-in call point program returns this value, it indicates that
139 When a plug-in call point program returns this value, it indicates that
291 Initialize all plug-in environment variables which do not change for the
354 Initialize all changing plug-in environment variables for use by the
355 plug-in programs.
412 # Clear the ffdc_list_file_path file. Plug-ins may now write to it.
418 # Clear the ffdc_report_list_path file. Plug-ins may now write to it.
424 # Clear the ffdc_summary_list_path file. Plug-ins may now write to it.
517 error_message = "Plug-in setup failed.\n"
[all …]
|
| /openbmc/openbmc-test-automation/bin/ |
| H A D | process_plug_in_packages.py | 29 description="%(prog)s will process the plug-in packages passed to it."
30 + " A plug-in package is essentially a directory containing"
34 + " (described below). For each plug-in package passed,"
36 + " point program in the plug-in directory. If it is found,"
42 + " failed_plug_in_name: <failed plug-in value,"
68 + ' "cp_" prefix. For each plug-in package passed to this program,'
70 + " the plug-in directory."
79 + " equals 0x00000200, it means that for each plug-in call point that"
91 + "non-zero if the call point program from any plug-in directory "
93 + "the call point program from each and every plug-in directory "
[all …]
|
| H A D | validate_plug_ins.py | 34 description="%(prog)s will validate the plug-in packages passed to it."
35 + " It will also print a list of the absolute plug-in"
121 # As stated in the help text, this program must print the full paths of each selected plug in.
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/ettercap/ettercap/ |
| H A D | 0001-sslstrip-Enhance-the-libcurl-version-check-to-consid.patch | 13 TOPDIR/build/tmp/work/cortexa15t2hf-neon-yoe-linux-gnueabi/ettercap/0.8.3.1-r0/git/plug-ins/sslstri…
20 plug-ins/sslstrip/sslstrip.c | 2 +-
23 diff --git a/plug-ins/sslstrip/sslstrip.c b/plug-ins/sslstrip/sslstrip.c
25 --- a/plug-ins/sslstrip/sslstrip.c
26 +++ b/plug-ins/sslstrip/sslstrip.c
|
| /openbmc/qemu/include/hw/ |
| H A D | hotplug.h | 29 * @plug_handler: a device performing plug/uplug action
40 * hardware (un)plug functions.
43 * @pre_plug: pre plug callback called at start of device.realize(true)
44 * @plug: plug callback called at end of device.realize(true).
59 hotplug_fn plug; member
68 * Call #HotplugHandlerClass.plug callback of @plug_handler.
|
| /openbmc/qemu/docs/ |
| H A D | pcie_pci_bridge.txt | 10 But due to its strict limitations - no support of hot-plug,
17 see 'PCIE-PCI bridge hot-plug' section),
18 and supports devices hot-plug into the bridge itself
21 Hot-plug of legacy PCI devices into the bridge
22 is provided by bridge's built-in Standard hot-plug Controller.
25 PCIE-PCI bridge hot-plug
27 Guest OSes require extra efforts to enable PCIE-PCI bridge hot-plug.
102 Windows 7 and older versions don't support hot-plug devices into the PCIE-PCI bridge.
103 To enable device hot-plug into the bridge on Linux there're 3 ways:
107 which allows the bridge to notify the OS about hot-plug event without having
|
| H A D | pcie.txt | 67 2.1.1 To plug a device into pcie.0 as a Root Complex Integrated Endpoint use:
92 Plug only PCI Express devices into PCI Express Ports.
145 PCI Express to PCI Bridge until is full and then plug a new PCI-PCI Bridge...
162 2.3.1 To plug a PCI device into pcie.0 as an Integrated Endpoint use:
220 5. Hot-plug
223 do not support hot-plug, so any devices plugged into Root Complexes
234 The PCI hot-plug into PCI-PCI bridge is ACPI based, whereas hot-plug into
236 the PCI Express native hot-plug.
241 5.1 Planning for hot-plug:
265 5.3 Hot-plug example:
|
| /openbmc/qemu/include/standard-headers/linux/ |
| H A D | virtio_mem.h | 55 * order to (un)plug memory. A device cannot (un)plug memory belonging to
61 * from the device to the device driver to (un)plug blocks. The
62 * device driver should try to (un)plug blocks in order to reach the
63 * "requested_size". It is impossible to plug more memory than requested.
66 * be used to (un)plug memory. It is always at least as big as the
99 /* request to plug memory blocks */
131 struct virtio_mem_req_plug plug; member
149 * Request denied - e.g. trying to plug more than requested, applicable for
208 * Currently used size. Changes due to plug/unplug requests, but no
212 /* Requested size. New plug requests cannot exceed it. Can change. */
|
| /openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/gpio/phosphor-gpio-monitor/ |
| H A D | yosemite4-phosphor-multi-gpio-monitor.json | 187 "FALLING": ["slot-hot-plug@1.service", "slot-plug-in@1.service"]
197 "FALLING": ["slot-hot-plug@2.service", "slot-plug-in@2.service"]
207 "FALLING": ["slot-hot-plug@3.service", "slot-plug-in@3.service"]
217 "FALLING": ["slot-hot-plug@4.service", "slot-plug-in@4.service"]
227 "FALLING": ["slot-hot-plug@5.service", "slot-plug-in@5.service"]
237 "FALLING": ["slot-hot-plug@6.service", "slot-plug-in@6.service"]
247 "FALLING": ["slot-hot-plug@7.service", "slot-plug-in@7.service"]
257 "FALLING": ["slot-hot-plug@8.service", "slot-plug-in@8.service"]
|
| H A D | slot-plug-in@.service | 2 Description=slot-plug-in %i
6 ExecStart=/usr/libexec/phosphor-gpio-monitor/slot-plug-in %i
7 SyslogIdentifier=slot-plug-in %i
|
| /openbmc/qemu/tests/qtest/ |
| H A D | device-plug-test.c | 2 * QEMU device plug/unplug handling
215 qtest_add_func("/device-plug/pci-unplug-request", in main()
217 qtest_add_func("/device-plug/pci-unplug-json-request", in main()
221 qtest_add_func("/device-plug/ccw-unplug", in main()
226 qtest_add_func("/device-plug/spapr-cpu-unplug-request", in main()
228 qtest_add_func("/device-plug/spapr-memory-unplug-request", in main()
230 qtest_add_func("/device-plug/spapr-phb-unplug-request", in main()
235 qtest_add_func("/device-plug/q35-pci-unplug-request", in main()
237 qtest_add_func("/device-plug/q35-pci-unplug-json-request", in main()
|
| H A D | cpu-plug-test.c | 99 path = g_strdup_printf("cpu-plug/%s/device-add/%ux%ux%u&maxcpus=%u", in add_pc_test_case()
125 path = g_strdup_printf("cpu-plug/%s/device-add/%ux%ux%u&maxcpus=%u", in add_pseries_test_case()
151 path = g_strdup_printf("cpu-plug/%s/device-add/%ux%ux%u&maxcpus=%u", in add_s390x_test_case()
173 path = g_strdup_printf("cpu-plug/%s/device-add/%ux%ux%u&maxcpus=%u", in add_loongarch_test_case()
|
| /openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/gpio/ |
| H A D | phosphor-gpio-monitor_%.bbappend | 16 file://slot-hot-plug@.service \
31 file://slot-plug-in@.service \
32 file://slot-plug-in \
53 slot-hot-plug@.service \
64 slot-plug-in@.service \
79 …install -m 0644 ${UNPACKDIR}/slot-hot-plug@.service ${D}${systemd_system_unitdir}/slot-hot-plug@.s…
90 install -m 0644 ${UNPACKDIR}/slot-plug-in@.service ${D}${systemd_system_unitdir}/
107 install -m 0755 ${UNPACKDIR}/slot-plug-in ${D}${libexecdir}/${PN}/
|
| /openbmc/openbmc-test-automation/bin/plug_ins/Stop/ |
| H A D | parm_def | 3 # "rest_fail" indicates that the Stop plug-in should fail if REST commands to the BMC are failing.
9 # Indicates that the test should be stopped when the Verify_hardware plug-in fails its analysis.
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | Circuit_v1.xml | 350 …ion" String="This value shall represent a plug that matches the NEMA specified 5-15 straight (non-…
354 …escription" String="This value shall represent a plug that matches the NEMA specified locking L5-1…
358 …ion" String="This value shall represent a plug that matches the NEMA specified 5-20 straight (non-…
362 …escription" String="This value shall represent a plug that matches the NEMA specified locking L5-2…
366 …escription" String="This value shall represent a plug that matches the NEMA specified locking L5-3…
370 …ion" String="This value shall represent a plug that matches the NEMA specified 6-15 straight (non-…
374 …escription" String="This value shall represent a plug that matches the NEMA specified locking L6-1…
378 …ion" String="This value shall represent a plug that matches the NEMA specified 6-20 straight (non-…
382 …escription" String="This value shall represent a plug that matches the NEMA specified locking L6-2…
386 …escription" String="This value shall represent a plug that matches the NEMA specified locking L6-3…
[all …]
|
| /openbmc/qemu/hw/core/ |
| H A D | hotplug.c | 33 if (hdc->plug) { in hotplug_handler_plug()
34 hdc->plug(plug_handler, plugged_dev, errp); in hotplug_handler_plug()
|
| /openbmc/openbmc-test-automation/bin/plug_ins/Soft_errors/ |
| H A D | cp_post_boot | 20 + " save it as a plug-in value for the benefit of the FFDC plug-in."
21 + " The FFDC plug-in can use that data to decide whether to collect"
|
| /openbmc/u-boot/include/usb/ |
| H A D | designware_udc.h | 16 * 2. The plug detect
154 * Defines for Plug Detect
162 /* Plug State Register definitions */
|
| /openbmc/u-boot/include/configs/ |
| H A D | ds109.h | 28 * mv-plug-common.h should be defined after CMD configs since it used them
31 #include "mv-plug-common.h"
|
| H A D | dreamplug.h | 25 * mv-plug-common.h should be defined after CMD configs since it used them
28 #include "mv-plug-common.h"
|
| /openbmc/qemu/hw/s390x/ |
| H A D | virtio-ccw-md.c | 28 * Without a bus hotplug handler, we cannot control the plug/unplug in virtio_ccw_md_pre_plug()
38 * First, see if we can plug this memory device at all. If that in virtio_ccw_md_pre_plug()
56 * Plug the memory device first and then branch off to the actual in virtio_ccw_md_plug()
|
| /openbmc/qemu/hw/virtio/ |
| H A D | virtio-md-pci.c | 28 * Without a bus hotplug handler, we cannot control the plug/unplug in virtio_md_pci_pre_plug()
37 * First, see if we can plug this memory device at all. If that in virtio_md_pci_pre_plug()
55 * Plug the memory device first and then branch off to the actual in virtio_md_pci_plug()
|