/openbmc/linux/drivers/s390/net/ |
H A D | qeth_core_sys.c | 411 switch (card->options.isolation) { in qeth_dev_isolation_show() 427 enum qeth_ipa_isolation_modes isolation; in qeth_dev_isolation_store() local 440 isolation = ISOLATION_MODE_NONE; in qeth_dev_isolation_store() 442 isolation = ISOLATION_MODE_FWD; in qeth_dev_isolation_store() 444 isolation = ISOLATION_MODE_DROP; in qeth_dev_isolation_store() 451 rc = qeth_setadpparms_set_access_ctrl(card, isolation); in qeth_dev_isolation_store() 454 WRITE_ONCE(card->options.isolation, isolation); in qeth_dev_isolation_store() 462 static DEVICE_ATTR(isolation, 0644, qeth_dev_isolation_show,
|
/openbmc/openbmc-test-automation/lib/ras/ |
H A D | host_utils.robot | 42 # fir_address FIR (Fault isolation register) value (e.g. 2011400). 90 # fir_address FIR (Fault isolation register) value (e.g. 2011400). 112 # fir_address FIR (Fault isolation register) value (e.g. 2011400). 187 # fir_address FIR (Fault isolation register) value (e.g. '2011400'). 218 # fir_address FIR (Fault isolation register) value (e.g. '2011400').
|
/openbmc/qemu/docs/system/ |
H A D | security.rst | 50 QEMU to provide guest isolation or any security guarantees. 61 Guest isolation is the confinement of guest code to the virtual machine. When 90 Following the principle of least privilege immediately fulfills guest isolation 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/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 219 created, an isolation procedure is needed to isolate the units from service. 245 and that should be automated, further tests on the isolation of each type of the
|
/openbmc/openbmc/meta-openpower/conf/distro/ |
H A D | openbmc-openpower.conf | 3 require conf/distro/include/phosphor-isolation.inc
|
/openbmc/linux/drivers/gpu/drm/i915/gt/ |
H A D | intel_engine_user.c | 266 unsigned int isolation; in intel_engines_driver_register() local 298 isolation = intel_engines_has_context_isolation(i915); in intel_engines_driver_register() 303 if ((isolation & bit) != expected) { in intel_engines_driver_register()
|
/openbmc/openbmc-test-automation/openpower/ras/ |
H A D | ras_utils.robot | 59 # fir_address FIR (Fault isolation register) value (e.g. 2011400). 88 # fir_address FIR (Fault isolation register) value (e.g. 2011400). 128 # fir_address FIR (Fault isolation register) value (e.g. '2011400'). 217 # fir_address FIR (Fault isolation register) value (e.g. 2011400).
|
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-m/files/corstone1000/ |
H A D | 0016-Platform-corstone1000-Fix-isolation-L2-memory-protection.patch | 4 Subject: [PATCH] Platform: corstone1000: Fix isolation L2 memory protection 7 the memory protection required for isolation level 2 was not present.
|
/openbmc/openbmc/meta-google/conf/distro/ |
H A D | gbmc.conf | 2 require conf/distro/include/phosphor-isolation.inc
|
/openbmc/linux/arch/arm/boot/dts/marvell/ |
H A D | armada-385-clearfog-gtr.dtsi | 50 47 - Control isolation of boot sensitive SAR signals 172 cf_gtr_isolation_pins: cf-gtr-isolation-pins { 437 sar-isolation { 441 line-name = "sar-isolation";
|
/openbmc/linux/Documentation/devicetree/bindings/soc/xilinx/ |
H A D | xlnx,vcu.txt | 7 LogicoreIP design to provide the isolation between processing system
|
/openbmc/linux/drivers/net/can/peak_canfd/ |
H A D | Kconfig | 11 up to 12 Mbit/s. A galvanic isolation of the CAN ports protects the
|
/openbmc/u-boot/drivers/tee/optee/ |
H A D | Kconfig | 8 ARM TrustZone(R) technology as the underlying hardware isolation
|
/openbmc/qemu/docs/interop/ |
H A D | dbus.rst | 68 - Moderately improved user based security isolation 72 - Best user based security isolation
|
/openbmc/linux/drivers/clk/xilinx/ |
H A D | Kconfig | 8 Provides the driver to enable and disable the isolation between the
|
/openbmc/linux/Documentation/devicetree/bindings/soc/dove/ |
H A D | pmu.txt | 28 - marvell,pmu_iso_mask: specifies the mask value for PMU isolation register
|
/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/linux/drivers/hv/ |
H A D | Kconfig | 27 VSM achieves and maintains isolation through Virtual Trust Levels
|
/openbmc/qemu/qapi/ |
H A D | net.json | 550 # @isolated: Enable isolation for this interface. Interface isolation 597 # @isolated: Enable isolation for this interface. Interface isolation 626 # @isolated: Enable isolation for this interface. Interface isolation
|
/openbmc/linux/Documentation/devicetree/bindings/misc/ |
H A D | fsl,qoriq-mc.txt | 16 same hardware "isolation context" and a 10-bit value called an ICID 17 (isolation context id) is expressed by the hardware to identify
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-driver-uacce | 27 isolation strategy. This size is a configured integer value, which is the
|
/openbmc/linux/Documentation/dev-tools/kunit/ |
H A D | faq.rst | 13 test a single unit of code in isolation and hence the name *unit test*. A unit 49 - A unit test is supposed to test a single unit of code in isolation. A unit
|
/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/libcper/ |
H A D | README.md | 43 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
|