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.
|
|
|
|
*
|
|
|
|
*/
|
2012-12-17 18:20:04 +01:00
|
|
|
#include "sysemu/sysemu.h"
|
2011-04-01 06:15:20 +02:00
|
|
|
#include "hw.h"
|
|
|
|
#include "elf.h"
|
2012-10-24 08:43:34 +02:00
|
|
|
#include "net/net.h"
|
2012-12-17 18:20:04 +01:00
|
|
|
#include "sysemu/blockdev.h"
|
|
|
|
#include "sysemu/cpus.h"
|
|
|
|
#include "sysemu/kvm.h"
|
2011-09-29 23:39:10 +02:00
|
|
|
#include "kvm_ppc.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"
|
2011-10-30 18:16:46 +01:00
|
|
|
#include "hw/spapr_pci.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"
|
2012-12-12 13:24:50 +01:00
|
|
|
#include "hw/pci/msi.h"
|
2011-04-01 06:15:20 +02:00
|
|
|
|
2012-12-17 18:20:04 +01:00
|
|
|
#include "sysemu/kvm.h"
|
2011-08-09 17:57:37 +02:00
|
|
|
#include "kvm_ppc.h"
|
2012-12-12 13:24:50 +01:00
|
|
|
#include "pci/pci.h"
|
2011-08-09 17:57:37 +02:00
|
|
|
|
2012-12-17 18:19:49 +01:00
|
|
|
#include "exec/address-spaces.h"
|
2012-08-16 04:03:56 +02:00
|
|
|
#include "hw/usb.h"
|
2012-12-17 18:20:00 +01:00
|
|
|
#include "qemu/config-file.h"
|
2011-10-03 12:56:38 +02:00
|
|
|
|
2011-04-01 06:15:20 +02:00
|
|
|
#include <libfdt.h>
|
|
|
|
|
2012-01-11 20:46:28 +01:00
|
|
|
/* SLOF memory layout:
|
|
|
|
*
|
|
|
|
* SLOF raw image loaded at 0, copies its romfs right below the flat
|
|
|
|
* device-tree, then position SLOF itself 31M below that
|
|
|
|
*
|
|
|
|
* So we set FW_OVERHEAD to 40MB which should account for all of that
|
|
|
|
* and more
|
|
|
|
*
|
|
|
|
* We load our kernel at 4M, leaving space for SLOF initial image
|
|
|
|
*/
|
2011-04-01 06:15:20 +02:00
|
|
|
#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"
|
2012-01-11 20:46:28 +01:00
|
|
|
#define FW_OVERHEAD 0x2800000
|
|
|
|
#define KERNEL_LOAD_ADDR FW_MAX_SIZE
|
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
|
|
|
|
2012-01-11 20:46:28 +01:00
|
|
|
#define MIN_RMA_SLOF 128UL
|
2011-04-01 06:15:20 +02:00
|
|
|
|
|
|
|
#define TIMEBASE_FREQ 512000000ULL
|
|
|
|
|
2011-04-19 03:54:50 +02:00
|
|
|
#define MAX_CPUS 256
|
2012-01-11 20:46:28 +01:00
|
|
|
#define XICS_IRQS 1024
|
2011-04-01 06:15:20 +02:00
|
|
|
|
2011-10-30 18:16:46 +01:00
|
|
|
#define SPAPR_PCI_BUID 0x800000020000001ULL
|
|
|
|
#define SPAPR_PCI_MEM_WIN_ADDR (0x10000000000ULL + 0xA0000000)
|
|
|
|
#define SPAPR_PCI_MEM_WIN_SIZE 0x20000000
|
|
|
|
#define SPAPR_PCI_IO_WIN_ADDR (0x10000000000ULL + 0x80000000)
|
2012-08-07 18:10:37 +02:00
|
|
|
#define SPAPR_PCI_MSI_WIN_ADDR (0x10000000000ULL + 0x90000000)
|
2011-10-30 18:16:46 +01:00
|
|
|
|
2011-08-03 23:02:17 +02:00
|
|
|
#define PHANDLE_XICP 0x00001111
|
|
|
|
|
2012-09-12 18:57:12 +02:00
|
|
|
#define HTAB_SIZE(spapr) (1ULL << ((spapr)->htab_shift))
|
|
|
|
|
2011-04-01 06:15:20 +02:00
|
|
|
sPAPREnvironment *spapr;
|
|
|
|
|
2012-09-12 18:57:18 +02:00
|
|
|
int spapr_allocate_irq(int hint, bool lsi)
|
2011-09-15 22:49:49 +02:00
|
|
|
{
|
2012-08-07 18:10:32 +02:00
|
|
|
int irq;
|
2011-09-15 22:49:49 +02:00
|
|
|
|
|
|
|
if (hint) {
|
|
|
|
irq = hint;
|
|
|
|
/* FIXME: we should probably check for collisions somehow */
|
|
|
|
} else {
|
|
|
|
irq = spapr->next_irq++;
|
|
|
|
}
|
|
|
|
|
2012-08-07 18:10:32 +02:00
|
|
|
/* Configure irq type */
|
|
|
|
if (!xics_get_qirq(spapr->icp, irq)) {
|
|
|
|
return 0;
|
2011-09-15 22:49:49 +02:00
|
|
|
}
|
|
|
|
|
2012-09-12 18:57:18 +02:00
|
|
|
xics_set_irq_type(spapr->icp, irq, lsi);
|
2011-09-15 22:49:49 +02:00
|
|
|
|
2012-08-07 18:10:32 +02:00
|
|
|
return irq;
|
2011-09-15 22:49:49 +02:00
|
|
|
}
|
|
|
|
|
2012-08-07 18:10:34 +02:00
|
|
|
/* Allocate block of consequtive IRQs, returns a number of the first */
|
2012-09-12 18:57:18 +02:00
|
|
|
int spapr_allocate_irq_block(int num, bool lsi)
|
2012-08-07 18:10:34 +02:00
|
|
|
{
|
|
|
|
int first = -1;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = 0; i < num; ++i) {
|
|
|
|
int irq;
|
|
|
|
|
2012-09-12 18:57:18 +02:00
|
|
|
irq = spapr_allocate_irq(0, lsi);
|
2012-08-07 18:10:34 +02:00
|
|
|
if (!irq) {
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (0 == i) {
|
|
|
|
first = irq;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* If the above doesn't create a consecutive block then that's
|
|
|
|
* an internal bug */
|
|
|
|
assert(irq == (first + i));
|
|
|
|
}
|
|
|
|
|
|
|
|
return first;
|
|
|
|
}
|
|
|
|
|
2012-09-12 18:57:12 +02:00
|
|
|
static int spapr_fixup_cpu_dt(void *fdt, sPAPREnvironment *spapr)
|
2011-12-12 19:24:30 +01:00
|
|
|
{
|
|
|
|
int ret = 0, offset;
|
2012-03-14 01:38:23 +01:00
|
|
|
CPUPPCState *env;
|
2012-12-17 04:22:03 +01:00
|
|
|
CPUState *cpu;
|
2011-12-12 19:24:30 +01:00
|
|
|
char cpu_model[32];
|
|
|
|
int smt = kvmppc_smt_threads();
|
2012-09-12 18:57:12 +02:00
|
|
|
uint32_t pft_size_prop[] = {0, cpu_to_be32(spapr->htab_shift)};
|
2011-12-12 19:24:30 +01:00
|
|
|
|
|
|
|
assert(spapr->cpu_model);
|
|
|
|
|
|
|
|
for (env = first_cpu; env != NULL; env = env->next_cpu) {
|
2012-12-17 04:22:03 +01:00
|
|
|
cpu = ENV_GET_CPU(env);
|
2011-12-12 19:24:30 +01:00
|
|
|
uint32_t associativity[] = {cpu_to_be32(0x5),
|
|
|
|
cpu_to_be32(0x0),
|
|
|
|
cpu_to_be32(0x0),
|
|
|
|
cpu_to_be32(0x0),
|
2012-12-17 04:22:03 +01:00
|
|
|
cpu_to_be32(cpu->numa_node),
|
2011-12-12 19:24:30 +01:00
|
|
|
cpu_to_be32(env->cpu_index)};
|
|
|
|
|
|
|
|
if ((env->cpu_index % smt) != 0) {
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
snprintf(cpu_model, 32, "/cpus/%s@%x", spapr->cpu_model,
|
|
|
|
env->cpu_index);
|
|
|
|
|
|
|
|
offset = fdt_path_offset(fdt, cpu_model);
|
|
|
|
if (offset < 0) {
|
|
|
|
return offset;
|
|
|
|
}
|
|
|
|
|
2012-09-12 18:57:12 +02:00
|
|
|
if (nb_numa_nodes > 1) {
|
|
|
|
ret = fdt_setprop(fdt, offset, "ibm,associativity", associativity,
|
|
|
|
sizeof(associativity));
|
|
|
|
if (ret < 0) {
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
ret = fdt_setprop(fdt, offset, "ibm,pft-size",
|
|
|
|
pft_size_prop, sizeof(pft_size_prop));
|
2011-12-12 19:24:30 +01:00
|
|
|
if (ret < 0) {
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2012-06-18 21:56:30 +02:00
|
|
|
|
|
|
|
static size_t create_page_sizes_prop(CPUPPCState *env, uint32_t *prop,
|
|
|
|
size_t maxsize)
|
|
|
|
{
|
|
|
|
size_t maxcells = maxsize / sizeof(uint32_t);
|
|
|
|
int i, j, count;
|
|
|
|
uint32_t *p = prop;
|
|
|
|
|
|
|
|
for (i = 0; i < PPC_PAGE_SIZES_MAX_SZ; i++) {
|
|
|
|
struct ppc_one_seg_page_size *sps = &env->sps.sps[i];
|
|
|
|
|
|
|
|
if (!sps->page_shift) {
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
for (count = 0; count < PPC_PAGE_SIZES_MAX_SZ; count++) {
|
|
|
|
if (sps->enc[count].page_shift == 0) {
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if ((p - prop) >= (maxcells - 3 - count * 2)) {
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
*(p++) = cpu_to_be32(sps->page_shift);
|
|
|
|
*(p++) = cpu_to_be32(sps->slb_enc);
|
|
|
|
*(p++) = cpu_to_be32(count);
|
|
|
|
for (j = 0; j < count; j++) {
|
|
|
|
*(p++) = cpu_to_be32(sps->enc[j].page_shift);
|
|
|
|
*(p++) = cpu_to_be32(sps->enc[j].pte_enc);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return (p - prop) * sizeof(uint32_t);
|
|
|
|
}
|
|
|
|
|
2012-09-12 18:57:12 +02:00
|
|
|
#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)
|
|
|
|
|
|
|
|
|
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,
|
2012-10-23 12:30:10 +02:00
|
|
|
hwaddr initrd_base,
|
|
|
|
hwaddr initrd_size,
|
|
|
|
hwaddr kernel_size,
|
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
|
|
|
const char *boot_device,
|
2012-10-08 20:17:39 +02:00
|
|
|
const char *kernel_cmdline,
|
|
|
|
uint32_t epow_irq)
|
2011-04-01 06:15:20 +02:00
|
|
|
{
|
|
|
|
void *fdt;
|
2012-03-14 01:38:23 +01:00
|
|
|
CPUPPCState *env;
|
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:28 +02:00
|
|
|
char hypertas_prop[] = "hcall-pft\0hcall-term\0hcall-dabr\0hcall-interrupt"
|
2011-08-31 17:50:50 +02:00
|
|
|
"\0hcall-tce\0hcall-vio\0hcall-splpar\0hcall-bulk";
|
2012-06-18 22:21:37 +02:00
|
|
|
char qemu_hypertas_prop[] = "hcall-memop1";
|
2012-09-12 18:57:12 +02:00
|
|
|
uint32_t refpoints[] = {cpu_to_be32(0x4), cpu_to_be32(0x4)};
|
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
|
|
|
char *modelname;
|
2012-09-12 18:57:12 +02:00
|
|
|
int i, smt = kvmppc_smt_threads();
|
2011-12-12 19:24:30 +01:00
|
|
|
unsigned char vec5[] = {0x0, 0x0, 0x0, 0x0, 0x0, 0x80};
|
2011-04-01 06:15:20 +02:00
|
|
|
|
2011-08-21 05:09:37 +02:00
|
|
|
fdt = g_malloc0(FDT_MAX_SIZE);
|
2011-04-01 06:15:20 +02:00
|
|
|
_FDT((fdt_create(fdt, FDT_MAX_SIZE)));
|
|
|
|
|
2012-01-11 20:46:28 +01:00
|
|
|
if (kernel_size) {
|
|
|
|
_FDT((fdt_add_reservemap_entry(fdt, KERNEL_LOAD_ADDR, kernel_size)));
|
|
|
|
}
|
|
|
|
if (initrd_size) {
|
|
|
|
_FDT((fdt_add_reservemap_entry(fdt, initrd_base, initrd_size)));
|
|
|
|
}
|
2011-04-01 06:15:20 +02:00
|
|
|
_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")));
|
|
|
|
|
2011-12-12 19:24:30 +01:00
|
|
|
/* Set Form1_affinity */
|
|
|
|
_FDT((fdt_property(fdt, "ibm,architecture-vec-5", vec5, sizeof(vec5))));
|
|
|
|
|
2011-04-01 06:15:20 +02:00
|
|
|
_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))));
|
2012-01-11 20:46:28 +01:00
|
|
|
if (kernel_size) {
|
|
|
|
uint64_t kprop[2] = { cpu_to_be64(KERNEL_LOAD_ADDR),
|
|
|
|
cpu_to_be64(kernel_size) };
|
2011-04-01 06:15:20 +02:00
|
|
|
|
2012-01-11 20:46:28 +01:00
|
|
|
_FDT((fdt_property(fdt, "qemu,boot-kernel", &kprop, sizeof(kprop))));
|
|
|
|
}
|
|
|
|
_FDT((fdt_property_string(fdt, "qemu,boot-device", boot_device)));
|
2012-08-06 18:42:00 +02:00
|
|
|
_FDT((fdt_property_cell(fdt, "qemu,graphic-width", graphic_width)));
|
|
|
|
_FDT((fdt_property_cell(fdt, "qemu,graphic-height", graphic_height)));
|
|
|
|
_FDT((fdt_property_cell(fdt, "qemu,graphic-depth", graphic_depth)));
|
2011-10-30 18:16:46 +01:00
|
|
|
|
2011-04-01 06:15:20 +02:00
|
|
|
_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)));
|
|
|
|
|
2011-08-21 05:09:37 +02:00
|
|
|
modelname = g_strdup(cpu_model);
|
2011-04-01 06:15:20 +02:00
|
|
|
|
|
|
|
for (i = 0; i < strlen(modelname); i++) {
|
|
|
|
modelname[i] = toupper(modelname[i]);
|
|
|
|
}
|
|
|
|
|
2011-12-12 19:24:30 +01:00
|
|
|
/* This is needed during FDT finalization */
|
|
|
|
spapr->cpu_model = g_strdup(modelname);
|
|
|
|
|
2011-04-05 07:12:09 +02:00
|
|
|
for (env = first_cpu; env != NULL; env = env->next_cpu) {
|
|
|
|
int index = env->cpu_index;
|
2011-09-29 23:39:10 +02:00
|
|
|
uint32_t servers_prop[smp_threads];
|
|
|
|
uint32_t gservers_prop[smp_threads * 2];
|
2011-04-01 06:15:20 +02:00
|
|
|
char *nodename;
|
|
|
|
uint32_t segs[] = {cpu_to_be32(28), cpu_to_be32(40),
|
|
|
|
0xffffffff, 0xffffffff};
|
2011-08-09 18:07:13 +02:00
|
|
|
uint32_t tbfreq = kvm_enabled() ? kvmppc_get_tbfreq() : TIMEBASE_FREQ;
|
|
|
|
uint32_t cpufreq = kvm_enabled() ? kvmppc_get_clockfreq() : 1000000000;
|
2012-06-18 21:56:30 +02:00
|
|
|
uint32_t page_sizes_prop[64];
|
|
|
|
size_t page_sizes_prop_size;
|
2011-04-01 06:15:20 +02:00
|
|
|
|
2011-09-29 23:39:10 +02:00
|
|
|
if ((index % smt) != 0) {
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
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)));
|
2011-08-09 18:07:13 +02:00
|
|
|
_FDT((fdt_property_cell(fdt, "timebase-frequency", tbfreq)));
|
|
|
|
_FDT((fdt_property_cell(fdt, "clock-frequency", cpufreq)));
|
2011-04-01 06:15:20 +02:00
|
|
|
_FDT((fdt_property_cell(fdt, "ibm,slb-size", env->slb_nr)));
|
|
|
|
_FDT((fdt_property_string(fdt, "status", "okay")));
|
|
|
|
_FDT((fdt_property(fdt, "64-bit", NULL, 0)));
|
2011-09-29 23:39:10 +02:00
|
|
|
|
|
|
|
/* Build interrupt servers and gservers properties */
|
|
|
|
for (i = 0; i < smp_threads; i++) {
|
|
|
|
servers_prop[i] = cpu_to_be32(index + i);
|
|
|
|
/* Hack, direct the group queues back to cpu 0 */
|
|
|
|
gservers_prop[i*2] = cpu_to_be32(index + i);
|
|
|
|
gservers_prop[i*2 + 1] = 0;
|
|
|
|
}
|
|
|
|
_FDT((fdt_property(fdt, "ibm,ppc-interrupt-server#s",
|
|
|
|
servers_prop, sizeof(servers_prop))));
|
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",
|
2011-09-29 23:39:10 +02:00
|
|
|
gservers_prop, sizeof(gservers_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))));
|
|
|
|
}
|
|
|
|
|
pseries: Add device tree properties for VMX/VSX and DFP under kvm
Sufficiently recent PAPR specifications define properties "ibm,vmx"
and "ibm,dfp" on the CPU node which advertise whether the VMX vector
extensions (or the later VSX version) and/or the Decimal Floating
Point operations from IBM's recent POWER CPUs are available.
Currently we do not put these in the guest device tree and the guest
kernel will consequently assume they are not available. This is good,
because they are not supported under TCG. VMX is similar enough to
Altivec that it might be trivial to support, but VSX and DFP would
both require significant work to support in TCG.
However, when running under kvm on a host which supports these
instructions, there's no reason not to let the guest use them. This
patch, therefore, checks for the relevant support on the host CPU
and, if present, advertises them to the guest as well.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-10-10 20:31:01 +02:00
|
|
|
/* Advertise VMX/VSX (vector extensions) if available
|
|
|
|
* 0 / no property == no vector extensions
|
|
|
|
* 1 == VMX / Altivec available
|
|
|
|
* 2 == VSX available */
|
2011-10-17 20:15:41 +02:00
|
|
|
if (env->insns_flags & PPC_ALTIVEC) {
|
|
|
|
uint32_t vmx = (env->insns_flags2 & PPC2_VSX) ? 2 : 1;
|
|
|
|
|
pseries: Add device tree properties for VMX/VSX and DFP under kvm
Sufficiently recent PAPR specifications define properties "ibm,vmx"
and "ibm,dfp" on the CPU node which advertise whether the VMX vector
extensions (or the later VSX version) and/or the Decimal Floating
Point operations from IBM's recent POWER CPUs are available.
Currently we do not put these in the guest device tree and the guest
kernel will consequently assume they are not available. This is good,
because they are not supported under TCG. VMX is similar enough to
Altivec that it might be trivial to support, but VSX and DFP would
both require significant work to support in TCG.
However, when running under kvm on a host which supports these
instructions, there's no reason not to let the guest use them. This
patch, therefore, checks for the relevant support on the host CPU
and, if present, advertises them to the guest as well.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-10-10 20:31:01 +02:00
|
|
|
_FDT((fdt_property_cell(fdt, "ibm,vmx", vmx)));
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Advertise DFP (Decimal Floating Point) if available
|
|
|
|
* 0 / no property == no DFP
|
|
|
|
* 1 == DFP available */
|
2011-10-17 20:15:41 +02:00
|
|
|
if (env->insns_flags2 & PPC2_DFP) {
|
|
|
|
_FDT((fdt_property_cell(fdt, "ibm,dfp", 1)));
|
pseries: Add device tree properties for VMX/VSX and DFP under kvm
Sufficiently recent PAPR specifications define properties "ibm,vmx"
and "ibm,dfp" on the CPU node which advertise whether the VMX vector
extensions (or the later VSX version) and/or the Decimal Floating
Point operations from IBM's recent POWER CPUs are available.
Currently we do not put these in the guest device tree and the guest
kernel will consequently assume they are not available. This is good,
because they are not supported under TCG. VMX is similar enough to
Altivec that it might be trivial to support, but VSX and DFP would
both require significant work to support in TCG.
However, when running under kvm on a host which supports these
instructions, there's no reason not to let the guest use them. This
patch, therefore, checks for the relevant support on the host CPU
and, if present, advertises them to the guest as well.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Alexander Graf <agraf@suse.de>
2011-10-10 20:31:01 +02:00
|
|
|
}
|
|
|
|
|
2012-06-18 21:56:30 +02:00
|
|
|
page_sizes_prop_size = create_page_sizes_prop(env, page_sizes_prop,
|
|
|
|
sizeof(page_sizes_prop));
|
|
|
|
if (page_sizes_prop_size) {
|
|
|
|
_FDT((fdt_property(fdt, "ibm,segment-page-sizes",
|
|
|
|
page_sizes_prop, page_sizes_prop_size)));
|
|
|
|
}
|
|
|
|
|
2011-04-01 06:15:20 +02:00
|
|
|
_FDT((fdt_end_node(fdt)));
|
|
|
|
}
|
|
|
|
|
2011-08-21 05:09:37 +02:00
|
|
|
g_free(modelname);
|
2011-04-01 06:15:20 +02:00
|
|
|
|
|
|
|
_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))));
|
2012-06-18 22:21:37 +02:00
|
|
|
_FDT((fdt_property(fdt, "qemu,hypertas-functions", qemu_hypertas_prop,
|
|
|
|
sizeof(qemu_hypertas_prop))));
|
2011-04-01 06:15:22 +02:00
|
|
|
|
2011-12-12 19:24:30 +01:00
|
|
|
_FDT((fdt_property(fdt, "ibm,associativity-reference-points",
|
|
|
|
refpoints, sizeof(refpoints))));
|
|
|
|
|
2012-10-08 20:17:39 +02:00
|
|
|
_FDT((fdt_property_cell(fdt, "rtas-error-log-max", RTAS_ERROR_LOG_MAX)));
|
|
|
|
|
2011-04-01 06:15:22 +02:00
|
|
|
_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 */
|
2011-08-03 23:02:18 +02:00
|
|
|
_FDT((fdt_begin_node(fdt, "interrupt-controller")));
|
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_string(fdt, "device_type",
|
|
|
|
"PowerPC-External-Interrupt-Presentation")));
|
|
|
|
_FDT((fdt_property_string(fdt, "compatible", "IBM,ppc-xicp")));
|
|
|
|
_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))));
|
2011-08-03 23:02:17 +02:00
|
|
|
_FDT((fdt_property_cell(fdt, "#interrupt-cells", 2)));
|
|
|
|
_FDT((fdt_property_cell(fdt, "linux,phandle", PHANDLE_XICP)));
|
|
|
|
_FDT((fdt_property_cell(fdt, "phandle", PHANDLE_XICP)));
|
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_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)));
|
|
|
|
|
2012-10-08 20:17:39 +02:00
|
|
|
/* event-sources */
|
|
|
|
spapr_events_fdt_skel(fdt, epow_irq);
|
|
|
|
|
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;
|
|
|
|
}
|
|
|
|
|
2012-09-12 18:57:12 +02:00
|
|
|
static int spapr_populate_memory(sPAPREnvironment *spapr, void *fdt)
|
|
|
|
{
|
|
|
|
uint32_t associativity[] = {cpu_to_be32(0x4), cpu_to_be32(0x0),
|
|
|
|
cpu_to_be32(0x0), cpu_to_be32(0x0),
|
|
|
|
cpu_to_be32(0x0)};
|
|
|
|
char mem_name[32];
|
2012-10-23 12:30:10 +02:00
|
|
|
hwaddr node0_size, mem_start;
|
2012-09-12 18:57:12 +02:00
|
|
|
uint64_t mem_reg_property[2];
|
|
|
|
int i, off;
|
|
|
|
|
|
|
|
/* memory node(s) */
|
|
|
|
node0_size = (nb_numa_nodes > 1) ? node_mem[0] : ram_size;
|
|
|
|
if (spapr->rma_size > node0_size) {
|
|
|
|
spapr->rma_size = node0_size;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* RMA */
|
|
|
|
mem_reg_property[0] = 0;
|
|
|
|
mem_reg_property[1] = cpu_to_be64(spapr->rma_size);
|
|
|
|
off = fdt_add_subnode(fdt, 0, "memory@0");
|
|
|
|
_FDT(off);
|
|
|
|
_FDT((fdt_setprop_string(fdt, off, "device_type", "memory")));
|
|
|
|
_FDT((fdt_setprop(fdt, off, "reg", mem_reg_property,
|
|
|
|
sizeof(mem_reg_property))));
|
|
|
|
_FDT((fdt_setprop(fdt, off, "ibm,associativity", associativity,
|
|
|
|
sizeof(associativity))));
|
|
|
|
|
|
|
|
/* RAM: Node 0 */
|
|
|
|
if (node0_size > spapr->rma_size) {
|
|
|
|
mem_reg_property[0] = cpu_to_be64(spapr->rma_size);
|
|
|
|
mem_reg_property[1] = cpu_to_be64(node0_size - spapr->rma_size);
|
|
|
|
|
|
|
|
sprintf(mem_name, "memory@" TARGET_FMT_lx, spapr->rma_size);
|
|
|
|
off = fdt_add_subnode(fdt, 0, mem_name);
|
|
|
|
_FDT(off);
|
|
|
|
_FDT((fdt_setprop_string(fdt, off, "device_type", "memory")));
|
|
|
|
_FDT((fdt_setprop(fdt, off, "reg", mem_reg_property,
|
|
|
|
sizeof(mem_reg_property))));
|
|
|
|
_FDT((fdt_setprop(fdt, off, "ibm,associativity", associativity,
|
|
|
|
sizeof(associativity))));
|
|
|
|
}
|
|
|
|
|
|
|
|
/* RAM: Node 1 and beyond */
|
|
|
|
mem_start = node0_size;
|
|
|
|
for (i = 1; i < nb_numa_nodes; i++) {
|
|
|
|
mem_reg_property[0] = cpu_to_be64(mem_start);
|
|
|
|
mem_reg_property[1] = cpu_to_be64(node_mem[i]);
|
|
|
|
associativity[3] = associativity[4] = cpu_to_be32(i);
|
|
|
|
sprintf(mem_name, "memory@" TARGET_FMT_lx, mem_start);
|
|
|
|
off = fdt_add_subnode(fdt, 0, mem_name);
|
|
|
|
_FDT(off);
|
|
|
|
_FDT((fdt_setprop_string(fdt, off, "device_type", "memory")));
|
|
|
|
_FDT((fdt_setprop(fdt, off, "reg", mem_reg_property,
|
|
|
|
sizeof(mem_reg_property))));
|
|
|
|
_FDT((fdt_setprop(fdt, off, "ibm,associativity", associativity,
|
|
|
|
sizeof(associativity))));
|
|
|
|
mem_start += node_mem[i];
|
|
|
|
}
|
|
|
|
|
|
|
|
return 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
|
|
|
static void spapr_finalize_fdt(sPAPREnvironment *spapr,
|
2012-10-23 12:30:10 +02:00
|
|
|
hwaddr fdt_addr,
|
|
|
|
hwaddr rtas_addr,
|
|
|
|
hwaddr rtas_size)
|
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
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
void *fdt;
|
2011-10-30 18:16:46 +01:00
|
|
|
sPAPRPHBState *phb;
|
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
|
|
|
|
2011-08-21 05:09:37 +02:00
|
|
|
fdt = g_malloc(FDT_MAX_SIZE);
|
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
|
|
|
|
|
|
|
/* 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
|
|
|
|
2012-09-12 18:57:12 +02:00
|
|
|
ret = spapr_populate_memory(spapr, fdt);
|
|
|
|
if (ret < 0) {
|
|
|
|
fprintf(stderr, "couldn't setup memory nodes in fdt\n");
|
|
|
|
exit(1);
|
|
|
|
}
|
|
|
|
|
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-10-30 18:16:46 +01:00
|
|
|
QLIST_FOREACH(phb, &spapr->phbs, list) {
|
2012-06-13 20:40:06 +02:00
|
|
|
ret = spapr_populate_pci_dt(phb, PHANDLE_XICP, fdt);
|
2011-10-30 18:16:46 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
if (ret < 0) {
|
|
|
|
fprintf(stderr, "couldn't setup PCI 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-12-12 19:24:30 +01:00
|
|
|
/* Advertise NUMA via ibm,associativity */
|
2012-09-12 18:57:12 +02:00
|
|
|
ret = spapr_fixup_cpu_dt(fdt, spapr);
|
|
|
|
if (ret < 0) {
|
|
|
|
fprintf(stderr, "Couldn't finalize CPU device tree properties\n");
|
2011-12-12 19:24:30 +01:00
|
|
|
}
|
|
|
|
|
2012-08-14 13:22:13 +02:00
|
|
|
if (!spapr->has_graphics) {
|
2012-08-06 18:42:00 +02:00
|
|
|
spapr_populate_chosen_stdout(fdt, spapr->vio_bus);
|
|
|
|
}
|
2011-12-13 05:24:34 +01:00
|
|
|
|
2011-04-01 06:15:21 +02:00
|
|
|
_FDT((fdt_pack(fdt)));
|
|
|
|
|
2012-01-11 20:46:28 +01:00
|
|
|
if (fdt_totalsize(fdt) > FDT_MAX_SIZE) {
|
|
|
|
hw_error("FDT too big ! 0x%x bytes (max is 0x%x)\n",
|
|
|
|
fdt_totalsize(fdt), FDT_MAX_SIZE);
|
|
|
|
exit(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
|
|
|
cpu_physical_memory_write(fdt_addr, fdt, fdt_totalsize(fdt));
|
2011-04-01 06:15:20 +02:00
|
|
|
|
2011-08-21 05:09:37 +02:00
|
|
|
g_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;
|
|
|
|
}
|
|
|
|
|
2012-05-03 06:03:45 +02:00
|
|
|
static void emulate_spapr_hypercall(PowerPCCPU *cpu)
|
2011-04-01 06:15:20 +02:00
|
|
|
{
|
2012-05-03 06:03:45 +02:00
|
|
|
CPUPPCState *env = &cpu->env;
|
|
|
|
|
2012-09-25 19:12:20 +02:00
|
|
|
if (msr_pr) {
|
|
|
|
hcall_dprintf("Hypercall made with MSR[PR]=1\n");
|
|
|
|
env->gpr[3] = H_PRIVILEGE;
|
|
|
|
} else {
|
2012-05-03 06:13:14 +02:00
|
|
|
env->gpr[3] = spapr_hypercall(cpu, env->gpr[3], &env->gpr[4]);
|
2012-09-25 19:12:20 +02:00
|
|
|
}
|
2011-04-01 06:15:20 +02:00
|
|
|
}
|
|
|
|
|
2012-09-12 18:57:12 +02:00
|
|
|
static void spapr_reset_htab(sPAPREnvironment *spapr)
|
|
|
|
{
|
|
|
|
long shift;
|
|
|
|
|
|
|
|
/* allocate hash page table. For now we always make this 16mb,
|
|
|
|
* later we should probably make it scale to the size of guest
|
|
|
|
* RAM */
|
|
|
|
|
|
|
|
shift = kvmppc_reset_htab(spapr->htab_shift);
|
|
|
|
|
|
|
|
if (shift > 0) {
|
|
|
|
/* Kernel handles htab, we don't need to allocate one */
|
|
|
|
spapr->htab_shift = shift;
|
|
|
|
} else {
|
|
|
|
if (!spapr->htab) {
|
|
|
|
/* Allocate an htab if we don't yet have one */
|
|
|
|
spapr->htab = qemu_memalign(HTAB_SIZE(spapr), HTAB_SIZE(spapr));
|
|
|
|
}
|
|
|
|
|
|
|
|
/* And clear it */
|
|
|
|
memset(spapr->htab, 0, HTAB_SIZE(spapr));
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Update the RMA size if necessary */
|
|
|
|
if (spapr->vrma_adjust) {
|
|
|
|
spapr->rma_size = kvmppc_rma_size(ram_size, spapr->htab_shift);
|
|
|
|
}
|
2011-04-01 06:15:20 +02:00
|
|
|
}
|
|
|
|
|
2012-09-12 18:57:11 +02:00
|
|
|
static void ppc_spapr_reset(void)
|
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
|
|
|
{
|
2012-09-12 18:57:12 +02:00
|
|
|
/* Reset the hash table & recalc the RMA */
|
|
|
|
spapr_reset_htab(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
|
|
|
|
2012-09-12 18:57:11 +02:00
|
|
|
qemu_devices_reset();
|
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
|
|
|
|
|
|
|
/* 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;
|
|
|
|
|
|
|
|
}
|
|
|
|
|
2012-02-08 03:03:33 +01:00
|
|
|
static void spapr_cpu_reset(void *opaque)
|
|
|
|
{
|
2012-05-04 17:49:38 +02:00
|
|
|
PowerPCCPU *cpu = opaque;
|
2012-09-12 18:57:10 +02:00
|
|
|
CPUPPCState *env = &cpu->env;
|
2012-02-08 03:03:33 +01:00
|
|
|
|
2012-05-04 17:49:38 +02:00
|
|
|
cpu_reset(CPU(cpu));
|
2012-09-12 18:57:10 +02:00
|
|
|
|
|
|
|
/* All CPUs start halted. CPU0 is unhalted from the machine level
|
|
|
|
* reset code and the rest are explicitly started up by the guest
|
|
|
|
* using an RTAS call */
|
|
|
|
env->halted = 1;
|
|
|
|
|
|
|
|
env->spr[SPR_HIOR] = 0;
|
2012-09-12 18:57:12 +02:00
|
|
|
|
|
|
|
env->external_htab = spapr->htab;
|
|
|
|
env->htab_base = -1;
|
|
|
|
env->htab_mask = HTAB_SIZE(spapr) - 1;
|
|
|
|
env->spr[SPR_SDR1] = (unsigned long)spapr->htab |
|
|
|
|
(spapr->htab_shift - 18);
|
2012-02-08 03:03:33 +01:00
|
|
|
}
|
|
|
|
|
2012-11-12 17:46:57 +01:00
|
|
|
static void spapr_create_nvram(sPAPREnvironment *spapr)
|
|
|
|
{
|
|
|
|
QemuOpts *machine_opts;
|
|
|
|
DeviceState *dev;
|
|
|
|
|
|
|
|
dev = qdev_create(&spapr->vio_bus->bus, "spapr-nvram");
|
|
|
|
|
|
|
|
machine_opts = qemu_opts_find(qemu_find_opts("machine"), 0);
|
|
|
|
if (machine_opts) {
|
|
|
|
const char *drivename;
|
|
|
|
|
|
|
|
drivename = qemu_opt_get(machine_opts, "nvram");
|
|
|
|
if (drivename) {
|
|
|
|
BlockDriverState *bs;
|
|
|
|
|
|
|
|
bs = bdrv_find(drivename);
|
|
|
|
if (!bs) {
|
|
|
|
fprintf(stderr, "No such block device \"%s\" for nvram\n",
|
|
|
|
drivename);
|
|
|
|
exit(1);
|
|
|
|
}
|
|
|
|
qdev_prop_set_drive_nofail(dev, "drive", bs);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
qdev_init_nofail(dev);
|
|
|
|
|
|
|
|
spapr->nvram = (struct sPAPRNVRAM *)dev;
|
|
|
|
}
|
|
|
|
|
2012-08-14 13:11:49 +02:00
|
|
|
/* Returns whether we want to use VGA or not */
|
2012-08-06 18:42:00 +02:00
|
|
|
static int spapr_vga_init(PCIBus *pci_bus)
|
|
|
|
{
|
2012-08-14 13:11:49 +02:00
|
|
|
switch (vga_interface_type) {
|
|
|
|
case VGA_NONE:
|
2012-09-08 12:40:45 +02:00
|
|
|
case VGA_STD:
|
|
|
|
return pci_vga_init(pci_bus) != NULL;
|
2012-08-14 13:11:49 +02:00
|
|
|
default:
|
2012-08-06 18:42:00 +02:00
|
|
|
fprintf(stderr, "This vga model is not supported,"
|
|
|
|
"currently it only supports -vga std\n");
|
2012-08-14 13:11:49 +02:00
|
|
|
exit(0);
|
|
|
|
break;
|
2012-08-06 18:42:00 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2011-04-01 06:15:20 +02:00
|
|
|
/* pSeries LPAR / sPAPR hardware init */
|
2012-10-15 22:22:02 +02:00
|
|
|
static void ppc_spapr_init(QEMUMachineInitArgs *args)
|
2011-04-01 06:15:20 +02:00
|
|
|
{
|
2012-10-15 22:22:02 +02:00
|
|
|
ram_addr_t ram_size = args->ram_size;
|
|
|
|
const char *cpu_model = args->cpu_model;
|
|
|
|
const char *kernel_filename = args->kernel_filename;
|
|
|
|
const char *kernel_cmdline = args->kernel_cmdline;
|
|
|
|
const char *initrd_filename = args->initrd_filename;
|
|
|
|
const char *boot_device = args->boot_device;
|
2012-05-03 05:45:10 +02:00
|
|
|
PowerPCCPU *cpu;
|
2012-03-14 01:38:23 +01:00
|
|
|
CPUPPCState *env;
|
2012-08-20 19:08:05 +02:00
|
|
|
PCIHostState *phb;
|
2011-04-01 06:15:20 +02:00
|
|
|
int i;
|
2011-10-03 12:56:38 +02:00
|
|
|
MemoryRegion *sysmem = get_system_memory();
|
|
|
|
MemoryRegion *ram = g_new(MemoryRegion, 1);
|
2012-10-23 12:30:10 +02:00
|
|
|
hwaddr rma_alloc_size;
|
2012-01-11 20:46:28 +01:00
|
|
|
uint32_t initrd_base = 0;
|
|
|
|
long kernel_size = 0, initrd_size = 0;
|
|
|
|
long load_limit, rtas_limit, fw_size;
|
2011-04-01 06:15:23 +02:00
|
|
|
char *filename;
|
2011-04-01 06:15:20 +02:00
|
|
|
|
2012-08-07 18:10:37 +02:00
|
|
|
msi_supported = true;
|
|
|
|
|
2011-11-01 17:49:05 +01:00
|
|
|
spapr = g_malloc0(sizeof(*spapr));
|
|
|
|
QLIST_INIT(&spapr->phbs);
|
|
|
|
|
2011-04-01 06:15:20 +02:00
|
|
|
cpu_ppc_hypercall = emulate_spapr_hypercall;
|
|
|
|
|
2011-09-29 23:39:11 +02:00
|
|
|
/* Allocate RMA if necessary */
|
|
|
|
rma_alloc_size = kvmppc_alloc_rma("ppc_spapr.rma", sysmem);
|
|
|
|
|
|
|
|
if (rma_alloc_size == -1) {
|
|
|
|
hw_error("qemu: Unable to create RMA\n");
|
|
|
|
exit(1);
|
|
|
|
}
|
2012-09-12 18:57:12 +02:00
|
|
|
|
2011-09-29 23:39:11 +02:00
|
|
|
if (rma_alloc_size && (rma_alloc_size < ram_size)) {
|
2012-09-12 18:57:12 +02:00
|
|
|
spapr->rma_size = rma_alloc_size;
|
2011-09-29 23:39:11 +02:00
|
|
|
} else {
|
2012-09-12 18:57:12 +02:00
|
|
|
spapr->rma_size = ram_size;
|
|
|
|
|
|
|
|
/* With KVM, we don't actually know whether KVM supports an
|
|
|
|
* unbounded RMA (PR KVM) or is limited by the hash table size
|
|
|
|
* (HV KVM using VRMA), so we always assume the latter
|
|
|
|
*
|
|
|
|
* In that case, we also limit the initial allocations for RTAS
|
|
|
|
* etc... to 256M since we have no way to know what the VRMA size
|
|
|
|
* is going to be as it depends on the size of the hash table
|
|
|
|
* isn't determined yet.
|
|
|
|
*/
|
|
|
|
if (kvm_enabled()) {
|
|
|
|
spapr->vrma_adjust = 1;
|
|
|
|
spapr->rma_size = MIN(spapr->rma_size, 0x10000000);
|
|
|
|
}
|
2011-09-29 23:39:11 +02:00
|
|
|
}
|
|
|
|
|
2012-01-11 20:46:28 +01:00
|
|
|
/* We place the device tree and RTAS just below either the top of the RMA,
|
2011-09-29 23:39:11 +02:00
|
|
|
* or just below 2GB, whichever is lowere, so that it can be
|
|
|
|
* processed with 32-bit real mode code if necessary */
|
2012-09-12 18:57:12 +02:00
|
|
|
rtas_limit = MIN(spapr->rma_size, 0x80000000);
|
2012-01-11 20:46:28 +01:00
|
|
|
spapr->rtas_addr = rtas_limit - RTAS_MAX_SIZE;
|
|
|
|
spapr->fdt_addr = spapr->rtas_addr - FDT_MAX_SIZE;
|
|
|
|
load_limit = spapr->fdt_addr - FW_OVERHEAD;
|
2011-04-01 06:15:20 +02:00
|
|
|
|
2012-09-20 19:42:27 +02:00
|
|
|
/* We aim for a hash table of size 1/128 the size of RAM. The
|
|
|
|
* normal rule of thumb is 1/64 the size of RAM, but that's much
|
|
|
|
* more than needed for the Linux guests we support. */
|
|
|
|
spapr->htab_shift = 18; /* Minimum architected size */
|
|
|
|
while (spapr->htab_shift <= 46) {
|
|
|
|
if ((1ULL << (spapr->htab_shift + 7)) >= ram_size) {
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
spapr->htab_shift++;
|
|
|
|
}
|
2012-09-12 18:57:12 +02:00
|
|
|
|
2011-04-01 06:15:20 +02:00
|
|
|
/* init CPUs */
|
|
|
|
if (cpu_model == NULL) {
|
2011-10-13 00:40:34 +02:00
|
|
|
cpu_model = kvm_enabled() ? "host" : "POWER7";
|
2011-04-01 06:15:20 +02:00
|
|
|
}
|
|
|
|
for (i = 0; i < smp_cpus; i++) {
|
2012-05-03 05:45:10 +02:00
|
|
|
cpu = cpu_ppc_init(cpu_model);
|
|
|
|
if (cpu == NULL) {
|
2011-04-01 06:15:20 +02:00
|
|
|
fprintf(stderr, "Unable to find PowerPC CPU definition\n");
|
|
|
|
exit(1);
|
|
|
|
}
|
2012-05-03 05:45:10 +02:00
|
|
|
env = &cpu->env;
|
|
|
|
|
2011-04-01 06:15:20 +02:00
|
|
|
/* Set time-base frequency to 512 MHz */
|
|
|
|
cpu_ppc_tb_init(env, TIMEBASE_FREQ);
|
|
|
|
|
2012-09-12 18:57:10 +02:00
|
|
|
/* PAPR always has exception vectors in RAM not ROM */
|
2011-04-01 06:15:20 +02:00
|
|
|
env->hreset_excp_prefix = 0;
|
2012-09-12 18:57:10 +02:00
|
|
|
|
|
|
|
/* Tell KVM that we're in PAPR mode */
|
|
|
|
if (kvm_enabled()) {
|
2012-10-31 06:06:49 +01:00
|
|
|
kvmppc_set_papr(cpu);
|
2012-09-12 18:57:10 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
qemu_register_reset(spapr_cpu_reset, cpu);
|
2011-04-01 06:15:20 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
/* allocate RAM */
|
2011-08-03 23:02:19 +02:00
|
|
|
spapr->ram_limit = ram_size;
|
2011-09-29 23:39:11 +02:00
|
|
|
if (spapr->ram_limit > rma_alloc_size) {
|
|
|
|
ram_addr_t nonrma_base = rma_alloc_size;
|
|
|
|
ram_addr_t nonrma_size = spapr->ram_limit - rma_alloc_size;
|
|
|
|
|
2011-12-20 14:59:12 +01:00
|
|
|
memory_region_init_ram(ram, "ppc_spapr.ram", nonrma_size);
|
|
|
|
vmstate_register_ram_global(ram);
|
2011-09-29 23:39:11 +02:00
|
|
|
memory_region_add_subregion(sysmem, nonrma_base, ram);
|
|
|
|
}
|
2011-04-01 06:15:20 +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,
|
2012-01-11 20:46:28 +01:00
|
|
|
rtas_limit - spapr->rtas_addr);
|
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
|
|
|
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);
|
|
|
|
}
|
2012-01-11 20:46:28 +01:00
|
|
|
if (spapr->rtas_size > RTAS_MAX_SIZE) {
|
|
|
|
hw_error("RTAS too big ! 0x%lx bytes (max is 0x%x)\n",
|
|
|
|
spapr->rtas_size, RTAS_MAX_SIZE);
|
|
|
|
exit(1);
|
|
|
|
}
|
2011-08-21 05:09:37 +02:00
|
|
|
g_free(filename);
|
2011-04-01 06:15:23 +02:00
|
|
|
|
2012-01-11 20:46:28 +01:00
|
|
|
|
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);
|
2012-11-12 17:46:50 +01:00
|
|
|
spapr->next_irq = XICS_IRQ_BASE;
|
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
|
|
|
|
2012-10-08 20:17:39 +02:00
|
|
|
/* Set up EPOW events infrastructure */
|
|
|
|
spapr_events_init(spapr);
|
|
|
|
|
2012-06-27 06:50:44 +02:00
|
|
|
/* Set up IOMMU */
|
|
|
|
spapr_iommu_init();
|
|
|
|
|
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-05-26 11:52:44 +02:00
|
|
|
for (i = 0; i < MAX_SERIAL_PORTS; i++) {
|
2011-04-01 06:15:21 +02:00
|
|
|
if (serial_hds[i]) {
|
2012-04-25 19:55:41 +02:00
|
|
|
spapr_vty_create(spapr->vio_bus, serial_hds[i]);
|
2011-04-01 06:15:21 +02:00
|
|
|
}
|
|
|
|
}
|
2011-04-01 06:15:20 +02:00
|
|
|
|
2012-11-12 17:46:57 +01:00
|
|
|
/* We always have at least the nvram device on VIO */
|
|
|
|
spapr_create_nvram(spapr);
|
|
|
|
|
2011-10-30 18:16:46 +01:00
|
|
|
/* Set up PCI */
|
2012-08-07 18:10:33 +02:00
|
|
|
spapr_pci_rtas_init();
|
|
|
|
|
2011-10-30 18:16:46 +01:00
|
|
|
spapr_create_phb(spapr, "pci", SPAPR_PCI_BUID,
|
|
|
|
SPAPR_PCI_MEM_WIN_ADDR,
|
|
|
|
SPAPR_PCI_MEM_WIN_SIZE,
|
2012-08-07 18:10:37 +02:00
|
|
|
SPAPR_PCI_IO_WIN_ADDR,
|
|
|
|
SPAPR_PCI_MSI_WIN_ADDR);
|
2012-08-20 19:08:08 +02:00
|
|
|
phb = PCI_HOST_BRIDGE(QLIST_FIRST(&spapr->phbs));
|
2011-10-30 18:16:46 +01:00
|
|
|
|
2011-05-26 11:52:44 +02:00
|
|
|
for (i = 0; i < nb_nics; i++) {
|
2011-04-01 06:15:29 +02:00
|
|
|
NICInfo *nd = &nd_table[i];
|
|
|
|
|
|
|
|
if (!nd->model) {
|
2011-08-21 05:09:37 +02:00
|
|
|
nd->model = g_strdup("ibmveth");
|
2011-04-01 06:15:29 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
if (strcmp(nd->model, "ibmveth") == 0) {
|
2012-04-25 19:55:41 +02:00
|
|
|
spapr_vlan_create(spapr->vio_bus, nd);
|
2011-04-01 06:15:29 +02:00
|
|
|
} else {
|
2011-10-30 18:16:46 +01:00
|
|
|
pci_nic_init_nofail(&nd_table[i], nd->model, NULL);
|
2011-04-01 06:15:29 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2011-04-01 06:15:31 +02:00
|
|
|
for (i = 0; i <= drive_get_max_bus(IF_SCSI); i++) {
|
2012-04-25 19:55:41 +02:00
|
|
|
spapr_vscsi_create(spapr->vio_bus);
|
2011-04-01 06:15:31 +02:00
|
|
|
}
|
|
|
|
|
2012-08-06 18:42:00 +02:00
|
|
|
/* Graphics */
|
2012-08-20 19:08:05 +02:00
|
|
|
if (spapr_vga_init(phb->bus)) {
|
2012-08-14 13:22:13 +02:00
|
|
|
spapr->has_graphics = true;
|
2012-08-06 18:42:00 +02:00
|
|
|
}
|
|
|
|
|
2012-09-02 21:25:28 +02:00
|
|
|
if (usb_enabled(spapr->has_graphics)) {
|
2012-08-20 19:08:05 +02:00
|
|
|
pci_create_simple(phb->bus, -1, "pci-ohci");
|
2012-08-16 04:03:56 +02:00
|
|
|
if (spapr->has_graphics) {
|
|
|
|
usbdevice_create("keyboard");
|
|
|
|
usbdevice_create("mouse");
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2012-09-12 18:57:12 +02:00
|
|
|
if (spapr->rma_size < (MIN_RMA_SLOF << 20)) {
|
2012-01-11 20:46:28 +01:00
|
|
|
fprintf(stderr, "qemu: pSeries SLOF firmware requires >= "
|
|
|
|
"%ldM guest RMA (Real Mode Area memory)\n", MIN_RMA_SLOF);
|
|
|
|
exit(1);
|
|
|
|
}
|
|
|
|
|
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,
|
2012-01-11 20:46:28 +01:00
|
|
|
load_limit - 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) {
|
2012-01-11 20:46:28 +01:00
|
|
|
/* Try to locate the initrd in the gap between the kernel
|
|
|
|
* and the firmware. Add a bit of space just in case
|
|
|
|
*/
|
|
|
|
initrd_base = (KERNEL_LOAD_ADDR + kernel_size + 0x1ffff) & ~0xffff;
|
2011-04-01 06:15:20 +02:00
|
|
|
initrd_size = load_image_targphys(initrd_filename, initrd_base,
|
2012-01-11 20:46:28 +01:00
|
|
|
load_limit - initrd_base);
|
2011-04-01 06:15:20 +02:00
|
|
|
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;
|
|
|
|
}
|
2012-01-11 20:46:28 +01: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
|
|
|
|
2012-01-11 20:46:28 +01:00
|
|
|
filename = qemu_find_file(QEMU_FILE_TYPE_BIOS, FW_FILE_NAME);
|
|
|
|
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);
|
|
|
|
}
|
|
|
|
g_free(filename);
|
|
|
|
|
|
|
|
spapr->entry_point = 0x100;
|
|
|
|
|
2011-04-01 06:15:20 +02:00
|
|
|
/* Prepare the device tree */
|
2012-09-12 18:57:12 +02:00
|
|
|
spapr->fdt_skel = spapr_create_fdt_skel(cpu_model,
|
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
|
|
|
initrd_base, initrd_size,
|
2012-01-11 20:46:28 +01:00
|
|
|
kernel_size,
|
2012-10-08 20:17:39 +02:00
|
|
|
boot_device, kernel_cmdline,
|
|
|
|
spapr->epow_irq);
|
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
|
|
|
assert(spapr->fdt_skel != NULL);
|
2011-04-01 06:15:20 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
static QEMUMachine spapr_machine = {
|
|
|
|
.name = "pseries",
|
|
|
|
.desc = "pSeries Logical Partition (PAPR compliant)",
|
|
|
|
.init = ppc_spapr_init,
|
2012-09-12 18:57:11 +02:00
|
|
|
.reset = ppc_spapr_reset,
|
2012-11-20 15:30:34 +01:00
|
|
|
.block_default_type = IF_SCSI,
|
2011-04-01 06:15:20 +02:00
|
|
|
.max_cpus = MAX_CPUS,
|
|
|
|
.no_parallel = 1,
|
|
|
|
};
|
|
|
|
|
|
|
|
static void spapr_machine_init(void)
|
|
|
|
{
|
|
|
|
qemu_register_machine(&spapr_machine);
|
|
|
|
}
|
|
|
|
|
|
|
|
machine_init(spapr_machine_init);
|