Home
last modified time | relevance | path

Searched full:isolation (Results 1 – 25 of 90) sorted by relevance

1234

/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/HardwareIsolation/
H A DCreate.interface.yaml21 The severity of hardware isolation.
42 caused the isolation.
51 The severity of hardware isolation.
55 The BMC error log caused the isolation of hardware.
H A DEntry.interface.yaml23 The severity of hardware isolation.
37 Possible severity for hardware isolation.
/openbmc/docs/designs/
H A Dguard-on-bmc.md7 document discusses the design of the BMC support for such isolation procedures.
11 notifying users about the components in isolation, clearing isolation, isolating
13 process of isolation is mentioned as guard in this document, which means
216 created, an isolation procedure is needed to isolate the units from service.
242 and that should be automated, further tests on the isolation of each type of the
/openbmc/openpower-proc-control/procedures/phal/
H A Dstart_host.cpp174 * procedure callout for the hardware isolation policy
207 // and even we should allow the hardware isolation by default. in createPELForHwIsolationSettingsErr()
210 "for the hardware isolation policy settings failures.", in createPELForHwIsolationSettingsErr()
217 * @brief Helper function to decide the hardware isolation (aka guard)
220 * true on failure since hardware isolation feature should be
/openbmc/u-boot/arch/arm/mach-keystone/
H A Dpsc.c104 * isolation functionality in psc_set_state()
188 * psc_set_reset_iso() - Set the reset isolation bit in mdctl
191 * The reset isolation enable bit is set. The state of the module is not
194 * Return: 0 if the module config showed that reset isolation is supported.
203 /* Set the reset isolation bit */ in psc_set_reset_iso()
/openbmc/openbmc/meta-openpower/conf/distro/
H A Dopenbmc-openpower.conf3 require conf/distro/include/phosphor-isolation.inc
/openbmc/u-boot/arch/arm/include/asm/arch-fsl-layerscape/
H A Dstream_id_lsch3.h42 * -the MC is responsible for allocating and setting up 'isolation context
55 * ICID[6:0] 6-0 // isolation context id
/openbmc/qemu/docs/interop/
H A Ddbus.rst68 - Moderately improved user based security isolation
72 - Best user based security isolation
/openbmc/openpower-hw-diags/analyzer/
H A Dservice_data.hpp25 * @param i_isoData The data found during isolation.
50 /** The data found during isolation. */
73 /** @return The data found during isolation. */
/openbmc/phosphor-logging/extensions/openpower-pels/registry/
H A DO_component_ids.json8 "3100": "bmc hardware isolation",
/openbmc/u-boot/drivers/tee/optee/
H A DKconfig8 ARM TrustZone(R) technology as the underlying hardware isolation
/openbmc/u-boot/arch/arm/mach-omap2/omap5/
H A Ddra7xx_iodelay.c214 * isolation. So error handling and debug prints are done after in __recalibrate_iodelay_end()
222 puts("IODELAY: Isolation of Device IOs failed\n"); in __recalibrate_iodelay_end()
228 puts("IODELAY: De-isolation of Device IOs failed\n"); in __recalibrate_iodelay_end()
/openbmc/openbmc/meta-openembedded/meta-oe/licenses/
H A DGPL-2.0-with-lmbench-restriction41 to be published in isolation, without the complete story being told.
87 networking numbers in isolation. The restrictions only kick
/openbmc/openbmc/meta-google/conf/distro/
H A Dgbmc.conf2 require conf/distro/include/phosphor-isolation.inc
/openbmc/openpower-hw-diags/test/
H A Dtest-root-cause-filter.cpp73 // Add the signatures to the isolation data in TEST()
87 // Add the signatures to the isolation data in TEST()
/openbmc/openbmc/poky/meta/classes-recipe/
H A Dpython_pep517.bbclass40 …nativepython3 -m build --no-isolation --wheel --outdir ${PEP517_WHEEL_PATH} ${PEP517_SOURCE_PATH} …
/openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/corstone1000/
H A Dsoftware-architecture.rst225 Corstone-1000 implements isolation level 2. Cortex-M0+ MPU (Memory Protection
226 Unit) is used to implement isolation level 2.
231 secure by real hardware isolation but have a higher latency path. In the
233 subsystem have lower latency but virtual hardware isolation created by
/openbmc/u-boot/arch/arm/include/asm/arch-imx8/sci/svc/rm/
H A Dapi.h53 * isolation HW.
/openbmc/webui-vue/tests/unit/
H A Di18n.locale-alias.spec.js1 // How to run this test in isolation:
H A Di18n.vendor.spec.js1 // How to run this test in isolation:
/openbmc/libcper/
H A DREADME.md43 isolation.
/openbmc/phosphor-power/phosphor-power-sequencer/docs/
H A Dmonitoring_chassis_pgood.md47 hardware isolation, which will cause the `Enabled` property of the chassis
/openbmc/qemu/hw/remote/
H A Diommu.c21 * IOMMU for TYPE_REMOTE_MACHINE - manages DMA address space isolation
/openbmc/phosphor-power/phosphor-power-sequencer/src/
H A Dconfig_file_parser.hpp155 * A chassis_template object cannot be fully parsed in isolation. It is a
179 * Note that chassis_template objects cannot be fully parsed in isolation. See
/openbmc/openpower-hw-diags/analyzer/ras-data/
H A Dras-data-parser.hpp55 * @brief Initializes the signature list within the input isolation data

1234