/openbmc/qemu/docs/devel/ |
H A D | s390-dasd-ipl.rst | 4 s390 hardware IPL 7 The s390 hardware IPL process consists of the following steps. 9 1. A READ IPL ccw is constructed in memory location ``0x0``. 15 2. Execute the Read IPL ccw at ``0x00``, thereby reading IPL1 data into ``0x00``. 18 IPL ccw it read the 24-bytes of IPL1 to be read into memory starting at 21 the original READ IPL ccw. The read ccw will read the IPL2 data into memory 43 the IPL/boot process. 56 management console. This "Load" procedure crafts a special "Read IPL" ccw in 59 written immediately after the special "Read IPL" ccw, the IPL1 channel program 68 In theory we should merely have to do the following to IPL/boot a guest [all …]
|
/openbmc/linux/Documentation/virt/kvm/s390/ |
H A D | s390-pv-boot.rst | 4 s390 (IBM Z) Boot/IPL of Protected VMs 15 On IPL (boot) a small plaintext bootloader is started, which provides 34 This diagnose instruction is the basic mechanism to handle IPL and 36 IPL information blocks, that specify the IPL method/devices and 41 Subcode 8: Set an IPL Information Block of type 5 (information block 73 non-clearing IPL subcodes are not allowed. 76 Re-IPL into a protected mode is only possible via a detour into non
|
/openbmc/openpower-hw-diags/attn/ |
H A D | Attention_Handler.md | 37 - PHYPTI: log an event and request a memory preserving IPL (MPIPL) of the host. 55 host IPL's 63 - Host Transition (re-IPL, MPIPL request): dbus interface. 95 and then use the systemd interface to request a re-IPL of the host. This type of 117 completion, or timeout, request a re-IPL of the host using the dbus interface. 123 of the dump the attention handler will request a re-IPL of the host via the dbus 150 call the analyzer before requesting a dump or IPL. The check for recoverable 160 timeout, will request a re-IPL of the host. 183 Normally active attentions will be cleared by the host re-IPL but any component
|
/openbmc/qemu/docs/system/s390x/ |
H A D | bootdevices.rst | 8 have to explicitly specify the disk where you want to boot from (or "IPL" from, 9 in s390x-speak -- IPL means "Initial Program Load"). 19 device to IPL first. If the IPL fails for the first, the device with the second 20 lowest bootindex will be tried and so on until IPL is successful or there are no 96 In this case, the primary boot device will attempt to IPL using the default 99 IPL using entry number 3.
|
/openbmc/qemu/target/rx/ |
H A D | cpu.h | 38 FIELD(PSW, IPL, 24, 4) 164 psw = FIELD_DP32(psw, PSW, IPL, env->psw_ipl); in rx_cpu_pack_psw()
|
H A D | helper.c | 29 env->psw_ipl = FIELD_EX32(psw, PSW, IPL); in rx_cpu_unpack_psw()
|
/openbmc/openbmc/meta-openpower/recipes-phosphor/host/ |
H A D | p9-host-start.bb | 2 DESCRIPTION = "Service to start POWER9 IPL through SBE"
|
/openbmc/openbmc/meta-arm/meta-arm-systemready/recipes-test/arm-systemready-linux-distros/ |
H A D | arm-systemready-linux-distros-opensuse.bb | 9 & GPL-3.0-only & GPL-3.0-or-later & HPND & ICU & IPL-1.0 & IPA \ 45 file://${COMMON_LICENSE_DIR}/IPL-1.0;md5=be739b8845e6e98f99e206221fe9293b \
|
H A D | arm-systemready-linux-distros-debian.bb | 19 …& MIT-advertising & Beerware & Intel & X11 & ISC & IPL-1.0 & SSH-OpenSSH & SSH-short & RSA-MD & OP… 93 file://${COMMON_LICENSE_DIR}/IPL-1.0;md5=be739b8845e6e98f99e206221fe9293b \
|
/openbmc/u-boot/doc/ |
H A D | README.nand-boot-ppc440 | 14 a) IPL (Initial Program Loader, integrated inside CPU)
|
/openbmc/linux/drivers/char/tpm/eventlog/ |
H A D | tpm1.c | 163 case IPL: in get_event_name()
|
/openbmc/linux/include/linux/ |
H A D | tpm_eventlog.h | 48 IPL, enumerator
|
/openbmc/linux/Documentation/powerpc/ |
H A D | papr_hcalls.rst | 245 | 02 | PMEM device contents are persisted from previous IPL. The data from | 248 | 03 | PMEM device contents are not persisted from previous IPL. There was no| 253 | 05 | PMEM device will be garded off next IPL due to failure |
|
/openbmc/linux/arch/sh/ |
H A D | Kconfig.debug | 30 used by the SH-IPL bootloader, starting very early in the boot
|
/openbmc/openbmc-test-automation/openpower/mpipl/ |
H A D | test_mpipl_basic.robot | 2 Documentation Test MPIPL (Memory preserving IPL).
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/postfix/ |
H A D | postfix_3.8.6.bb | 14 LICENSE = "IPL-1.0 | EPL-2.0"
|
/openbmc/linux/Documentation/arch/s390/ |
H A D | vfio-ccw.rst | 428 programs are not supported. For this reason, IPL has to be handled as
|
H A D | vfio-ap.rst | 35 Profile which can be edited via the HMC. When the linux host system is IPL'd 70 is IPL'd in the LPAR, the AP bus module detects the AP usage and control
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | Interbase-1.0 | 179 …pliance with the License. You may obtain a copy of the License at http://www.Interbase.com/IPL.html
|
/openbmc/linux/ |
H A D | opengrok0.0.log | [all...] |