2011-04-01 06:15:20 +02:00
|
|
|
/*
|
|
|
|
|
* QEMU PowerPC pSeries Logical Partition (aka sPAPR) hardware System Emulator
|
|
|
|
|
*
|
|
|
|
|
* Copyright (c) 2004-2007 Fabrice Bellard
|
|
|
|
|
* Copyright (c) 2007 Jocelyn Mayer
|
|
|
|
|
* Copyright (c) 2010 David Gibson, IBM Corporation.
|
|
|
|
|
*
|
|
|
|
|
* Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
|
|
|
* of this software and associated documentation files (the "Software"), to deal
|
|
|
|
|
* in the Software without restriction, including without limitation the rights
|
|
|
|
|
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
|
|
|
* copies of the Software, and to permit persons to whom the Software is
|
|
|
|
|
* furnished to do so, subject to the following conditions:
|
|
|
|
|
*
|
|
|
|
|
* The above copyright notice and this permission notice shall be included in
|
|
|
|
|
* all copies or substantial portions of the Software.
|
|
|
|
|
*
|
|
|
|
|
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
|
|
|
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
|
|
|
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
|
|
|
|
|
* THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
|
|
|
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
|
|
|
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
|
|
|
|
* THE SOFTWARE.
|
|
|
|
|
*
|
|
|
|
|
*/
|
|
|
|
|
#include "sysemu.h"
|
|
|
|
|
#include "hw.h"
|
|
|
|
|
#include "elf.h"
|
2011-04-01 06:15:29 +02:00
|
|
|
#include "net.h"
|
2011-04-01 06:15:31 +02:00
|
|
|
#include "blockdev.h"
|
2011-04-01 06:15:20 +02:00
|
|
|
|
|
|
|
|
#include "hw/boards.h"
|
|
|
|
|
#include "hw/ppc.h"
|
|
|
|
|
#include "hw/loader.h"
|
|
|
|
|
|
|
|
|
|
#include "hw/spapr.h"
|
2011-04-01 06:15:21 +02:00
|
|
|
#include "hw/spapr_vio.h"
|
Implement the PAPR (pSeries) virtualized interrupt controller (xics)
PAPR defines an interrupt control architecture which is logically divided
into ICS (Interrupt Control Presentation, each unit is responsible for
presenting interrupts to a particular "interrupt server", i.e. CPU) and
ICS (Interrupt Control Source, each unit responsible for one or more
hardware interrupts as numbered globally across the system). All PAPR
virtual IO devices expect to deliver interrupts via this mechanism. In
Linux, this interrupt controller system is handled by the "xics" driver.
On pSeries systems, access to the interrupt controller is virtualized via
hypercalls and RTAS methods. However, the virtualized interface is very
similar to the underlying interrupt controller hardware, and similar PICs
exist un-virtualized in some other systems.
This patch implements both the ICP and ICS sides of the PAPR interrupt
controller. For now, only the hypercall virtualized interface is provided,
however it would be relatively straightforward to graft an emulated
register interface onto the underlying interrupt logic if we want to add
a machine with a hardware ICS/ICP system in the future.
There are some limitations in this implementation: it is assumed for now
that only one instance of the ICS exists, although a full xics system can
have several, each responsible for a different group of hardware irqs.
ICP/ICS can handle both level-sensitve (LSI) and message signalled (MSI)
interrupt inputs. For now, this implementation supports only MSI
interrupts, since that is used by PAPR virtual IO devices.
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-01 06:15:25 +02:00
|
|
|
#include "hw/xics.h"
|
2011-04-01 06:15:20 +02:00
|
|
|
|
|
|
|
|
#include <libfdt.h>
|
|
|
|
|
|
|
|
|
|
#define KERNEL_LOAD_ADDR 0x00000000
|
|
|
|
|
#define INITRD_LOAD_ADDR 0x02800000
|
|
|
|
|
#define FDT_MAX_SIZE 0x10000
|
2011-04-01 06:15:23 +02:00
|
|
|
#define RTAS_MAX_SIZE 0x10000
|
Add SLOF-based partition firmware for pSeries machine, allowing more boot options
Currently, the emulated pSeries machine requires the use of the
-kernel parameter in order to explicitly load a guest kernel. This
means booting from the virtual disk, cdrom or network is not possible.
This patch addresses this limitation by inserting a within-partition
firmware image (derived from the "SLOF" free Open Firmware project).
If -kernel is not specified, qemu will now load the SLOF image, which
has access to the qemu boot device list through the device tree, and
can boot from any of the usual virtual devices.
In order to support the new firmware, an extension to the emulated
machine/hypervisor is necessary. Unlike Linux, which expects
multi-CPU entry to be handled kexec() style, the SLOF firmware expects
only one CPU to be active at entry, and to use a hypervisor RTAS
method to enable the other CPUs one by one.
This patch also implements this 'start-cpu' method, so that SLOF can
start the secondary CPUs and marshal them into the kexec() holding
pattern ready for entry into the guest OS. Linux should, and in the
future might directly use the start-cpu method to enable initially
disabled CPUs, but for now it does require kexec() entry.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-01 06:15:34 +02:00
|
|
|
#define FW_MAX_SIZE 0x400000
|
|
|
|
|
#define FW_FILE_NAME "slof.bin"
|
|
|
|
|
|
|
|
|
|
#define MIN_RAM_SLOF 512UL
|
2011-04-01 06:15:20 +02:00
|
|
|
|
|
|
|
|
#define TIMEBASE_FREQ 512000000ULL
|
|
|
|
|
|
2011-04-19 03:54:50 +02:00
|
|
|
#define MAX_CPUS 256
|
Implement the PAPR (pSeries) virtualized interrupt controller (xics)
PAPR defines an interrupt control architecture which is logically divided
into ICS (Interrupt Control Presentation, each unit is responsible for
presenting interrupts to a particular "interrupt server", i.e. CPU) and
ICS (Interrupt Control Source, each unit responsible for one or more
hardware interrupts as numbered globally across the system). All PAPR
virtual IO devices expect to deliver interrupts via this mechanism. In
Linux, this interrupt controller system is handled by the "xics" driver.
On pSeries systems, access to the interrupt controller is virtualized via
hypercalls and RTAS methods. However, the virtualized interface is very
similar to the underlying interrupt controller hardware, and similar PICs
exist un-virtualized in some other systems.
This patch implements both the ICP and ICS sides of the PAPR interrupt
controller. For now, only the hypercall virtualized interface is provided,
however it would be relatively straightforward to graft an emulated
register interface onto the underlying interrupt logic if we want to add
a machine with a hardware ICS/ICP system in the future.
There are some limitations in this implementation: it is assumed for now
that only one instance of the ICS exists, although a full xics system can
have several, each responsible for a different group of hardware irqs.
ICP/ICS can handle both level-sensitve (LSI) and message signalled (MSI)
interrupt inputs. For now, this implementation supports only MSI
interrupts, since that is used by PAPR virtual IO devices.
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-01 06:15:25 +02:00
|
|
|
#define XICS_IRQS 1024
|
2011-04-01 06:15:20 +02:00
|
|
|
|
|
|
|
|
sPAPREnvironment *spapr;
|
|
|
|
|
|
Delay creation of pseries device tree until reset
At present, the 'pseries' machine creates a flattened device tree in the
machine->init function to pass to either the guest kernel or to firmware.
However, the machine->init function runs before processing of -device
command line options, which means that the device tree so created will
be (incorrectly) missing devices specified that way.
Supplying a correct device tree is, in any case, part of the required
platform entry conditions. Therefore, this patch moves the creation and
loading of the device tree from machine->init to a reset callback. The
setup of entry point address and initial register state moves with it,
which leads to a slight cleanup.
This is not, alas, quite enough to make a fully working reset for pseries.
For that we would need to reload the firmware images, which on this
machine are loaded into RAM. It's a step in the right direction, though.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-05 07:12:10 +02:00
|
|
|
static void *spapr_create_fdt_skel(const char *cpu_model,
|
|
|
|
|
target_phys_addr_t initrd_base,
|
|
|
|
|
target_phys_addr_t initrd_size,
|
|
|
|
|
const char *boot_device,
|
|
|
|
|
const char *kernel_cmdline,
|
|
|
|
|
long hash_shift)
|
2011-04-01 06:15:20 +02:00
|
|
|
{
|
|
|
|
|
void *fdt;
|
2011-04-05 07:12:09 +02:00
|
|
|
CPUState *env;
|
Delay creation of pseries device tree until reset
At present, the 'pseries' machine creates a flattened device tree in the
machine->init function to pass to either the guest kernel or to firmware.
However, the machine->init function runs before processing of -device
command line options, which means that the device tree so created will
be (incorrectly) missing devices specified that way.
Supplying a correct device tree is, in any case, part of the required
platform entry conditions. Therefore, this patch moves the creation and
loading of the device tree from machine->init to a reset callback. The
setup of entry point address and initial register state moves with it,
which leads to a slight cleanup.
This is not, alas, quite enough to make a fully working reset for pseries.
For that we would need to reload the firmware images, which on this
machine are loaded into RAM. It's a step in the right direction, though.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-05 07:12:10 +02:00
|
|
|
uint64_t mem_reg_property[] = { 0, cpu_to_be64(ram_size) };
|
2011-04-01 06:15:20 +02:00
|
|
|
uint32_t start_prop = cpu_to_be32(initrd_base);
|
|
|
|
|
uint32_t end_prop = cpu_to_be32(initrd_base + initrd_size);
|
2011-04-01 06:15:22 +02:00
|
|
|
uint32_t pft_size_prop[] = {0, cpu_to_be32(hash_shift)};
|
2011-04-01 06:15:28 +02:00
|
|
|
char hypertas_prop[] = "hcall-pft\0hcall-term\0hcall-dabr\0hcall-interrupt"
|
Implement PAPR VPA functions for pSeries shared processor partitions
Shared-processor partitions are those where a CPU is time-sliced between
partitions, rather than being permanently dedicated to a single
partition. qemu emulated partitions, since they are just scheduled with
the qemu user process, behave mostly like shared processor partitions.
In order to better support shared processor partitions (splpar), PAPR
defines the "VPA" (Virtual Processor Area), a shared memory communication
channel between the hypervisor and partitions. There are also two
additional shared memory communication areas for specialized purposes
associated with the VPA.
A VPA is not essential for operating an splpar, though it can be necessary
for obtaining accurate performance measurements in the presence of
runtime partition switching.
Most importantly, however, the VPA is a prerequisite for PAPR's H_CEDE,
hypercall, which allows a partition OS to give up it's shared processor
timeslices to other partitions when idle.
This patch implements the VPA and H_CEDE hypercalls in qemu. We don't
implement any of the more advanced statistics which can be communicated
through the VPA. However, this is enough to make normal pSeries kernels
do an effective power-save idle on an emulated pSeries, significantly
reducing the host load of a qemu emulated pSeries running an idle guest OS.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-01 06:15:33 +02:00
|
|
|
"\0hcall-tce\0hcall-vio\0hcall-splpar";
|
Implement the PAPR (pSeries) virtualized interrupt controller (xics)
PAPR defines an interrupt control architecture which is logically divided
into ICS (Interrupt Control Presentation, each unit is responsible for
presenting interrupts to a particular "interrupt server", i.e. CPU) and
ICS (Interrupt Control Source, each unit responsible for one or more
hardware interrupts as numbered globally across the system). All PAPR
virtual IO devices expect to deliver interrupts via this mechanism. In
Linux, this interrupt controller system is handled by the "xics" driver.
On pSeries systems, access to the interrupt controller is virtualized via
hypercalls and RTAS methods. However, the virtualized interface is very
similar to the underlying interrupt controller hardware, and similar PICs
exist un-virtualized in some other systems.
This patch implements both the ICP and ICS sides of the PAPR interrupt
controller. For now, only the hypercall virtualized interface is provided,
however it would be relatively straightforward to graft an emulated
register interface onto the underlying interrupt logic if we want to add
a machine with a hardware ICS/ICP system in the future.
There are some limitations in this implementation: it is assumed for now
that only one instance of the ICS exists, although a full xics system can
have several, each responsible for a different group of hardware irqs.
ICP/ICS can handle both level-sensitve (LSI) and message signalled (MSI)
interrupt inputs. For now, this implementation supports only MSI
interrupts, since that is used by PAPR virtual IO devices.
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-01 06:15:25 +02:00
|
|
|
uint32_t interrupt_server_ranges_prop[] = {0, cpu_to_be32(smp_cpus)};
|
2011-04-01 06:15:20 +02:00
|
|
|
int i;
|
|
|
|
|
char *modelname;
|
|
|
|
|
|
|
|
|
|
#define _FDT(exp) \
|
|
|
|
|
do { \
|
|
|
|
|
int ret = (exp); \
|
|
|
|
|
if (ret < 0) { \
|
|
|
|
|
fprintf(stderr, "qemu: error creating device tree: %s: %s\n", \
|
|
|
|
|
#exp, fdt_strerror(ret)); \
|
|
|
|
|
exit(1); \
|
|
|
|
|
} \
|
|
|
|
|
} while (0)
|
|
|
|
|
|
|
|
|
|
fdt = qemu_mallocz(FDT_MAX_SIZE);
|
|
|
|
|
_FDT((fdt_create(fdt, FDT_MAX_SIZE)));
|
|
|
|
|
|
|
|
|
|
_FDT((fdt_finish_reservemap(fdt)));
|
|
|
|
|
|
|
|
|
|
/* Root node */
|
|
|
|
|
_FDT((fdt_begin_node(fdt, "")));
|
|
|
|
|
_FDT((fdt_property_string(fdt, "device_type", "chrp")));
|
2011-04-19 03:54:51 +02:00
|
|
|
_FDT((fdt_property_string(fdt, "model", "IBM pSeries (emulated by qemu)")));
|
2011-04-01 06:15:20 +02:00
|
|
|
|
|
|
|
|
_FDT((fdt_property_cell(fdt, "#address-cells", 0x2)));
|
|
|
|
|
_FDT((fdt_property_cell(fdt, "#size-cells", 0x2)));
|
|
|
|
|
|
|
|
|
|
/* /chosen */
|
|
|
|
|
_FDT((fdt_begin_node(fdt, "chosen")));
|
|
|
|
|
|
|
|
|
|
_FDT((fdt_property_string(fdt, "bootargs", kernel_cmdline)));
|
|
|
|
|
_FDT((fdt_property(fdt, "linux,initrd-start",
|
|
|
|
|
&start_prop, sizeof(start_prop))));
|
|
|
|
|
_FDT((fdt_property(fdt, "linux,initrd-end",
|
|
|
|
|
&end_prop, sizeof(end_prop))));
|
Add SLOF-based partition firmware for pSeries machine, allowing more boot options
Currently, the emulated pSeries machine requires the use of the
-kernel parameter in order to explicitly load a guest kernel. This
means booting from the virtual disk, cdrom or network is not possible.
This patch addresses this limitation by inserting a within-partition
firmware image (derived from the "SLOF" free Open Firmware project).
If -kernel is not specified, qemu will now load the SLOF image, which
has access to the qemu boot device list through the device tree, and
can boot from any of the usual virtual devices.
In order to support the new firmware, an extension to the emulated
machine/hypervisor is necessary. Unlike Linux, which expects
multi-CPU entry to be handled kexec() style, the SLOF firmware expects
only one CPU to be active at entry, and to use a hypervisor RTAS
method to enable the other CPUs one by one.
This patch also implements this 'start-cpu' method, so that SLOF can
start the secondary CPUs and marshal them into the kexec() holding
pattern ready for entry into the guest OS. Linux should, and in the
future might directly use the start-cpu method to enable initially
disabled CPUs, but for now it does require kexec() entry.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-01 06:15:34 +02:00
|
|
|
_FDT((fdt_property_string(fdt, "qemu,boot-device", boot_device)));
|
2011-04-01 06:15:20 +02:00
|
|
|
|
|
|
|
|
_FDT((fdt_end_node(fdt)));
|
|
|
|
|
|
|
|
|
|
/* memory node */
|
|
|
|
|
_FDT((fdt_begin_node(fdt, "memory@0")));
|
|
|
|
|
|
|
|
|
|
_FDT((fdt_property_string(fdt, "device_type", "memory")));
|
|
|
|
|
_FDT((fdt_property(fdt, "reg",
|
|
|
|
|
mem_reg_property, sizeof(mem_reg_property))));
|
|
|
|
|
|
|
|
|
|
_FDT((fdt_end_node(fdt)));
|
|
|
|
|
|
|
|
|
|
/* cpus */
|
|
|
|
|
_FDT((fdt_begin_node(fdt, "cpus")));
|
|
|
|
|
|
|
|
|
|
_FDT((fdt_property_cell(fdt, "#address-cells", 0x1)));
|
|
|
|
|
_FDT((fdt_property_cell(fdt, "#size-cells", 0x0)));
|
|
|
|
|
|
|
|
|
|
modelname = qemu_strdup(cpu_model);
|
|
|
|
|
|
|
|
|
|
for (i = 0; i < strlen(modelname); i++) {
|
|
|
|
|
modelname[i] = toupper(modelname[i]);
|
|
|
|
|
}
|
|
|
|
|
|
2011-04-05 07:12:09 +02:00
|
|
|
for (env = first_cpu; env != NULL; env = env->next_cpu) {
|
|
|
|
|
int index = env->cpu_index;
|
|
|
|
|
uint32_t gserver_prop[] = {cpu_to_be32(index), 0}; /* HACK! */
|
2011-04-01 06:15:20 +02:00
|
|
|
char *nodename;
|
|
|
|
|
uint32_t segs[] = {cpu_to_be32(28), cpu_to_be32(40),
|
|
|
|
|
0xffffffff, 0xffffffff};
|
|
|
|
|
|
2011-04-05 07:12:09 +02:00
|
|
|
if (asprintf(&nodename, "%s@%x", modelname, index) < 0) {
|
2011-04-01 06:15:20 +02:00
|
|
|
fprintf(stderr, "Allocation failure\n");
|
|
|
|
|
exit(1);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
_FDT((fdt_begin_node(fdt, nodename)));
|
|
|
|
|
|
|
|
|
|
free(nodename);
|
|
|
|
|
|
2011-04-05 07:12:09 +02:00
|
|
|
_FDT((fdt_property_cell(fdt, "reg", index)));
|
2011-04-01 06:15:20 +02:00
|
|
|
_FDT((fdt_property_string(fdt, "device_type", "cpu")));
|
|
|
|
|
|
|
|
|
|
_FDT((fdt_property_cell(fdt, "cpu-version", env->spr[SPR_PVR])));
|
|
|
|
|
_FDT((fdt_property_cell(fdt, "dcache-block-size",
|
|
|
|
|
env->dcache_line_size)));
|
|
|
|
|
_FDT((fdt_property_cell(fdt, "icache-block-size",
|
|
|
|
|
env->icache_line_size)));
|
|
|
|
|
_FDT((fdt_property_cell(fdt, "timebase-frequency", TIMEBASE_FREQ)));
|
|
|
|
|
/* Hardcode CPU frequency for now. It's kind of arbitrary on
|
|
|
|
|
* full emu, for kvm we should copy it from the host */
|
|
|
|
|
_FDT((fdt_property_cell(fdt, "clock-frequency", 1000000000)));
|
|
|
|
|
_FDT((fdt_property_cell(fdt, "ibm,slb-size", env->slb_nr)));
|
2011-04-01 06:15:22 +02:00
|
|
|
_FDT((fdt_property(fdt, "ibm,pft-size",
|
|
|
|
|
pft_size_prop, sizeof(pft_size_prop))));
|
2011-04-01 06:15:20 +02:00
|
|
|
_FDT((fdt_property_string(fdt, "status", "okay")));
|
|
|
|
|
_FDT((fdt_property(fdt, "64-bit", NULL, 0)));
|
2011-04-05 07:12:09 +02:00
|
|
|
_FDT((fdt_property_cell(fdt, "ibm,ppc-interrupt-server#s", index)));
|
Implement the PAPR (pSeries) virtualized interrupt controller (xics)
PAPR defines an interrupt control architecture which is logically divided
into ICS (Interrupt Control Presentation, each unit is responsible for
presenting interrupts to a particular "interrupt server", i.e. CPU) and
ICS (Interrupt Control Source, each unit responsible for one or more
hardware interrupts as numbered globally across the system). All PAPR
virtual IO devices expect to deliver interrupts via this mechanism. In
Linux, this interrupt controller system is handled by the "xics" driver.
On pSeries systems, access to the interrupt controller is virtualized via
hypercalls and RTAS methods. However, the virtualized interface is very
similar to the underlying interrupt controller hardware, and similar PICs
exist un-virtualized in some other systems.
This patch implements both the ICP and ICS sides of the PAPR interrupt
controller. For now, only the hypercall virtualized interface is provided,
however it would be relatively straightforward to graft an emulated
register interface onto the underlying interrupt logic if we want to add
a machine with a hardware ICS/ICP system in the future.
There are some limitations in this implementation: it is assumed for now
that only one instance of the ICS exists, although a full xics system can
have several, each responsible for a different group of hardware irqs.
ICP/ICS can handle both level-sensitve (LSI) and message signalled (MSI)
interrupt inputs. For now, this implementation supports only MSI
interrupts, since that is used by PAPR virtual IO devices.
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-01 06:15:25 +02:00
|
|
|
_FDT((fdt_property(fdt, "ibm,ppc-interrupt-gserver#s",
|
|
|
|
|
gserver_prop, sizeof(gserver_prop))));
|
2011-04-01 06:15:20 +02:00
|
|
|
|
2011-04-05 07:12:09 +02:00
|
|
|
if (env->mmu_model & POWERPC_MMU_1TSEG) {
|
2011-04-01 06:15:20 +02:00
|
|
|
_FDT((fdt_property(fdt, "ibm,processor-segment-sizes",
|
|
|
|
|
segs, sizeof(segs))));
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
_FDT((fdt_end_node(fdt)));
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
qemu_free(modelname);
|
|
|
|
|
|
|
|
|
|
_FDT((fdt_end_node(fdt)));
|
|
|
|
|
|
2011-04-01 06:15:22 +02:00
|
|
|
/* RTAS */
|
|
|
|
|
_FDT((fdt_begin_node(fdt, "rtas")));
|
|
|
|
|
|
|
|
|
|
_FDT((fdt_property(fdt, "ibm,hypertas-functions", hypertas_prop,
|
|
|
|
|
sizeof(hypertas_prop))));
|
|
|
|
|
|
|
|
|
|
_FDT((fdt_end_node(fdt)));
|
|
|
|
|
|
Implement the PAPR (pSeries) virtualized interrupt controller (xics)
PAPR defines an interrupt control architecture which is logically divided
into ICS (Interrupt Control Presentation, each unit is responsible for
presenting interrupts to a particular "interrupt server", i.e. CPU) and
ICS (Interrupt Control Source, each unit responsible for one or more
hardware interrupts as numbered globally across the system). All PAPR
virtual IO devices expect to deliver interrupts via this mechanism. In
Linux, this interrupt controller system is handled by the "xics" driver.
On pSeries systems, access to the interrupt controller is virtualized via
hypercalls and RTAS methods. However, the virtualized interface is very
similar to the underlying interrupt controller hardware, and similar PICs
exist un-virtualized in some other systems.
This patch implements both the ICP and ICS sides of the PAPR interrupt
controller. For now, only the hypercall virtualized interface is provided,
however it would be relatively straightforward to graft an emulated
register interface onto the underlying interrupt logic if we want to add
a machine with a hardware ICS/ICP system in the future.
There are some limitations in this implementation: it is assumed for now
that only one instance of the ICS exists, although a full xics system can
have several, each responsible for a different group of hardware irqs.
ICP/ICS can handle both level-sensitve (LSI) and message signalled (MSI)
interrupt inputs. For now, this implementation supports only MSI
interrupts, since that is used by PAPR virtual IO devices.
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-01 06:15:25 +02:00
|
|
|
/* interrupt controller */
|
|
|
|
|
_FDT((fdt_begin_node(fdt, "interrupt-controller@0")));
|
|
|
|
|
|
|
|
|
|
_FDT((fdt_property_string(fdt, "device_type",
|
|
|
|
|
"PowerPC-External-Interrupt-Presentation")));
|
|
|
|
|
_FDT((fdt_property_string(fdt, "compatible", "IBM,ppc-xicp")));
|
|
|
|
|
_FDT((fdt_property_cell(fdt, "reg", 0)));
|
|
|
|
|
_FDT((fdt_property(fdt, "interrupt-controller", NULL, 0)));
|
|
|
|
|
_FDT((fdt_property(fdt, "ibm,interrupt-server-ranges",
|
|
|
|
|
interrupt_server_ranges_prop,
|
|
|
|
|
sizeof(interrupt_server_ranges_prop))));
|
|
|
|
|
|
|
|
|
|
_FDT((fdt_end_node(fdt)));
|
|
|
|
|
|
2011-04-01 06:15:21 +02:00
|
|
|
/* vdevice */
|
|
|
|
|
_FDT((fdt_begin_node(fdt, "vdevice")));
|
|
|
|
|
|
|
|
|
|
_FDT((fdt_property_string(fdt, "device_type", "vdevice")));
|
|
|
|
|
_FDT((fdt_property_string(fdt, "compatible", "IBM,vdevice")));
|
|
|
|
|
_FDT((fdt_property_cell(fdt, "#address-cells", 0x1)));
|
|
|
|
|
_FDT((fdt_property_cell(fdt, "#size-cells", 0x0)));
|
Implement the PAPR (pSeries) virtualized interrupt controller (xics)
PAPR defines an interrupt control architecture which is logically divided
into ICS (Interrupt Control Presentation, each unit is responsible for
presenting interrupts to a particular "interrupt server", i.e. CPU) and
ICS (Interrupt Control Source, each unit responsible for one or more
hardware interrupts as numbered globally across the system). All PAPR
virtual IO devices expect to deliver interrupts via this mechanism. In
Linux, this interrupt controller system is handled by the "xics" driver.
On pSeries systems, access to the interrupt controller is virtualized via
hypercalls and RTAS methods. However, the virtualized interface is very
similar to the underlying interrupt controller hardware, and similar PICs
exist un-virtualized in some other systems.
This patch implements both the ICP and ICS sides of the PAPR interrupt
controller. For now, only the hypercall virtualized interface is provided,
however it would be relatively straightforward to graft an emulated
register interface onto the underlying interrupt logic if we want to add
a machine with a hardware ICS/ICP system in the future.
There are some limitations in this implementation: it is assumed for now
that only one instance of the ICS exists, although a full xics system can
have several, each responsible for a different group of hardware irqs.
ICP/ICS can handle both level-sensitve (LSI) and message signalled (MSI)
interrupt inputs. For now, this implementation supports only MSI
interrupts, since that is used by PAPR virtual IO devices.
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-01 06:15:25 +02:00
|
|
|
_FDT((fdt_property_cell(fdt, "#interrupt-cells", 0x2)));
|
|
|
|
|
_FDT((fdt_property(fdt, "interrupt-controller", NULL, 0)));
|
2011-04-01 06:15:21 +02:00
|
|
|
|
|
|
|
|
_FDT((fdt_end_node(fdt)));
|
|
|
|
|
|
2011-04-01 06:15:20 +02:00
|
|
|
_FDT((fdt_end_node(fdt))); /* close root node */
|
|
|
|
|
_FDT((fdt_finish(fdt)));
|
|
|
|
|
|
Delay creation of pseries device tree until reset
At present, the 'pseries' machine creates a flattened device tree in the
machine->init function to pass to either the guest kernel or to firmware.
However, the machine->init function runs before processing of -device
command line options, which means that the device tree so created will
be (incorrectly) missing devices specified that way.
Supplying a correct device tree is, in any case, part of the required
platform entry conditions. Therefore, this patch moves the creation and
loading of the device tree from machine->init to a reset callback. The
setup of entry point address and initial register state moves with it,
which leads to a slight cleanup.
This is not, alas, quite enough to make a fully working reset for pseries.
For that we would need to reload the firmware images, which on this
machine are loaded into RAM. It's a step in the right direction, though.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-05 07:12:10 +02:00
|
|
|
return fdt;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void spapr_finalize_fdt(sPAPREnvironment *spapr,
|
|
|
|
|
target_phys_addr_t fdt_addr,
|
|
|
|
|
target_phys_addr_t rtas_addr,
|
|
|
|
|
target_phys_addr_t rtas_size)
|
|
|
|
|
{
|
|
|
|
|
int ret;
|
|
|
|
|
void *fdt;
|
|
|
|
|
|
|
|
|
|
fdt = qemu_malloc(FDT_MAX_SIZE);
|
|
|
|
|
|
|
|
|
|
/* open out the base tree into a temp buffer for the final tweaks */
|
|
|
|
|
_FDT((fdt_open_into(spapr->fdt_skel, fdt, FDT_MAX_SIZE)));
|
2011-04-01 06:15:21 +02:00
|
|
|
|
|
|
|
|
ret = spapr_populate_vdevice(spapr->vio_bus, fdt);
|
|
|
|
|
if (ret < 0) {
|
|
|
|
|
fprintf(stderr, "couldn't setup vio devices in fdt\n");
|
|
|
|
|
exit(1);
|
|
|
|
|
}
|
|
|
|
|
|
2011-04-01 06:15:23 +02:00
|
|
|
/* RTAS */
|
|
|
|
|
ret = spapr_rtas_device_tree_setup(fdt, rtas_addr, rtas_size);
|
|
|
|
|
if (ret < 0) {
|
|
|
|
|
fprintf(stderr, "Couldn't set up RTAS device tree properties\n");
|
|
|
|
|
}
|
|
|
|
|
|
2011-04-01 06:15:21 +02:00
|
|
|
_FDT((fdt_pack(fdt)));
|
|
|
|
|
|
Delay creation of pseries device tree until reset
At present, the 'pseries' machine creates a flattened device tree in the
machine->init function to pass to either the guest kernel or to firmware.
However, the machine->init function runs before processing of -device
command line options, which means that the device tree so created will
be (incorrectly) missing devices specified that way.
Supplying a correct device tree is, in any case, part of the required
platform entry conditions. Therefore, this patch moves the creation and
loading of the device tree from machine->init to a reset callback. The
setup of entry point address and initial register state moves with it,
which leads to a slight cleanup.
This is not, alas, quite enough to make a fully working reset for pseries.
For that we would need to reload the firmware images, which on this
machine are loaded into RAM. It's a step in the right direction, though.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-05 07:12:10 +02:00
|
|
|
cpu_physical_memory_write(fdt_addr, fdt, fdt_totalsize(fdt));
|
2011-04-01 06:15:20 +02:00
|
|
|
|
Delay creation of pseries device tree until reset
At present, the 'pseries' machine creates a flattened device tree in the
machine->init function to pass to either the guest kernel or to firmware.
However, the machine->init function runs before processing of -device
command line options, which means that the device tree so created will
be (incorrectly) missing devices specified that way.
Supplying a correct device tree is, in any case, part of the required
platform entry conditions. Therefore, this patch moves the creation and
loading of the device tree from machine->init to a reset callback. The
setup of entry point address and initial register state moves with it,
which leads to a slight cleanup.
This is not, alas, quite enough to make a fully working reset for pseries.
For that we would need to reload the firmware images, which on this
machine are loaded into RAM. It's a step in the right direction, though.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-05 07:12:10 +02:00
|
|
|
qemu_free(fdt);
|
2011-04-01 06:15:20 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static uint64_t translate_kernel_address(void *opaque, uint64_t addr)
|
|
|
|
|
{
|
|
|
|
|
return (addr & 0x0fffffff) + KERNEL_LOAD_ADDR;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void emulate_spapr_hypercall(CPUState *env)
|
|
|
|
|
{
|
|
|
|
|
env->gpr[3] = spapr_hypercall(env, env->gpr[3], &env->gpr[4]);
|
|
|
|
|
}
|
|
|
|
|
|
Delay creation of pseries device tree until reset
At present, the 'pseries' machine creates a flattened device tree in the
machine->init function to pass to either the guest kernel or to firmware.
However, the machine->init function runs before processing of -device
command line options, which means that the device tree so created will
be (incorrectly) missing devices specified that way.
Supplying a correct device tree is, in any case, part of the required
platform entry conditions. Therefore, this patch moves the creation and
loading of the device tree from machine->init to a reset callback. The
setup of entry point address and initial register state moves with it,
which leads to a slight cleanup.
This is not, alas, quite enough to make a fully working reset for pseries.
For that we would need to reload the firmware images, which on this
machine are loaded into RAM. It's a step in the right direction, though.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-05 07:12:10 +02:00
|
|
|
static void spapr_reset(void *opaque)
|
|
|
|
|
{
|
|
|
|
|
sPAPREnvironment *spapr = (sPAPREnvironment *)opaque;
|
|
|
|
|
|
|
|
|
|
fprintf(stderr, "sPAPR reset\n");
|
|
|
|
|
|
|
|
|
|
/* flush out the hash table */
|
|
|
|
|
memset(spapr->htab, 0, spapr->htab_size);
|
|
|
|
|
|
|
|
|
|
/* Load the fdt */
|
|
|
|
|
spapr_finalize_fdt(spapr, spapr->fdt_addr, spapr->rtas_addr,
|
|
|
|
|
spapr->rtas_size);
|
|
|
|
|
|
|
|
|
|
/* Set up the entry state */
|
|
|
|
|
first_cpu->gpr[3] = spapr->fdt_addr;
|
|
|
|
|
first_cpu->gpr[5] = 0;
|
|
|
|
|
first_cpu->halted = 0;
|
|
|
|
|
first_cpu->nip = spapr->entry_point;
|
|
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
2011-04-01 06:15:20 +02:00
|
|
|
/* pSeries LPAR / sPAPR hardware init */
|
|
|
|
|
static void ppc_spapr_init(ram_addr_t ram_size,
|
|
|
|
|
const char *boot_device,
|
|
|
|
|
const char *kernel_filename,
|
|
|
|
|
const char *kernel_cmdline,
|
|
|
|
|
const char *initrd_filename,
|
|
|
|
|
const char *cpu_model)
|
|
|
|
|
{
|
2011-04-05 07:12:09 +02:00
|
|
|
CPUState *env;
|
2011-04-01 06:15:20 +02:00
|
|
|
int i;
|
|
|
|
|
ram_addr_t ram_offset;
|
Delay creation of pseries device tree until reset
At present, the 'pseries' machine creates a flattened device tree in the
machine->init function to pass to either the guest kernel or to firmware.
However, the machine->init function runs before processing of -device
command line options, which means that the device tree so created will
be (incorrectly) missing devices specified that way.
Supplying a correct device tree is, in any case, part of the required
platform entry conditions. Therefore, this patch moves the creation and
loading of the device tree from machine->init to a reset callback. The
setup of entry point address and initial register state moves with it,
which leads to a slight cleanup.
This is not, alas, quite enough to make a fully working reset for pseries.
For that we would need to reload the firmware images, which on this
machine are loaded into RAM. It's a step in the right direction, though.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-05 07:12:10 +02:00
|
|
|
uint32_t initrd_base;
|
|
|
|
|
long kernel_size, initrd_size, fw_size;
|
2011-04-01 06:15:22 +02:00
|
|
|
long pteg_shift = 17;
|
2011-04-01 06:15:23 +02:00
|
|
|
char *filename;
|
2011-04-01 06:15:27 +02:00
|
|
|
int irq = 16;
|
2011-04-01 06:15:20 +02:00
|
|
|
|
|
|
|
|
spapr = qemu_malloc(sizeof(*spapr));
|
|
|
|
|
cpu_ppc_hypercall = emulate_spapr_hypercall;
|
|
|
|
|
|
|
|
|
|
/* We place the device tree just below either the top of RAM, or
|
|
|
|
|
* 2GB, so that it can be processed with 32-bit code if
|
|
|
|
|
* necessary */
|
Delay creation of pseries device tree until reset
At present, the 'pseries' machine creates a flattened device tree in the
machine->init function to pass to either the guest kernel or to firmware.
However, the machine->init function runs before processing of -device
command line options, which means that the device tree so created will
be (incorrectly) missing devices specified that way.
Supplying a correct device tree is, in any case, part of the required
platform entry conditions. Therefore, this patch moves the creation and
loading of the device tree from machine->init to a reset callback. The
setup of entry point address and initial register state moves with it,
which leads to a slight cleanup.
This is not, alas, quite enough to make a fully working reset for pseries.
For that we would need to reload the firmware images, which on this
machine are loaded into RAM. It's a step in the right direction, though.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-05 07:12:10 +02:00
|
|
|
spapr->fdt_addr = MIN(ram_size, 0x80000000) - FDT_MAX_SIZE;
|
|
|
|
|
spapr->rtas_addr = spapr->fdt_addr - RTAS_MAX_SIZE;
|
2011-04-01 06:15:20 +02:00
|
|
|
|
|
|
|
|
/* init CPUs */
|
|
|
|
|
if (cpu_model == NULL) {
|
|
|
|
|
cpu_model = "POWER7";
|
|
|
|
|
}
|
|
|
|
|
for (i = 0; i < smp_cpus; i++) {
|
2011-04-05 07:12:09 +02:00
|
|
|
env = cpu_init(cpu_model);
|
2011-04-01 06:15:20 +02:00
|
|
|
|
|
|
|
|
if (!env) {
|
|
|
|
|
fprintf(stderr, "Unable to find PowerPC CPU definition\n");
|
|
|
|
|
exit(1);
|
|
|
|
|
}
|
|
|
|
|
/* Set time-base frequency to 512 MHz */
|
|
|
|
|
cpu_ppc_tb_init(env, TIMEBASE_FREQ);
|
|
|
|
|
qemu_register_reset((QEMUResetHandler *)&cpu_reset, env);
|
|
|
|
|
|
|
|
|
|
env->hreset_vector = 0x60;
|
|
|
|
|
env->hreset_excp_prefix = 0;
|
2011-04-05 07:12:09 +02:00
|
|
|
env->gpr[3] = env->cpu_index;
|
2011-04-01 06:15:20 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* allocate RAM */
|
|
|
|
|
ram_offset = qemu_ram_alloc(NULL, "ppc_spapr.ram", ram_size);
|
|
|
|
|
cpu_register_physical_memory(0, ram_size, ram_offset);
|
|
|
|
|
|
2011-04-01 06:15:22 +02:00
|
|
|
/* allocate hash page table. For now we always make this 16mb,
|
|
|
|
|
* later we should probably make it scale to the size of guest
|
|
|
|
|
* RAM */
|
Delay creation of pseries device tree until reset
At present, the 'pseries' machine creates a flattened device tree in the
machine->init function to pass to either the guest kernel or to firmware.
However, the machine->init function runs before processing of -device
command line options, which means that the device tree so created will
be (incorrectly) missing devices specified that way.
Supplying a correct device tree is, in any case, part of the required
platform entry conditions. Therefore, this patch moves the creation and
loading of the device tree from machine->init to a reset callback. The
setup of entry point address and initial register state moves with it,
which leads to a slight cleanup.
This is not, alas, quite enough to make a fully working reset for pseries.
For that we would need to reload the firmware images, which on this
machine are loaded into RAM. It's a step in the right direction, though.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-05 07:12:10 +02:00
|
|
|
spapr->htab_size = 1ULL << (pteg_shift + 7);
|
|
|
|
|
spapr->htab = qemu_malloc(spapr->htab_size);
|
2011-04-01 06:15:22 +02:00
|
|
|
|
2011-04-05 07:12:09 +02:00
|
|
|
for (env = first_cpu; env != NULL; env = env->next_cpu) {
|
Delay creation of pseries device tree until reset
At present, the 'pseries' machine creates a flattened device tree in the
machine->init function to pass to either the guest kernel or to firmware.
However, the machine->init function runs before processing of -device
command line options, which means that the device tree so created will
be (incorrectly) missing devices specified that way.
Supplying a correct device tree is, in any case, part of the required
platform entry conditions. Therefore, this patch moves the creation and
loading of the device tree from machine->init to a reset callback. The
setup of entry point address and initial register state moves with it,
which leads to a slight cleanup.
This is not, alas, quite enough to make a fully working reset for pseries.
For that we would need to reload the firmware images, which on this
machine are loaded into RAM. It's a step in the right direction, though.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-05 07:12:10 +02:00
|
|
|
env->external_htab = spapr->htab;
|
2011-04-05 07:12:09 +02:00
|
|
|
env->htab_base = -1;
|
Delay creation of pseries device tree until reset
At present, the 'pseries' machine creates a flattened device tree in the
machine->init function to pass to either the guest kernel or to firmware.
However, the machine->init function runs before processing of -device
command line options, which means that the device tree so created will
be (incorrectly) missing devices specified that way.
Supplying a correct device tree is, in any case, part of the required
platform entry conditions. Therefore, this patch moves the creation and
loading of the device tree from machine->init to a reset callback. The
setup of entry point address and initial register state moves with it,
which leads to a slight cleanup.
This is not, alas, quite enough to make a fully working reset for pseries.
For that we would need to reload the firmware images, which on this
machine are loaded into RAM. It's a step in the right direction, though.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-05 07:12:10 +02:00
|
|
|
env->htab_mask = spapr->htab_size - 1;
|
2011-04-01 06:15:22 +02:00
|
|
|
}
|
|
|
|
|
|
2011-04-01 06:15:23 +02:00
|
|
|
filename = qemu_find_file(QEMU_FILE_TYPE_BIOS, "spapr-rtas.bin");
|
Delay creation of pseries device tree until reset
At present, the 'pseries' machine creates a flattened device tree in the
machine->init function to pass to either the guest kernel or to firmware.
However, the machine->init function runs before processing of -device
command line options, which means that the device tree so created will
be (incorrectly) missing devices specified that way.
Supplying a correct device tree is, in any case, part of the required
platform entry conditions. Therefore, this patch moves the creation and
loading of the device tree from machine->init to a reset callback. The
setup of entry point address and initial register state moves with it,
which leads to a slight cleanup.
This is not, alas, quite enough to make a fully working reset for pseries.
For that we would need to reload the firmware images, which on this
machine are loaded into RAM. It's a step in the right direction, though.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-05 07:12:10 +02:00
|
|
|
spapr->rtas_size = load_image_targphys(filename, spapr->rtas_addr,
|
|
|
|
|
ram_size - spapr->rtas_addr);
|
|
|
|
|
if (spapr->rtas_size < 0) {
|
2011-04-01 06:15:23 +02:00
|
|
|
hw_error("qemu: could not load LPAR rtas '%s'\n", filename);
|
|
|
|
|
exit(1);
|
|
|
|
|
}
|
|
|
|
|
qemu_free(filename);
|
|
|
|
|
|
Implement the PAPR (pSeries) virtualized interrupt controller (xics)
PAPR defines an interrupt control architecture which is logically divided
into ICS (Interrupt Control Presentation, each unit is responsible for
presenting interrupts to a particular "interrupt server", i.e. CPU) and
ICS (Interrupt Control Source, each unit responsible for one or more
hardware interrupts as numbered globally across the system). All PAPR
virtual IO devices expect to deliver interrupts via this mechanism. In
Linux, this interrupt controller system is handled by the "xics" driver.
On pSeries systems, access to the interrupt controller is virtualized via
hypercalls and RTAS methods. However, the virtualized interface is very
similar to the underlying interrupt controller hardware, and similar PICs
exist un-virtualized in some other systems.
This patch implements both the ICP and ICS sides of the PAPR interrupt
controller. For now, only the hypercall virtualized interface is provided,
however it would be relatively straightforward to graft an emulated
register interface onto the underlying interrupt logic if we want to add
a machine with a hardware ICS/ICP system in the future.
There are some limitations in this implementation: it is assumed for now
that only one instance of the ICS exists, although a full xics system can
have several, each responsible for a different group of hardware irqs.
ICP/ICS can handle both level-sensitve (LSI) and message signalled (MSI)
interrupt inputs. For now, this implementation supports only MSI
interrupts, since that is used by PAPR virtual IO devices.
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-01 06:15:25 +02:00
|
|
|
/* Set up Interrupt Controller */
|
2011-04-05 07:12:09 +02:00
|
|
|
spapr->icp = xics_system_init(XICS_IRQS);
|
Implement the PAPR (pSeries) virtualized interrupt controller (xics)
PAPR defines an interrupt control architecture which is logically divided
into ICS (Interrupt Control Presentation, each unit is responsible for
presenting interrupts to a particular "interrupt server", i.e. CPU) and
ICS (Interrupt Control Source, each unit responsible for one or more
hardware interrupts as numbered globally across the system). All PAPR
virtual IO devices expect to deliver interrupts via this mechanism. In
Linux, this interrupt controller system is handled by the "xics" driver.
On pSeries systems, access to the interrupt controller is virtualized via
hypercalls and RTAS methods. However, the virtualized interface is very
similar to the underlying interrupt controller hardware, and similar PICs
exist un-virtualized in some other systems.
This patch implements both the ICP and ICS sides of the PAPR interrupt
controller. For now, only the hypercall virtualized interface is provided,
however it would be relatively straightforward to graft an emulated
register interface onto the underlying interrupt logic if we want to add
a machine with a hardware ICS/ICP system in the future.
There are some limitations in this implementation: it is assumed for now
that only one instance of the ICS exists, although a full xics system can
have several, each responsible for a different group of hardware irqs.
ICP/ICS can handle both level-sensitve (LSI) and message signalled (MSI)
interrupt inputs. For now, this implementation supports only MSI
interrupts, since that is used by PAPR virtual IO devices.
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-01 06:15:25 +02:00
|
|
|
|
|
|
|
|
/* Set up VIO bus */
|
2011-04-01 06:15:21 +02:00
|
|
|
spapr->vio_bus = spapr_vio_bus_init();
|
|
|
|
|
|
2011-04-01 06:15:27 +02:00
|
|
|
for (i = 0; i < MAX_SERIAL_PORTS; i++, irq++) {
|
2011-04-01 06:15:21 +02:00
|
|
|
if (serial_hds[i]) {
|
2011-04-19 03:54:52 +02:00
|
|
|
spapr_vty_create(spapr->vio_bus, SPAPR_VTY_BASE_ADDRESS + i,
|
|
|
|
|
serial_hds[i], xics_find_qirq(spapr->icp, irq),
|
|
|
|
|
irq);
|
2011-04-01 06:15:21 +02:00
|
|
|
}
|
|
|
|
|
}
|
2011-04-01 06:15:20 +02:00
|
|
|
|
2011-04-01 06:15:29 +02:00
|
|
|
for (i = 0; i < nb_nics; i++, irq++) {
|
|
|
|
|
NICInfo *nd = &nd_table[i];
|
|
|
|
|
|
|
|
|
|
if (!nd->model) {
|
|
|
|
|
nd->model = qemu_strdup("ibmveth");
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if (strcmp(nd->model, "ibmveth") == 0) {
|
|
|
|
|
spapr_vlan_create(spapr->vio_bus, 0x1000 + i, nd,
|
|
|
|
|
xics_find_qirq(spapr->icp, irq), irq);
|
|
|
|
|
} else {
|
|
|
|
|
fprintf(stderr, "pSeries (sPAPR) platform does not support "
|
|
|
|
|
"NIC model '%s' (only ibmveth is supported)\n",
|
|
|
|
|
nd->model);
|
|
|
|
|
exit(1);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2011-04-01 06:15:31 +02:00
|
|
|
for (i = 0; i <= drive_get_max_bus(IF_SCSI); i++) {
|
|
|
|
|
spapr_vscsi_create(spapr->vio_bus, 0x2000 + i,
|
|
|
|
|
xics_find_qirq(spapr->icp, irq), irq);
|
|
|
|
|
irq++;
|
|
|
|
|
}
|
|
|
|
|
|
2011-04-01 06:15:20 +02:00
|
|
|
if (kernel_filename) {
|
|
|
|
|
uint64_t lowaddr = 0;
|
|
|
|
|
|
|
|
|
|
kernel_size = load_elf(kernel_filename, translate_kernel_address, NULL,
|
|
|
|
|
NULL, &lowaddr, NULL, 1, ELF_MACHINE, 0);
|
|
|
|
|
if (kernel_size < 0) {
|
Delay creation of pseries device tree until reset
At present, the 'pseries' machine creates a flattened device tree in the
machine->init function to pass to either the guest kernel or to firmware.
However, the machine->init function runs before processing of -device
command line options, which means that the device tree so created will
be (incorrectly) missing devices specified that way.
Supplying a correct device tree is, in any case, part of the required
platform entry conditions. Therefore, this patch moves the creation and
loading of the device tree from machine->init to a reset callback. The
setup of entry point address and initial register state moves with it,
which leads to a slight cleanup.
This is not, alas, quite enough to make a fully working reset for pseries.
For that we would need to reload the firmware images, which on this
machine are loaded into RAM. It's a step in the right direction, though.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-05 07:12:10 +02:00
|
|
|
kernel_size = load_image_targphys(kernel_filename,
|
|
|
|
|
KERNEL_LOAD_ADDR,
|
|
|
|
|
ram_size - KERNEL_LOAD_ADDR);
|
2011-04-01 06:15:20 +02:00
|
|
|
}
|
|
|
|
|
if (kernel_size < 0) {
|
|
|
|
|
fprintf(stderr, "qemu: could not load kernel '%s'\n",
|
|
|
|
|
kernel_filename);
|
|
|
|
|
exit(1);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* load initrd */
|
|
|
|
|
if (initrd_filename) {
|
|
|
|
|
initrd_base = INITRD_LOAD_ADDR;
|
|
|
|
|
initrd_size = load_image_targphys(initrd_filename, initrd_base,
|
|
|
|
|
ram_size - initrd_base);
|
|
|
|
|
if (initrd_size < 0) {
|
|
|
|
|
fprintf(stderr, "qemu: could not load initial ram disk '%s'\n",
|
|
|
|
|
initrd_filename);
|
|
|
|
|
exit(1);
|
|
|
|
|
}
|
|
|
|
|
} else {
|
|
|
|
|
initrd_base = 0;
|
|
|
|
|
initrd_size = 0;
|
|
|
|
|
}
|
Delay creation of pseries device tree until reset
At present, the 'pseries' machine creates a flattened device tree in the
machine->init function to pass to either the guest kernel or to firmware.
However, the machine->init function runs before processing of -device
command line options, which means that the device tree so created will
be (incorrectly) missing devices specified that way.
Supplying a correct device tree is, in any case, part of the required
platform entry conditions. Therefore, this patch moves the creation and
loading of the device tree from machine->init to a reset callback. The
setup of entry point address and initial register state moves with it,
which leads to a slight cleanup.
This is not, alas, quite enough to make a fully working reset for pseries.
For that we would need to reload the firmware images, which on this
machine are loaded into RAM. It's a step in the right direction, though.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-05 07:12:10 +02:00
|
|
|
|
|
|
|
|
spapr->entry_point = KERNEL_LOAD_ADDR;
|
2011-04-01 06:15:20 +02:00
|
|
|
} else {
|
Add SLOF-based partition firmware for pSeries machine, allowing more boot options
Currently, the emulated pSeries machine requires the use of the
-kernel parameter in order to explicitly load a guest kernel. This
means booting from the virtual disk, cdrom or network is not possible.
This patch addresses this limitation by inserting a within-partition
firmware image (derived from the "SLOF" free Open Firmware project).
If -kernel is not specified, qemu will now load the SLOF image, which
has access to the qemu boot device list through the device tree, and
can boot from any of the usual virtual devices.
In order to support the new firmware, an extension to the emulated
machine/hypervisor is necessary. Unlike Linux, which expects
multi-CPU entry to be handled kexec() style, the SLOF firmware expects
only one CPU to be active at entry, and to use a hypervisor RTAS
method to enable the other CPUs one by one.
This patch also implements this 'start-cpu' method, so that SLOF can
start the secondary CPUs and marshal them into the kexec() holding
pattern ready for entry into the guest OS. Linux should, and in the
future might directly use the start-cpu method to enable initially
disabled CPUs, but for now it does require kexec() entry.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-01 06:15:34 +02:00
|
|
|
if (ram_size < (MIN_RAM_SLOF << 20)) {
|
|
|
|
|
fprintf(stderr, "qemu: pSeries SLOF firmware requires >= "
|
|
|
|
|
"%ldM guest RAM\n", MIN_RAM_SLOF);
|
|
|
|
|
exit(1);
|
|
|
|
|
}
|
|
|
|
|
filename = qemu_find_file(QEMU_FILE_TYPE_BIOS, "slof.bin");
|
|
|
|
|
fw_size = load_image_targphys(filename, 0, FW_MAX_SIZE);
|
|
|
|
|
if (fw_size < 0) {
|
|
|
|
|
hw_error("qemu: could not load LPAR rtas '%s'\n", filename);
|
|
|
|
|
exit(1);
|
|
|
|
|
}
|
|
|
|
|
qemu_free(filename);
|
Delay creation of pseries device tree until reset
At present, the 'pseries' machine creates a flattened device tree in the
machine->init function to pass to either the guest kernel or to firmware.
However, the machine->init function runs before processing of -device
command line options, which means that the device tree so created will
be (incorrectly) missing devices specified that way.
Supplying a correct device tree is, in any case, part of the required
platform entry conditions. Therefore, this patch moves the creation and
loading of the device tree from machine->init to a reset callback. The
setup of entry point address and initial register state moves with it,
which leads to a slight cleanup.
This is not, alas, quite enough to make a fully working reset for pseries.
For that we would need to reload the firmware images, which on this
machine are loaded into RAM. It's a step in the right direction, though.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-05 07:12:10 +02:00
|
|
|
spapr->entry_point = 0x100;
|
Add SLOF-based partition firmware for pSeries machine, allowing more boot options
Currently, the emulated pSeries machine requires the use of the
-kernel parameter in order to explicitly load a guest kernel. This
means booting from the virtual disk, cdrom or network is not possible.
This patch addresses this limitation by inserting a within-partition
firmware image (derived from the "SLOF" free Open Firmware project).
If -kernel is not specified, qemu will now load the SLOF image, which
has access to the qemu boot device list through the device tree, and
can boot from any of the usual virtual devices.
In order to support the new firmware, an extension to the emulated
machine/hypervisor is necessary. Unlike Linux, which expects
multi-CPU entry to be handled kexec() style, the SLOF firmware expects
only one CPU to be active at entry, and to use a hypervisor RTAS
method to enable the other CPUs one by one.
This patch also implements this 'start-cpu' method, so that SLOF can
start the secondary CPUs and marshal them into the kexec() holding
pattern ready for entry into the guest OS. Linux should, and in the
future might directly use the start-cpu method to enable initially
disabled CPUs, but for now it does require kexec() entry.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-01 06:15:34 +02:00
|
|
|
initrd_base = 0;
|
|
|
|
|
initrd_size = 0;
|
|
|
|
|
|
|
|
|
|
/* SLOF will startup the secondary CPUs using RTAS,
|
|
|
|
|
rather than expecting a kexec() style entry */
|
2011-04-05 07:12:09 +02:00
|
|
|
for (env = first_cpu; env != NULL; env = env->next_cpu) {
|
|
|
|
|
env->halted = 1;
|
Add SLOF-based partition firmware for pSeries machine, allowing more boot options
Currently, the emulated pSeries machine requires the use of the
-kernel parameter in order to explicitly load a guest kernel. This
means booting from the virtual disk, cdrom or network is not possible.
This patch addresses this limitation by inserting a within-partition
firmware image (derived from the "SLOF" free Open Firmware project).
If -kernel is not specified, qemu will now load the SLOF image, which
has access to the qemu boot device list through the device tree, and
can boot from any of the usual virtual devices.
In order to support the new firmware, an extension to the emulated
machine/hypervisor is necessary. Unlike Linux, which expects
multi-CPU entry to be handled kexec() style, the SLOF firmware expects
only one CPU to be active at entry, and to use a hypervisor RTAS
method to enable the other CPUs one by one.
This patch also implements this 'start-cpu' method, so that SLOF can
start the secondary CPUs and marshal them into the kexec() holding
pattern ready for entry into the guest OS. Linux should, and in the
future might directly use the start-cpu method to enable initially
disabled CPUs, but for now it does require kexec() entry.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-01 06:15:34 +02:00
|
|
|
}
|
2011-04-01 06:15:20 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Prepare the device tree */
|
Delay creation of pseries device tree until reset
At present, the 'pseries' machine creates a flattened device tree in the
machine->init function to pass to either the guest kernel or to firmware.
However, the machine->init function runs before processing of -device
command line options, which means that the device tree so created will
be (incorrectly) missing devices specified that way.
Supplying a correct device tree is, in any case, part of the required
platform entry conditions. Therefore, this patch moves the creation and
loading of the device tree from machine->init to a reset callback. The
setup of entry point address and initial register state moves with it,
which leads to a slight cleanup.
This is not, alas, quite enough to make a fully working reset for pseries.
For that we would need to reload the firmware images, which on this
machine are loaded into RAM. It's a step in the right direction, though.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-05 07:12:10 +02:00
|
|
|
spapr->fdt_skel = spapr_create_fdt_skel(cpu_model,
|
|
|
|
|
initrd_base, initrd_size,
|
|
|
|
|
boot_device, kernel_cmdline,
|
|
|
|
|
pteg_shift + 7);
|
|
|
|
|
assert(spapr->fdt_skel != NULL);
|
2011-04-01 06:15:20 +02:00
|
|
|
|
Delay creation of pseries device tree until reset
At present, the 'pseries' machine creates a flattened device tree in the
machine->init function to pass to either the guest kernel or to firmware.
However, the machine->init function runs before processing of -device
command line options, which means that the device tree so created will
be (incorrectly) missing devices specified that way.
Supplying a correct device tree is, in any case, part of the required
platform entry conditions. Therefore, this patch moves the creation and
loading of the device tree from machine->init to a reset callback. The
setup of entry point address and initial register state moves with it,
which leads to a slight cleanup.
This is not, alas, quite enough to make a fully working reset for pseries.
For that we would need to reload the firmware images, which on this
machine are loaded into RAM. It's a step in the right direction, though.
Signed-off-by: David Gibson <dwg@au1.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-04-05 07:12:10 +02:00
|
|
|
qemu_register_reset(spapr_reset, spapr);
|
2011-04-01 06:15:20 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static QEMUMachine spapr_machine = {
|
|
|
|
|
.name = "pseries",
|
|
|
|
|
.desc = "pSeries Logical Partition (PAPR compliant)",
|
|
|
|
|
.init = ppc_spapr_init,
|
|
|
|
|
.max_cpus = MAX_CPUS,
|
|
|
|
|
.no_vga = 1,
|
|
|
|
|
.no_parallel = 1,
|
2011-04-01 06:15:31 +02:00
|
|
|
.use_scsi = 1,
|
2011-04-01 06:15:20 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static void spapr_machine_init(void)
|
|
|
|
|
{
|
|
|
|
|
qemu_register_machine(&spapr_machine);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
machine_init(spapr_machine_init);
|