| /openbmc/qemu/docs/system/ |
| H A D | security.rst | 50 QEMU to provide guest isolation or any security guarantees.
58 Guest Isolation
61 Guest isolation is the confinement of guest code to the virtual machine. When
63 virtual machine. Isolation also includes resource limits such as throttling of
90 Following the principle of least privilege immediately fulfills guest isolation
103 Isolation mechanisms
106 Several isolation mechanisms are available to realize this architecture of
107 guest isolation and the principle of least privilege. With the exception of
112 The fundamental isolation mechanism is that QEMU processes must run as
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/HardwareIsolation/ |
| H A D | Create.interface.yaml | 21 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 D | Entry.interface.yaml | 23 The severity of hardware isolation.
37 Possible severity for hardware isolation.
|
| /openbmc/docs/designs/ |
| H A D | guard-on-bmc.md | 7 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 D | start_host.cpp | 174 * 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 D | psc.c | 104 * 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 D | openbmc-openpower.conf | 3 require conf/distro/include/phosphor-isolation.inc
|
| /openbmc/u-boot/arch/arm/include/asm/arch-fsl-layerscape/ |
| H A D | stream_id_lsch3.h | 42 * -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 D | dbus.rst | 68 - Moderately improved user based security isolation
72 - Best user based security isolation
|
| /openbmc/phosphor-logging/extensions/openpower-pels/registry/ |
| H A D | O_component_ids.json | 8 "3100": "bmc hardware isolation",
|
| /openbmc/openpower-hw-diags/analyzer/ |
| H A D | service_data.hpp | 25 * @param i_isoData The data found during isolation.
50 /** The data found during isolation. */
73 /** @return The data found during isolation. */
|
| /openbmc/u-boot/drivers/tee/optee/ |
| H A D | Kconfig | 8 ARM TrustZone(R) technology as the underlying hardware isolation
|
| /openbmc/u-boot/arch/arm/mach-omap2/omap5/ |
| H A D | dra7xx_iodelay.c | 214 * 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 D | GPL-2.0-with-lmbench-restriction | 41 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 D | gbmc.conf | 2 require conf/distro/include/phosphor-isolation.inc
|
| /openbmc/openpower-hw-diags/test/ |
| H A D | test-root-cause-filter.cpp | 73 // 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 D | python_pep517.bbclass | 40 …nativepython3 -m build --no-isolation --wheel --outdir ${PEP517_WHEEL_PATH} ${PEP517_SOURCE_PATH} …
|
| /openbmc/webui-vue/tests/unit/ |
| H A D | i18n.vendor.spec.js | 1 // How to run this test in isolation:
|
| H A D | i18n.locale-alias.spec.js | 1 // How to run this test in isolation:
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/corstone1000/ |
| H A D | software-architecture.rst | 225 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 D | api.h | 53 * isolation HW.
|
| /openbmc/libcper/ |
| H A D | README.md | 43 isolation.
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | monitoring_chassis_pgood.md | 47 hardware isolation, which will cause the `Enabled` property of the chassis
|
| /openbmc/qemu/hw/remote/ |
| H A D | iommu.c | 21 * IOMMU for TYPE_REMOTE_MACHINE - manages DMA address space isolation
|
| /openbmc/qemu/qapi/ |
| H A D | net.json | 674 # @isolated: Enable isolation for this interface. Interface isolation
721 # @isolated: Enable isolation for this interface. Interface isolation
750 # @isolated: Enable isolation for this interface. Interface isolation
|