ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
/*
|
|
|
|
* QEMU PowerPC PowerNV (POWER9) PHB4 model
|
|
|
|
*
|
|
|
|
* Copyright (c) 2018-2020, IBM Corporation.
|
|
|
|
*
|
|
|
|
* This code is licensed under the GPL version 2 or later. See the
|
|
|
|
* COPYING file in the top-level directory.
|
|
|
|
*/
|
|
|
|
#include "qemu/osdep.h"
|
|
|
|
#include "qemu/log.h"
|
|
|
|
#include "qapi/visitor.h"
|
|
|
|
#include "qapi/error.h"
|
|
|
|
#include "monitor/monitor.h"
|
|
|
|
#include "target/ppc/cpu.h"
|
|
|
|
#include "hw/pci-host/pnv_phb4_regs.h"
|
|
|
|
#include "hw/pci-host/pnv_phb4.h"
|
|
|
|
#include "hw/pci/pcie_host.h"
|
|
|
|
#include "hw/pci/pcie_port.h"
|
|
|
|
#include "hw/ppc/pnv.h"
|
|
|
|
#include "hw/ppc/pnv_xscom.h"
|
|
|
|
#include "hw/irq.h"
|
|
|
|
#include "hw/qdev-properties.h"
|
2020-09-03 23:43:22 +03:00
|
|
|
#include "qom/object.h"
|
2021-01-26 20:10:53 +03:00
|
|
|
#include "trace.h"
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
|
|
|
|
#define phb_error(phb, fmt, ...) \
|
|
|
|
qemu_log_mask(LOG_GUEST_ERROR, "phb4[%d:%d]: " fmt "\n", \
|
|
|
|
(phb)->chip_id, (phb)->phb_id, ## __VA_ARGS__)
|
|
|
|
|
2022-01-12 13:28:27 +03:00
|
|
|
#define phb_pec_error(pec, fmt, ...) \
|
|
|
|
qemu_log_mask(LOG_GUEST_ERROR, "phb4_pec[%d:%d]: " fmt "\n", \
|
|
|
|
(pec)->chip_id, (pec)->index, ## __VA_ARGS__)
|
|
|
|
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
static PCIDevice *pnv_phb4_find_cfg_dev(PnvPHB4 *phb)
|
|
|
|
{
|
2022-06-24 11:49:14 +03:00
|
|
|
PCIHostState *pci = PCI_HOST_BRIDGE(phb->phb_base);
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
uint64_t addr = phb->regs[PHB_CONFIG_ADDRESS >> 3];
|
|
|
|
uint8_t bus, devfn;
|
|
|
|
|
|
|
|
if (!(addr >> 63)) {
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
bus = (addr >> 52) & 0xff;
|
|
|
|
devfn = (addr >> 44) & 0xff;
|
|
|
|
|
|
|
|
/* We don't access the root complex this way */
|
|
|
|
if (bus == 0 && devfn == 0) {
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
return pci_find_device(pci->bus, bus, devfn);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* The CONFIG_DATA register expects little endian accesses, but as the
|
|
|
|
* region is big endian, we have to swap the value.
|
|
|
|
*/
|
|
|
|
static void pnv_phb4_config_write(PnvPHB4 *phb, unsigned off,
|
|
|
|
unsigned size, uint64_t val)
|
|
|
|
{
|
|
|
|
uint32_t cfg_addr, limit;
|
|
|
|
PCIDevice *pdev;
|
|
|
|
|
|
|
|
pdev = pnv_phb4_find_cfg_dev(phb);
|
|
|
|
if (!pdev) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
cfg_addr = (phb->regs[PHB_CONFIG_ADDRESS >> 3] >> 32) & 0xffc;
|
|
|
|
cfg_addr |= off;
|
|
|
|
limit = pci_config_size(pdev);
|
|
|
|
if (limit <= cfg_addr) {
|
|
|
|
/*
|
|
|
|
* conventional pci device can be behind pcie-to-pci bridge.
|
|
|
|
* 256 <= addr < 4K has no effects.
|
|
|
|
*/
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
switch (size) {
|
|
|
|
case 1:
|
|
|
|
break;
|
|
|
|
case 2:
|
|
|
|
val = bswap16(val);
|
|
|
|
break;
|
|
|
|
case 4:
|
|
|
|
val = bswap32(val);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
g_assert_not_reached();
|
|
|
|
}
|
|
|
|
pci_host_config_write_common(pdev, cfg_addr, limit, val, size);
|
|
|
|
}
|
|
|
|
|
|
|
|
static uint64_t pnv_phb4_config_read(PnvPHB4 *phb, unsigned off,
|
|
|
|
unsigned size)
|
|
|
|
{
|
|
|
|
uint32_t cfg_addr, limit;
|
|
|
|
PCIDevice *pdev;
|
|
|
|
uint64_t val;
|
|
|
|
|
|
|
|
pdev = pnv_phb4_find_cfg_dev(phb);
|
|
|
|
if (!pdev) {
|
|
|
|
return ~0ull;
|
|
|
|
}
|
|
|
|
cfg_addr = (phb->regs[PHB_CONFIG_ADDRESS >> 3] >> 32) & 0xffc;
|
|
|
|
cfg_addr |= off;
|
|
|
|
limit = pci_config_size(pdev);
|
|
|
|
if (limit <= cfg_addr) {
|
|
|
|
/*
|
|
|
|
* conventional pci device can be behind pcie-to-pci bridge.
|
|
|
|
* 256 <= addr < 4K has no effects.
|
|
|
|
*/
|
|
|
|
return ~0ull;
|
|
|
|
}
|
|
|
|
val = pci_host_config_read_common(pdev, cfg_addr, limit, size);
|
|
|
|
switch (size) {
|
|
|
|
case 1:
|
|
|
|
return val;
|
|
|
|
case 2:
|
|
|
|
return bswap16(val);
|
|
|
|
case 4:
|
|
|
|
return bswap32(val);
|
|
|
|
default:
|
|
|
|
g_assert_not_reached();
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Root complex register accesses are memory mapped.
|
|
|
|
*/
|
|
|
|
static void pnv_phb4_rc_config_write(PnvPHB4 *phb, unsigned off,
|
|
|
|
unsigned size, uint64_t val)
|
|
|
|
{
|
2022-06-24 11:49:14 +03:00
|
|
|
PCIHostState *pci = PCI_HOST_BRIDGE(phb->phb_base);
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
PCIDevice *pdev;
|
|
|
|
|
|
|
|
if (size != 4) {
|
2023-06-20 02:36:36 +03:00
|
|
|
phb_error(phb, "rc_config_write invalid size %d", size);
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
pdev = pci_find_device(pci->bus, 0, 0);
|
2022-01-12 13:28:27 +03:00
|
|
|
if (!pdev) {
|
2023-06-20 02:36:36 +03:00
|
|
|
phb_error(phb, "rc_config_write device not found");
|
2022-01-12 13:28:27 +03:00
|
|
|
return;
|
|
|
|
}
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
|
|
|
|
pci_host_config_write_common(pdev, off, PHB_RC_CONFIG_SIZE,
|
|
|
|
bswap32(val), 4);
|
|
|
|
}
|
|
|
|
|
|
|
|
static uint64_t pnv_phb4_rc_config_read(PnvPHB4 *phb, unsigned off,
|
|
|
|
unsigned size)
|
|
|
|
{
|
2022-06-24 11:49:14 +03:00
|
|
|
PCIHostState *pci = PCI_HOST_BRIDGE(phb->phb_base);
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
PCIDevice *pdev;
|
|
|
|
uint64_t val;
|
|
|
|
|
|
|
|
if (size != 4) {
|
2023-06-20 02:36:36 +03:00
|
|
|
phb_error(phb, "rc_config_read invalid size %d", size);
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
return ~0ull;
|
|
|
|
}
|
|
|
|
|
|
|
|
pdev = pci_find_device(pci->bus, 0, 0);
|
2022-01-12 13:28:27 +03:00
|
|
|
if (!pdev) {
|
2023-06-20 02:36:36 +03:00
|
|
|
phb_error(phb, "rc_config_read device not found");
|
2022-01-12 13:28:27 +03:00
|
|
|
return ~0ull;
|
|
|
|
}
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
|
|
|
|
val = pci_host_config_read_common(pdev, off, PHB_RC_CONFIG_SIZE, 4);
|
|
|
|
return bswap32(val);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void pnv_phb4_check_mbt(PnvPHB4 *phb, uint32_t index)
|
|
|
|
{
|
|
|
|
uint64_t base, start, size, mbe0, mbe1;
|
|
|
|
MemoryRegion *parent;
|
|
|
|
char name[64];
|
|
|
|
|
|
|
|
/* Unmap first */
|
|
|
|
if (memory_region_is_mapped(&phb->mr_mmio[index])) {
|
|
|
|
/* Should we destroy it in RCU friendly way... ? */
|
|
|
|
memory_region_del_subregion(phb->mr_mmio[index].container,
|
|
|
|
&phb->mr_mmio[index]);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Get table entry */
|
|
|
|
mbe0 = phb->ioda_MBT[(index << 1)];
|
|
|
|
mbe1 = phb->ioda_MBT[(index << 1) + 1];
|
|
|
|
|
|
|
|
if (!(mbe0 & IODA3_MBT0_ENABLE)) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Grab geometry from registers */
|
|
|
|
base = GETFIELD(IODA3_MBT0_BASE_ADDR, mbe0) << 12;
|
|
|
|
size = GETFIELD(IODA3_MBT1_MASK, mbe1) << 12;
|
|
|
|
size |= 0xff00000000000000ull;
|
|
|
|
size = ~size + 1;
|
|
|
|
|
|
|
|
/* Calculate PCI side start address based on M32/M64 window type */
|
|
|
|
if (mbe0 & IODA3_MBT0_TYPE_M32) {
|
|
|
|
start = phb->regs[PHB_M32_START_ADDR >> 3];
|
|
|
|
if ((start + size) > 0x100000000ull) {
|
|
|
|
phb_error(phb, "M32 set beyond 4GB boundary !");
|
|
|
|
size = 0x100000000 - start;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
start = base | (phb->regs[PHB_M64_UPPER_BITS >> 3]);
|
|
|
|
}
|
|
|
|
|
2023-07-14 14:27:04 +03:00
|
|
|
/* TODO: Figure out how to implement/decode AOMASK */
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
|
|
|
|
/* Check if it matches an enabled MMIO region in the PEC stack */
|
2022-01-18 14:56:31 +03:00
|
|
|
if (memory_region_is_mapped(&phb->mmbar0) &&
|
|
|
|
base >= phb->mmio0_base &&
|
|
|
|
(base + size) <= (phb->mmio0_base + phb->mmio0_size)) {
|
|
|
|
parent = &phb->mmbar0;
|
|
|
|
base -= phb->mmio0_base;
|
|
|
|
} else if (memory_region_is_mapped(&phb->mmbar1) &&
|
|
|
|
base >= phb->mmio1_base &&
|
|
|
|
(base + size) <= (phb->mmio1_base + phb->mmio1_size)) {
|
|
|
|
parent = &phb->mmbar1;
|
|
|
|
base -= phb->mmio1_base;
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
} else {
|
|
|
|
phb_error(phb, "PHB MBAR %d out of parent bounds", index);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Create alias (better name ?) */
|
|
|
|
snprintf(name, sizeof(name), "phb4-mbar%d", index);
|
|
|
|
memory_region_init_alias(&phb->mr_mmio[index], OBJECT(phb), name,
|
|
|
|
&phb->pci_mmio, start, size);
|
|
|
|
memory_region_add_subregion(parent, base, &phb->mr_mmio[index]);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void pnv_phb4_check_all_mbt(PnvPHB4 *phb)
|
|
|
|
{
|
|
|
|
uint64_t i;
|
|
|
|
uint32_t num_windows = phb->big_phb ? PNV_PHB4_MAX_MMIO_WINDOWS :
|
|
|
|
PNV_PHB4_MIN_MMIO_WINDOWS;
|
|
|
|
|
|
|
|
for (i = 0; i < num_windows; i++) {
|
|
|
|
pnv_phb4_check_mbt(phb, i);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static uint64_t *pnv_phb4_ioda_access(PnvPHB4 *phb,
|
|
|
|
unsigned *out_table, unsigned *out_idx)
|
|
|
|
{
|
|
|
|
uint64_t adreg = phb->regs[PHB_IODA_ADDR >> 3];
|
|
|
|
unsigned int index = GETFIELD(PHB_IODA_AD_TADR, adreg);
|
|
|
|
unsigned int table = GETFIELD(PHB_IODA_AD_TSEL, adreg);
|
|
|
|
unsigned int mask;
|
|
|
|
uint64_t *tptr = NULL;
|
|
|
|
|
|
|
|
switch (table) {
|
|
|
|
case IODA3_TBL_LIST:
|
|
|
|
tptr = phb->ioda_LIST;
|
|
|
|
mask = 7;
|
|
|
|
break;
|
|
|
|
case IODA3_TBL_MIST:
|
|
|
|
tptr = phb->ioda_MIST;
|
|
|
|
mask = phb->big_phb ? PNV_PHB4_MAX_MIST : (PNV_PHB4_MAX_MIST >> 1);
|
|
|
|
mask -= 1;
|
|
|
|
break;
|
|
|
|
case IODA3_TBL_RCAM:
|
|
|
|
mask = phb->big_phb ? 127 : 63;
|
|
|
|
break;
|
|
|
|
case IODA3_TBL_MRT:
|
|
|
|
mask = phb->big_phb ? 15 : 7;
|
|
|
|
break;
|
|
|
|
case IODA3_TBL_PESTA:
|
|
|
|
case IODA3_TBL_PESTB:
|
|
|
|
mask = phb->big_phb ? PNV_PHB4_MAX_PEs : (PNV_PHB4_MAX_PEs >> 1);
|
|
|
|
mask -= 1;
|
|
|
|
break;
|
|
|
|
case IODA3_TBL_TVT:
|
|
|
|
tptr = phb->ioda_TVT;
|
|
|
|
mask = phb->big_phb ? PNV_PHB4_MAX_TVEs : (PNV_PHB4_MAX_TVEs >> 1);
|
|
|
|
mask -= 1;
|
|
|
|
break;
|
|
|
|
case IODA3_TBL_TCR:
|
|
|
|
case IODA3_TBL_TDR:
|
|
|
|
mask = phb->big_phb ? 1023 : 511;
|
|
|
|
break;
|
|
|
|
case IODA3_TBL_MBT:
|
|
|
|
tptr = phb->ioda_MBT;
|
|
|
|
mask = phb->big_phb ? PNV_PHB4_MAX_MBEs : (PNV_PHB4_MAX_MBEs >> 1);
|
|
|
|
mask -= 1;
|
|
|
|
break;
|
|
|
|
case IODA3_TBL_MDT:
|
|
|
|
tptr = phb->ioda_MDT;
|
|
|
|
mask = phb->big_phb ? PNV_PHB4_MAX_PEs : (PNV_PHB4_MAX_PEs >> 1);
|
|
|
|
mask -= 1;
|
|
|
|
break;
|
|
|
|
case IODA3_TBL_PEEV:
|
|
|
|
tptr = phb->ioda_PEEV;
|
|
|
|
mask = phb->big_phb ? PNV_PHB4_MAX_PEEVs : (PNV_PHB4_MAX_PEEVs >> 1);
|
|
|
|
mask -= 1;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
phb_error(phb, "invalid IODA table %d", table);
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
index &= mask;
|
|
|
|
if (out_idx) {
|
|
|
|
*out_idx = index;
|
|
|
|
}
|
|
|
|
if (out_table) {
|
|
|
|
*out_table = table;
|
|
|
|
}
|
|
|
|
if (tptr) {
|
|
|
|
tptr += index;
|
|
|
|
}
|
|
|
|
if (adreg & PHB_IODA_AD_AUTOINC) {
|
|
|
|
index = (index + 1) & mask;
|
|
|
|
adreg = SETFIELD(PHB_IODA_AD_TADR, adreg, index);
|
|
|
|
}
|
|
|
|
|
|
|
|
phb->regs[PHB_IODA_ADDR >> 3] = adreg;
|
|
|
|
return tptr;
|
|
|
|
}
|
|
|
|
|
|
|
|
static uint64_t pnv_phb4_ioda_read(PnvPHB4 *phb)
|
|
|
|
{
|
|
|
|
unsigned table, idx;
|
|
|
|
uint64_t *tptr;
|
|
|
|
|
|
|
|
tptr = pnv_phb4_ioda_access(phb, &table, &idx);
|
|
|
|
if (!tptr) {
|
|
|
|
/* Special PESTA case */
|
|
|
|
if (table == IODA3_TBL_PESTA) {
|
|
|
|
return ((uint64_t)(phb->ioda_PEST_AB[idx] & 1)) << 63;
|
|
|
|
} else if (table == IODA3_TBL_PESTB) {
|
|
|
|
return ((uint64_t)(phb->ioda_PEST_AB[idx] & 2)) << 62;
|
|
|
|
}
|
|
|
|
/* Return 0 on unsupported tables, not ff's */
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
return *tptr;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void pnv_phb4_ioda_write(PnvPHB4 *phb, uint64_t val)
|
|
|
|
{
|
|
|
|
unsigned table, idx;
|
|
|
|
uint64_t *tptr;
|
|
|
|
|
|
|
|
tptr = pnv_phb4_ioda_access(phb, &table, &idx);
|
|
|
|
if (!tptr) {
|
|
|
|
/* Special PESTA case */
|
|
|
|
if (table == IODA3_TBL_PESTA) {
|
|
|
|
phb->ioda_PEST_AB[idx] &= ~1;
|
|
|
|
phb->ioda_PEST_AB[idx] |= (val >> 63) & 1;
|
|
|
|
} else if (table == IODA3_TBL_PESTB) {
|
|
|
|
phb->ioda_PEST_AB[idx] &= ~2;
|
|
|
|
phb->ioda_PEST_AB[idx] |= (val >> 62) & 2;
|
|
|
|
}
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Handle side effects */
|
|
|
|
switch (table) {
|
|
|
|
case IODA3_TBL_LIST:
|
|
|
|
break;
|
|
|
|
case IODA3_TBL_MIST: {
|
|
|
|
/* Special mask for MIST partial write */
|
|
|
|
uint64_t adreg = phb->regs[PHB_IODA_ADDR >> 3];
|
|
|
|
uint32_t mmask = GETFIELD(PHB_IODA_AD_MIST_PWV, adreg);
|
|
|
|
uint64_t v = *tptr;
|
|
|
|
if (mmask == 0) {
|
|
|
|
mmask = 0xf;
|
|
|
|
}
|
|
|
|
if (mmask & 8) {
|
|
|
|
v &= 0x0000ffffffffffffull;
|
|
|
|
v |= 0xcfff000000000000ull & val;
|
|
|
|
}
|
|
|
|
if (mmask & 4) {
|
|
|
|
v &= 0xffff0000ffffffffull;
|
|
|
|
v |= 0x0000cfff00000000ull & val;
|
|
|
|
}
|
|
|
|
if (mmask & 2) {
|
|
|
|
v &= 0xffffffff0000ffffull;
|
|
|
|
v |= 0x00000000cfff0000ull & val;
|
|
|
|
}
|
|
|
|
if (mmask & 1) {
|
|
|
|
v &= 0xffffffffffff0000ull;
|
|
|
|
v |= 0x000000000000cfffull & val;
|
|
|
|
}
|
2021-07-12 23:04:37 +03:00
|
|
|
*tptr = v;
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
case IODA3_TBL_MBT:
|
|
|
|
*tptr = val;
|
|
|
|
|
2023-07-14 14:27:04 +03:00
|
|
|
/* Copy across the valid bit to the other half */
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
phb->ioda_MBT[idx ^ 1] &= 0x7fffffffffffffffull;
|
|
|
|
phb->ioda_MBT[idx ^ 1] |= 0x8000000000000000ull & val;
|
|
|
|
|
|
|
|
/* Update mappings */
|
|
|
|
pnv_phb4_check_mbt(phb, idx >> 1);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
*tptr = val;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void pnv_phb4_rtc_invalidate(PnvPHB4 *phb, uint64_t val)
|
|
|
|
{
|
|
|
|
PnvPhb4DMASpace *ds;
|
|
|
|
|
|
|
|
/* Always invalidate all for now ... */
|
|
|
|
QLIST_FOREACH(ds, &phb->dma_spaces, list) {
|
|
|
|
ds->pe_num = PHB_INVALID_PE;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void pnv_phb4_update_msi_regions(PnvPhb4DMASpace *ds)
|
|
|
|
{
|
|
|
|
uint64_t cfg = ds->phb->regs[PHB_PHB4_CONFIG >> 3];
|
|
|
|
|
|
|
|
if (cfg & PHB_PHB4C_32BIT_MSI_EN) {
|
|
|
|
if (!memory_region_is_mapped(MEMORY_REGION(&ds->msi32_mr))) {
|
|
|
|
memory_region_add_subregion(MEMORY_REGION(&ds->dma_mr),
|
|
|
|
0xffff0000, &ds->msi32_mr);
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
if (memory_region_is_mapped(MEMORY_REGION(&ds->msi32_mr))) {
|
|
|
|
memory_region_del_subregion(MEMORY_REGION(&ds->dma_mr),
|
|
|
|
&ds->msi32_mr);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (cfg & PHB_PHB4C_64BIT_MSI_EN) {
|
|
|
|
if (!memory_region_is_mapped(MEMORY_REGION(&ds->msi64_mr))) {
|
|
|
|
memory_region_add_subregion(MEMORY_REGION(&ds->dma_mr),
|
|
|
|
(1ull << 60), &ds->msi64_mr);
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
if (memory_region_is_mapped(MEMORY_REGION(&ds->msi64_mr))) {
|
|
|
|
memory_region_del_subregion(MEMORY_REGION(&ds->dma_mr),
|
|
|
|
&ds->msi64_mr);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void pnv_phb4_update_all_msi_regions(PnvPHB4 *phb)
|
|
|
|
{
|
|
|
|
PnvPhb4DMASpace *ds;
|
|
|
|
|
|
|
|
QLIST_FOREACH(ds, &phb->dma_spaces, list) {
|
|
|
|
pnv_phb4_update_msi_regions(ds);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void pnv_phb4_update_xsrc(PnvPHB4 *phb)
|
|
|
|
{
|
|
|
|
int shift, flags, i, lsi_base;
|
|
|
|
XiveSource *xsrc = &phb->xsrc;
|
|
|
|
|
|
|
|
/* The XIVE source characteristics can be set at run time */
|
|
|
|
if (phb->regs[PHB_CTRLR >> 3] & PHB_CTRLR_IRQ_PGSZ_64K) {
|
|
|
|
shift = XIVE_ESB_64K;
|
|
|
|
} else {
|
|
|
|
shift = XIVE_ESB_4K;
|
|
|
|
}
|
|
|
|
if (phb->regs[PHB_CTRLR >> 3] & PHB_CTRLR_IRQ_STORE_EOI) {
|
|
|
|
flags = XIVE_SRC_STORE_EOI;
|
|
|
|
} else {
|
|
|
|
flags = 0;
|
|
|
|
}
|
|
|
|
|
2022-03-02 08:51:39 +03:00
|
|
|
/*
|
|
|
|
* When the PQ disable configuration bit is set, the check on the
|
|
|
|
* PQ state bits is disabled on the PHB side (for MSI only) and it
|
|
|
|
* is performed on the IC side instead.
|
|
|
|
*/
|
|
|
|
if (phb->regs[PHB_CTRLR >> 3] & PHB_CTRLR_IRQ_PQ_DISABLE) {
|
|
|
|
flags |= XIVE_SRC_PQ_DISABLE;
|
|
|
|
}
|
|
|
|
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
phb->xsrc.esb_shift = shift;
|
|
|
|
phb->xsrc.esb_flags = flags;
|
|
|
|
|
|
|
|
lsi_base = GETFIELD(PHB_LSI_SRC_ID, phb->regs[PHB_LSI_SOURCE_ID >> 3]);
|
|
|
|
lsi_base <<= 3;
|
|
|
|
|
|
|
|
/* TODO: handle reset values of PHB_LSI_SRC_ID */
|
|
|
|
if (!lsi_base) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* TODO: need a xive_source_irq_reset_lsi() */
|
|
|
|
bitmap_zero(xsrc->lsi_map, xsrc->nr_irqs);
|
|
|
|
|
|
|
|
for (i = 0; i < xsrc->nr_irqs; i++) {
|
|
|
|
bool msi = (i < lsi_base || i >= (lsi_base + 8));
|
|
|
|
if (!msi) {
|
|
|
|
xive_source_irq_set_lsi(xsrc, i);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void pnv_phb4_reg_write(void *opaque, hwaddr off, uint64_t val,
|
|
|
|
unsigned size)
|
|
|
|
{
|
|
|
|
PnvPHB4 *phb = PNV_PHB4(opaque);
|
|
|
|
bool changed;
|
|
|
|
|
|
|
|
/* Special case outbound configuration data */
|
|
|
|
if ((off & 0xfffc) == PHB_CONFIG_DATA) {
|
|
|
|
pnv_phb4_config_write(phb, off & 0x3, size, val);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Special case RC configuration space */
|
|
|
|
if ((off & 0xf800) == PHB_RC_CONFIG_BASE) {
|
|
|
|
pnv_phb4_rc_config_write(phb, off & 0x7ff, size, val);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Other registers are 64-bit only */
|
|
|
|
if (size != 8 || off & 0x7) {
|
|
|
|
phb_error(phb, "Invalid register access, offset: 0x%"PRIx64" size: %d",
|
|
|
|
off, size);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Handle masking */
|
|
|
|
switch (off) {
|
|
|
|
case PHB_LSI_SOURCE_ID:
|
|
|
|
val &= PHB_LSI_SRC_ID;
|
|
|
|
break;
|
|
|
|
case PHB_M64_UPPER_BITS:
|
|
|
|
val &= 0xff00000000000000ull;
|
|
|
|
break;
|
|
|
|
/* TCE Kill */
|
|
|
|
case PHB_TCE_KILL:
|
|
|
|
/* Clear top 3 bits which HW does to indicate successful queuing */
|
|
|
|
val &= ~(PHB_TCE_KILL_ALL | PHB_TCE_KILL_PE | PHB_TCE_KILL_ONE);
|
|
|
|
break;
|
|
|
|
case PHB_Q_DMA_R:
|
|
|
|
/*
|
|
|
|
* This is enough logic to make SW happy but we aren't
|
|
|
|
* actually quiescing the DMAs
|
|
|
|
*/
|
|
|
|
if (val & PHB_Q_DMA_R_AUTORESET) {
|
|
|
|
val = 0;
|
|
|
|
} else {
|
|
|
|
val &= PHB_Q_DMA_R_QUIESCE_DMA;
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
/* LEM stuff */
|
|
|
|
case PHB_LEM_FIR_AND_MASK:
|
|
|
|
phb->regs[PHB_LEM_FIR_ACCUM >> 3] &= val;
|
|
|
|
return;
|
|
|
|
case PHB_LEM_FIR_OR_MASK:
|
|
|
|
phb->regs[PHB_LEM_FIR_ACCUM >> 3] |= val;
|
|
|
|
return;
|
|
|
|
case PHB_LEM_ERROR_AND_MASK:
|
|
|
|
phb->regs[PHB_LEM_ERROR_MASK >> 3] &= val;
|
|
|
|
return;
|
|
|
|
case PHB_LEM_ERROR_OR_MASK:
|
|
|
|
phb->regs[PHB_LEM_ERROR_MASK >> 3] |= val;
|
|
|
|
return;
|
|
|
|
case PHB_LEM_WOF:
|
|
|
|
val = 0;
|
|
|
|
break;
|
|
|
|
/* TODO: More regs ..., maybe create a table with masks... */
|
|
|
|
|
|
|
|
/* Read only registers */
|
|
|
|
case PHB_CPU_LOADSTORE_STATUS:
|
|
|
|
case PHB_ETU_ERR_SUMMARY:
|
|
|
|
case PHB_PHB4_GEN_CAP:
|
|
|
|
case PHB_PHB4_TCE_CAP:
|
|
|
|
case PHB_PHB4_IRQ_CAP:
|
|
|
|
case PHB_PHB4_EEH_CAP:
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Record whether it changed */
|
|
|
|
changed = phb->regs[off >> 3] != val;
|
|
|
|
|
|
|
|
/* Store in register cache first */
|
|
|
|
phb->regs[off >> 3] = val;
|
|
|
|
|
|
|
|
/* Handle side effects */
|
|
|
|
switch (off) {
|
|
|
|
case PHB_PHB4_CONFIG:
|
|
|
|
if (changed) {
|
|
|
|
pnv_phb4_update_all_msi_regions(phb);
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
case PHB_M32_START_ADDR:
|
|
|
|
case PHB_M64_UPPER_BITS:
|
|
|
|
if (changed) {
|
|
|
|
pnv_phb4_check_all_mbt(phb);
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
|
|
|
|
/* IODA table accesses */
|
|
|
|
case PHB_IODA_DATA0:
|
|
|
|
pnv_phb4_ioda_write(phb, val);
|
|
|
|
break;
|
|
|
|
|
|
|
|
/* RTC invalidation */
|
|
|
|
case PHB_RTC_INVALIDATE:
|
|
|
|
pnv_phb4_rtc_invalidate(phb, val);
|
|
|
|
break;
|
|
|
|
|
|
|
|
/* PHB Control (Affects XIVE source) */
|
|
|
|
case PHB_CTRLR:
|
|
|
|
case PHB_LSI_SOURCE_ID:
|
|
|
|
pnv_phb4_update_xsrc(phb);
|
|
|
|
break;
|
|
|
|
|
|
|
|
/* Silent simple writes */
|
|
|
|
case PHB_ASN_CMPM:
|
|
|
|
case PHB_CONFIG_ADDRESS:
|
|
|
|
case PHB_IODA_ADDR:
|
|
|
|
case PHB_TCE_KILL:
|
|
|
|
case PHB_TCE_SPEC_CTL:
|
|
|
|
case PHB_PEST_BAR:
|
|
|
|
case PHB_PELTV_BAR:
|
|
|
|
case PHB_RTT_BAR:
|
|
|
|
case PHB_LEM_FIR_ACCUM:
|
|
|
|
case PHB_LEM_ERROR_MASK:
|
|
|
|
case PHB_LEM_ACTION0:
|
|
|
|
case PHB_LEM_ACTION1:
|
|
|
|
case PHB_TCE_TAG_ENABLE:
|
|
|
|
case PHB_INT_NOTIFY_ADDR:
|
|
|
|
case PHB_INT_NOTIFY_INDEX:
|
|
|
|
case PHB_DMARD_SYNC:
|
|
|
|
break;
|
|
|
|
|
|
|
|
/* Noise on anything else */
|
|
|
|
default:
|
|
|
|
qemu_log_mask(LOG_UNIMP, "phb4: reg_write 0x%"PRIx64"=%"PRIx64"\n",
|
|
|
|
off, val);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static uint64_t pnv_phb4_reg_read(void *opaque, hwaddr off, unsigned size)
|
|
|
|
{
|
|
|
|
PnvPHB4 *phb = PNV_PHB4(opaque);
|
|
|
|
uint64_t val;
|
|
|
|
|
|
|
|
if ((off & 0xfffc) == PHB_CONFIG_DATA) {
|
|
|
|
return pnv_phb4_config_read(phb, off & 0x3, size);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Special case RC configuration space */
|
|
|
|
if ((off & 0xf800) == PHB_RC_CONFIG_BASE) {
|
|
|
|
return pnv_phb4_rc_config_read(phb, off & 0x7ff, size);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Other registers are 64-bit only */
|
|
|
|
if (size != 8 || off & 0x7) {
|
|
|
|
phb_error(phb, "Invalid register access, offset: 0x%"PRIx64" size: %d",
|
|
|
|
off, size);
|
|
|
|
return ~0ull;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Default read from cache */
|
|
|
|
val = phb->regs[off >> 3];
|
|
|
|
|
|
|
|
switch (off) {
|
|
|
|
case PHB_VERSION:
|
2022-01-18 14:56:31 +03:00
|
|
|
return PNV_PHB4_PEC_GET_CLASS(phb->pec)->version;
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
|
|
|
|
/* Read-only */
|
|
|
|
case PHB_PHB4_GEN_CAP:
|
|
|
|
return 0xe4b8000000000000ull;
|
|
|
|
case PHB_PHB4_TCE_CAP:
|
|
|
|
return phb->big_phb ? 0x4008440000000400ull : 0x2008440000000200ull;
|
|
|
|
case PHB_PHB4_IRQ_CAP:
|
|
|
|
return phb->big_phb ? 0x0800000000001000ull : 0x0800000000000800ull;
|
|
|
|
case PHB_PHB4_EEH_CAP:
|
|
|
|
return phb->big_phb ? 0x2000000000000000ull : 0x1000000000000000ull;
|
|
|
|
|
|
|
|
/* IODA table accesses */
|
|
|
|
case PHB_IODA_DATA0:
|
|
|
|
return pnv_phb4_ioda_read(phb);
|
|
|
|
|
|
|
|
/* Link training always appears trained */
|
|
|
|
case PHB_PCIE_DLP_TRAIN_CTL:
|
|
|
|
/* TODO: Do something sensible with speed ? */
|
|
|
|
return PHB_PCIE_DLP_INBAND_PRESENCE | PHB_PCIE_DLP_TL_LINKACT;
|
|
|
|
|
|
|
|
/* DMA read sync: make it look like it's complete */
|
|
|
|
case PHB_DMARD_SYNC:
|
|
|
|
return PHB_DMARD_SYNC_COMPLETE;
|
|
|
|
|
|
|
|
/* Silent simple reads */
|
|
|
|
case PHB_LSI_SOURCE_ID:
|
|
|
|
case PHB_CPU_LOADSTORE_STATUS:
|
|
|
|
case PHB_ASN_CMPM:
|
|
|
|
case PHB_PHB4_CONFIG:
|
|
|
|
case PHB_M32_START_ADDR:
|
|
|
|
case PHB_CONFIG_ADDRESS:
|
|
|
|
case PHB_IODA_ADDR:
|
|
|
|
case PHB_RTC_INVALIDATE:
|
|
|
|
case PHB_TCE_KILL:
|
|
|
|
case PHB_TCE_SPEC_CTL:
|
|
|
|
case PHB_PEST_BAR:
|
|
|
|
case PHB_PELTV_BAR:
|
|
|
|
case PHB_RTT_BAR:
|
|
|
|
case PHB_M64_UPPER_BITS:
|
|
|
|
case PHB_CTRLR:
|
|
|
|
case PHB_LEM_FIR_ACCUM:
|
|
|
|
case PHB_LEM_ERROR_MASK:
|
|
|
|
case PHB_LEM_ACTION0:
|
|
|
|
case PHB_LEM_ACTION1:
|
|
|
|
case PHB_TCE_TAG_ENABLE:
|
|
|
|
case PHB_INT_NOTIFY_ADDR:
|
|
|
|
case PHB_INT_NOTIFY_INDEX:
|
|
|
|
case PHB_Q_DMA_R:
|
|
|
|
case PHB_ETU_ERR_SUMMARY:
|
|
|
|
break;
|
|
|
|
|
|
|
|
/* Noise on anything else */
|
|
|
|
default:
|
|
|
|
qemu_log_mask(LOG_UNIMP, "phb4: reg_read 0x%"PRIx64"=%"PRIx64"\n",
|
|
|
|
off, val);
|
|
|
|
}
|
|
|
|
return val;
|
|
|
|
}
|
|
|
|
|
|
|
|
static const MemoryRegionOps pnv_phb4_reg_ops = {
|
|
|
|
.read = pnv_phb4_reg_read,
|
|
|
|
.write = pnv_phb4_reg_write,
|
|
|
|
.valid.min_access_size = 1,
|
|
|
|
.valid.max_access_size = 8,
|
|
|
|
.impl.min_access_size = 1,
|
|
|
|
.impl.max_access_size = 8,
|
|
|
|
.endianness = DEVICE_BIG_ENDIAN,
|
|
|
|
};
|
|
|
|
|
|
|
|
static uint64_t pnv_phb4_xscom_read(void *opaque, hwaddr addr, unsigned size)
|
|
|
|
{
|
|
|
|
PnvPHB4 *phb = PNV_PHB4(opaque);
|
|
|
|
uint32_t reg = addr >> 3;
|
|
|
|
uint64_t val;
|
|
|
|
hwaddr offset;
|
|
|
|
|
|
|
|
switch (reg) {
|
|
|
|
case PHB_SCOM_HV_IND_ADDR:
|
|
|
|
return phb->scom_hv_ind_addr_reg;
|
|
|
|
|
|
|
|
case PHB_SCOM_HV_IND_DATA:
|
|
|
|
if (!(phb->scom_hv_ind_addr_reg & PHB_SCOM_HV_IND_ADDR_VALID)) {
|
|
|
|
phb_error(phb, "Invalid indirect address");
|
|
|
|
return ~0ull;
|
|
|
|
}
|
|
|
|
size = (phb->scom_hv_ind_addr_reg & PHB_SCOM_HV_IND_ADDR_4B) ? 4 : 8;
|
|
|
|
offset = GETFIELD(PHB_SCOM_HV_IND_ADDR_ADDR, phb->scom_hv_ind_addr_reg);
|
|
|
|
val = pnv_phb4_reg_read(phb, offset, size);
|
|
|
|
if (phb->scom_hv_ind_addr_reg & PHB_SCOM_HV_IND_ADDR_AUTOINC) {
|
|
|
|
offset += size;
|
|
|
|
offset &= 0x3fff;
|
|
|
|
phb->scom_hv_ind_addr_reg = SETFIELD(PHB_SCOM_HV_IND_ADDR_ADDR,
|
|
|
|
phb->scom_hv_ind_addr_reg,
|
|
|
|
offset);
|
|
|
|
}
|
|
|
|
return val;
|
|
|
|
case PHB_SCOM_ETU_LEM_FIR:
|
|
|
|
case PHB_SCOM_ETU_LEM_FIR_AND:
|
|
|
|
case PHB_SCOM_ETU_LEM_FIR_OR:
|
|
|
|
case PHB_SCOM_ETU_LEM_FIR_MSK:
|
|
|
|
case PHB_SCOM_ETU_LEM_ERR_MSK_AND:
|
|
|
|
case PHB_SCOM_ETU_LEM_ERR_MSK_OR:
|
|
|
|
case PHB_SCOM_ETU_LEM_ACT0:
|
|
|
|
case PHB_SCOM_ETU_LEM_ACT1:
|
|
|
|
case PHB_SCOM_ETU_LEM_WOF:
|
|
|
|
offset = ((reg - PHB_SCOM_ETU_LEM_FIR) << 3) + PHB_LEM_FIR_ACCUM;
|
|
|
|
return pnv_phb4_reg_read(phb, offset, size);
|
|
|
|
case PHB_SCOM_ETU_PMON_CONFIG:
|
|
|
|
case PHB_SCOM_ETU_PMON_CTR0:
|
|
|
|
case PHB_SCOM_ETU_PMON_CTR1:
|
|
|
|
case PHB_SCOM_ETU_PMON_CTR2:
|
|
|
|
case PHB_SCOM_ETU_PMON_CTR3:
|
|
|
|
offset = ((reg - PHB_SCOM_ETU_PMON_CONFIG) << 3) + PHB_PERFMON_CONFIG;
|
|
|
|
return pnv_phb4_reg_read(phb, offset, size);
|
|
|
|
|
|
|
|
default:
|
|
|
|
qemu_log_mask(LOG_UNIMP, "phb4: xscom_read 0x%"HWADDR_PRIx"\n", addr);
|
|
|
|
return ~0ull;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void pnv_phb4_xscom_write(void *opaque, hwaddr addr,
|
|
|
|
uint64_t val, unsigned size)
|
|
|
|
{
|
|
|
|
PnvPHB4 *phb = PNV_PHB4(opaque);
|
|
|
|
uint32_t reg = addr >> 3;
|
|
|
|
hwaddr offset;
|
|
|
|
|
|
|
|
switch (reg) {
|
|
|
|
case PHB_SCOM_HV_IND_ADDR:
|
|
|
|
phb->scom_hv_ind_addr_reg = val & 0xe000000000001fff;
|
|
|
|
break;
|
|
|
|
case PHB_SCOM_HV_IND_DATA:
|
|
|
|
if (!(phb->scom_hv_ind_addr_reg & PHB_SCOM_HV_IND_ADDR_VALID)) {
|
|
|
|
phb_error(phb, "Invalid indirect address");
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
size = (phb->scom_hv_ind_addr_reg & PHB_SCOM_HV_IND_ADDR_4B) ? 4 : 8;
|
|
|
|
offset = GETFIELD(PHB_SCOM_HV_IND_ADDR_ADDR, phb->scom_hv_ind_addr_reg);
|
|
|
|
pnv_phb4_reg_write(phb, offset, val, size);
|
|
|
|
if (phb->scom_hv_ind_addr_reg & PHB_SCOM_HV_IND_ADDR_AUTOINC) {
|
|
|
|
offset += size;
|
|
|
|
offset &= 0x3fff;
|
|
|
|
phb->scom_hv_ind_addr_reg = SETFIELD(PHB_SCOM_HV_IND_ADDR_ADDR,
|
|
|
|
phb->scom_hv_ind_addr_reg,
|
|
|
|
offset);
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
case PHB_SCOM_ETU_LEM_FIR:
|
|
|
|
case PHB_SCOM_ETU_LEM_FIR_AND:
|
|
|
|
case PHB_SCOM_ETU_LEM_FIR_OR:
|
|
|
|
case PHB_SCOM_ETU_LEM_FIR_MSK:
|
|
|
|
case PHB_SCOM_ETU_LEM_ERR_MSK_AND:
|
|
|
|
case PHB_SCOM_ETU_LEM_ERR_MSK_OR:
|
|
|
|
case PHB_SCOM_ETU_LEM_ACT0:
|
|
|
|
case PHB_SCOM_ETU_LEM_ACT1:
|
|
|
|
case PHB_SCOM_ETU_LEM_WOF:
|
|
|
|
offset = ((reg - PHB_SCOM_ETU_LEM_FIR) << 3) + PHB_LEM_FIR_ACCUM;
|
|
|
|
pnv_phb4_reg_write(phb, offset, val, size);
|
|
|
|
break;
|
|
|
|
case PHB_SCOM_ETU_PMON_CONFIG:
|
|
|
|
case PHB_SCOM_ETU_PMON_CTR0:
|
|
|
|
case PHB_SCOM_ETU_PMON_CTR1:
|
|
|
|
case PHB_SCOM_ETU_PMON_CTR2:
|
|
|
|
case PHB_SCOM_ETU_PMON_CTR3:
|
|
|
|
offset = ((reg - PHB_SCOM_ETU_PMON_CONFIG) << 3) + PHB_PERFMON_CONFIG;
|
|
|
|
pnv_phb4_reg_write(phb, offset, val, size);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
qemu_log_mask(LOG_UNIMP, "phb4: xscom_write 0x%"HWADDR_PRIx
|
|
|
|
"=%"PRIx64"\n", addr, val);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
const MemoryRegionOps pnv_phb4_xscom_ops = {
|
|
|
|
.read = pnv_phb4_xscom_read,
|
|
|
|
.write = pnv_phb4_xscom_write,
|
|
|
|
.valid.min_access_size = 8,
|
|
|
|
.valid.max_access_size = 8,
|
|
|
|
.impl.min_access_size = 8,
|
|
|
|
.impl.max_access_size = 8,
|
|
|
|
.endianness = DEVICE_BIG_ENDIAN,
|
|
|
|
};
|
|
|
|
|
2022-01-12 13:28:27 +03:00
|
|
|
static uint64_t pnv_pec_stk_nest_xscom_read(void *opaque, hwaddr addr,
|
|
|
|
unsigned size)
|
|
|
|
{
|
2022-01-18 14:56:31 +03:00
|
|
|
PnvPHB4 *phb = PNV_PHB4(opaque);
|
2022-01-12 13:28:27 +03:00
|
|
|
uint32_t reg = addr >> 3;
|
|
|
|
|
|
|
|
/* TODO: add list of allowed registers and error out if not */
|
2022-01-18 14:56:31 +03:00
|
|
|
return phb->nest_regs[reg];
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
|
|
|
|
2022-01-18 14:56:31 +03:00
|
|
|
/*
|
|
|
|
* Return the 'stack_no' of a PHB4. 'stack_no' is the order
|
|
|
|
* the PHB4 occupies in the PEC. This is the reverse of what
|
|
|
|
* pnv_phb4_pec_get_phb_id() does.
|
|
|
|
*
|
|
|
|
* E.g. a phb with phb_id = 4 and pec->index = 1 (PEC1) will
|
|
|
|
* be the second phb (stack_no = 1) of the PEC.
|
|
|
|
*/
|
|
|
|
static int pnv_phb4_get_phb_stack_no(PnvPHB4 *phb)
|
|
|
|
{
|
|
|
|
PnvPhb4PecState *pec = phb->pec;
|
|
|
|
PnvPhb4PecClass *pecc = PNV_PHB4_PEC_GET_CLASS(pec);
|
|
|
|
int index = pec->index;
|
|
|
|
int stack_no = phb->phb_id;
|
|
|
|
|
|
|
|
while (index--) {
|
2022-01-18 14:56:31 +03:00
|
|
|
stack_no -= pecc->num_phbs[index];
|
2022-01-18 14:56:31 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
return stack_no;
|
|
|
|
}
|
|
|
|
|
2022-01-18 14:56:31 +03:00
|
|
|
static void pnv_phb4_update_regions(PnvPHB4 *phb)
|
2022-01-12 13:28:27 +03:00
|
|
|
{
|
|
|
|
/* Unmap first always */
|
|
|
|
if (memory_region_is_mapped(&phb->mr_regs)) {
|
2022-01-18 14:56:30 +03:00
|
|
|
memory_region_del_subregion(&phb->phbbar, &phb->mr_regs);
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
|
|
|
if (memory_region_is_mapped(&phb->xsrc.esb_mmio)) {
|
2022-01-18 14:56:30 +03:00
|
|
|
memory_region_del_subregion(&phb->intbar, &phb->xsrc.esb_mmio);
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Map registers if enabled */
|
2022-01-18 14:56:30 +03:00
|
|
|
if (memory_region_is_mapped(&phb->phbbar)) {
|
|
|
|
memory_region_add_subregion(&phb->phbbar, 0, &phb->mr_regs);
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Map ESB if enabled */
|
2022-01-18 14:56:30 +03:00
|
|
|
if (memory_region_is_mapped(&phb->intbar)) {
|
|
|
|
memory_region_add_subregion(&phb->intbar, 0, &phb->xsrc.esb_mmio);
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Check/update m32 */
|
|
|
|
pnv_phb4_check_all_mbt(phb);
|
|
|
|
}
|
|
|
|
|
2022-01-18 14:56:31 +03:00
|
|
|
static void pnv_pec_phb_update_map(PnvPHB4 *phb)
|
2022-01-12 13:28:27 +03:00
|
|
|
{
|
2022-01-18 14:56:31 +03:00
|
|
|
PnvPhb4PecState *pec = phb->pec;
|
2022-01-12 13:28:27 +03:00
|
|
|
MemoryRegion *sysmem = get_system_memory();
|
2022-01-18 14:56:31 +03:00
|
|
|
uint64_t bar_en = phb->nest_regs[PEC_NEST_STK_BAR_EN];
|
2022-01-18 14:56:31 +03:00
|
|
|
int stack_no = pnv_phb4_get_phb_stack_no(phb);
|
2022-01-12 13:28:27 +03:00
|
|
|
uint64_t bar, mask, size;
|
|
|
|
char name[64];
|
|
|
|
|
|
|
|
/*
|
|
|
|
* NOTE: This will really not work well if those are remapped
|
|
|
|
* after the PHB has created its sub regions. We could do better
|
|
|
|
* if we had a way to resize regions but we don't really care
|
|
|
|
* that much in practice as the stuff below really only happens
|
|
|
|
* once early during boot
|
|
|
|
*/
|
|
|
|
|
|
|
|
/* Handle unmaps */
|
2022-01-18 14:56:31 +03:00
|
|
|
if (memory_region_is_mapped(&phb->mmbar0) &&
|
2022-01-12 13:28:27 +03:00
|
|
|
!(bar_en & PEC_NEST_STK_BAR_EN_MMIO0)) {
|
2022-01-18 14:56:31 +03:00
|
|
|
memory_region_del_subregion(sysmem, &phb->mmbar0);
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
2022-01-18 14:56:31 +03:00
|
|
|
if (memory_region_is_mapped(&phb->mmbar1) &&
|
2022-01-12 13:28:27 +03:00
|
|
|
!(bar_en & PEC_NEST_STK_BAR_EN_MMIO1)) {
|
2022-01-18 14:56:31 +03:00
|
|
|
memory_region_del_subregion(sysmem, &phb->mmbar1);
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
2022-01-18 14:56:30 +03:00
|
|
|
if (memory_region_is_mapped(&phb->phbbar) &&
|
2022-01-12 13:28:27 +03:00
|
|
|
!(bar_en & PEC_NEST_STK_BAR_EN_PHB)) {
|
2022-01-18 14:56:30 +03:00
|
|
|
memory_region_del_subregion(sysmem, &phb->phbbar);
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
2022-01-18 14:56:30 +03:00
|
|
|
if (memory_region_is_mapped(&phb->intbar) &&
|
2022-01-12 13:28:27 +03:00
|
|
|
!(bar_en & PEC_NEST_STK_BAR_EN_INT)) {
|
2022-01-18 14:56:30 +03:00
|
|
|
memory_region_del_subregion(sysmem, &phb->intbar);
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Update PHB */
|
2022-01-18 14:56:31 +03:00
|
|
|
pnv_phb4_update_regions(phb);
|
2022-01-12 13:28:27 +03:00
|
|
|
|
|
|
|
/* Handle maps */
|
2022-01-18 14:56:31 +03:00
|
|
|
if (!memory_region_is_mapped(&phb->mmbar0) &&
|
2022-01-12 13:28:27 +03:00
|
|
|
(bar_en & PEC_NEST_STK_BAR_EN_MMIO0)) {
|
2022-01-18 14:56:31 +03:00
|
|
|
bar = phb->nest_regs[PEC_NEST_STK_MMIO_BAR0] >> 8;
|
|
|
|
mask = phb->nest_regs[PEC_NEST_STK_MMIO_BAR0_MASK];
|
2022-01-12 13:28:27 +03:00
|
|
|
size = ((~mask) >> 8) + 1;
|
2022-01-18 14:56:31 +03:00
|
|
|
snprintf(name, sizeof(name), "pec-%d.%d-phb-%d-mmio0",
|
2022-01-18 14:56:31 +03:00
|
|
|
pec->chip_id, pec->index, stack_no);
|
2022-01-18 14:56:31 +03:00
|
|
|
memory_region_init(&phb->mmbar0, OBJECT(phb), name, size);
|
|
|
|
memory_region_add_subregion(sysmem, bar, &phb->mmbar0);
|
|
|
|
phb->mmio0_base = bar;
|
|
|
|
phb->mmio0_size = size;
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
2022-01-18 14:56:31 +03:00
|
|
|
if (!memory_region_is_mapped(&phb->mmbar1) &&
|
2022-01-12 13:28:27 +03:00
|
|
|
(bar_en & PEC_NEST_STK_BAR_EN_MMIO1)) {
|
2022-01-18 14:56:31 +03:00
|
|
|
bar = phb->nest_regs[PEC_NEST_STK_MMIO_BAR1] >> 8;
|
|
|
|
mask = phb->nest_regs[PEC_NEST_STK_MMIO_BAR1_MASK];
|
2022-01-12 13:28:27 +03:00
|
|
|
size = ((~mask) >> 8) + 1;
|
2022-01-18 14:56:31 +03:00
|
|
|
snprintf(name, sizeof(name), "pec-%d.%d-phb-%d-mmio1",
|
2022-01-18 14:56:31 +03:00
|
|
|
pec->chip_id, pec->index, stack_no);
|
2022-01-18 14:56:31 +03:00
|
|
|
memory_region_init(&phb->mmbar1, OBJECT(phb), name, size);
|
|
|
|
memory_region_add_subregion(sysmem, bar, &phb->mmbar1);
|
|
|
|
phb->mmio1_base = bar;
|
|
|
|
phb->mmio1_size = size;
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
2022-01-18 14:56:30 +03:00
|
|
|
if (!memory_region_is_mapped(&phb->phbbar) &&
|
2022-01-12 13:28:27 +03:00
|
|
|
(bar_en & PEC_NEST_STK_BAR_EN_PHB)) {
|
2022-01-18 14:56:31 +03:00
|
|
|
bar = phb->nest_regs[PEC_NEST_STK_PHB_REGS_BAR] >> 8;
|
2022-01-12 13:28:27 +03:00
|
|
|
size = PNV_PHB4_NUM_REGS << 3;
|
2022-01-18 14:56:30 +03:00
|
|
|
snprintf(name, sizeof(name), "pec-%d.%d-phb-%d",
|
2022-01-18 14:56:31 +03:00
|
|
|
pec->chip_id, pec->index, stack_no);
|
2022-01-18 14:56:30 +03:00
|
|
|
memory_region_init(&phb->phbbar, OBJECT(phb), name, size);
|
|
|
|
memory_region_add_subregion(sysmem, bar, &phb->phbbar);
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
2022-01-18 14:56:30 +03:00
|
|
|
if (!memory_region_is_mapped(&phb->intbar) &&
|
2022-01-12 13:28:27 +03:00
|
|
|
(bar_en & PEC_NEST_STK_BAR_EN_INT)) {
|
2022-01-18 14:56:31 +03:00
|
|
|
bar = phb->nest_regs[PEC_NEST_STK_INT_BAR] >> 8;
|
2022-01-12 13:28:27 +03:00
|
|
|
size = PNV_PHB4_MAX_INTs << 16;
|
2022-01-18 14:56:30 +03:00
|
|
|
snprintf(name, sizeof(name), "pec-%d.%d-phb-%d-int",
|
2022-01-18 14:56:31 +03:00
|
|
|
phb->pec->chip_id, phb->pec->index, stack_no);
|
2022-01-18 14:56:30 +03:00
|
|
|
memory_region_init(&phb->intbar, OBJECT(phb), name, size);
|
|
|
|
memory_region_add_subregion(sysmem, bar, &phb->intbar);
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Update PHB */
|
2022-01-18 14:56:31 +03:00
|
|
|
pnv_phb4_update_regions(phb);
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
static void pnv_pec_stk_nest_xscom_write(void *opaque, hwaddr addr,
|
|
|
|
uint64_t val, unsigned size)
|
|
|
|
{
|
2022-01-18 14:56:31 +03:00
|
|
|
PnvPHB4 *phb = PNV_PHB4(opaque);
|
2022-01-18 14:56:31 +03:00
|
|
|
PnvPhb4PecState *pec = phb->pec;
|
2022-01-12 13:28:27 +03:00
|
|
|
uint32_t reg = addr >> 3;
|
|
|
|
|
|
|
|
switch (reg) {
|
|
|
|
case PEC_NEST_STK_PCI_NEST_FIR:
|
2022-01-18 14:56:31 +03:00
|
|
|
phb->nest_regs[PEC_NEST_STK_PCI_NEST_FIR] = val;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_NEST_STK_PCI_NEST_FIR_CLR:
|
2022-01-18 14:56:31 +03:00
|
|
|
phb->nest_regs[PEC_NEST_STK_PCI_NEST_FIR] &= val;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_NEST_STK_PCI_NEST_FIR_SET:
|
2022-01-18 14:56:31 +03:00
|
|
|
phb->nest_regs[PEC_NEST_STK_PCI_NEST_FIR] |= val;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_NEST_STK_PCI_NEST_FIR_MSK:
|
2022-01-18 14:56:31 +03:00
|
|
|
phb->nest_regs[PEC_NEST_STK_PCI_NEST_FIR_MSK] = val;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_NEST_STK_PCI_NEST_FIR_MSKC:
|
2022-01-18 14:56:31 +03:00
|
|
|
phb->nest_regs[PEC_NEST_STK_PCI_NEST_FIR_MSK] &= val;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_NEST_STK_PCI_NEST_FIR_MSKS:
|
2022-01-18 14:56:31 +03:00
|
|
|
phb->nest_regs[PEC_NEST_STK_PCI_NEST_FIR_MSK] |= val;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_NEST_STK_PCI_NEST_FIR_ACT0:
|
|
|
|
case PEC_NEST_STK_PCI_NEST_FIR_ACT1:
|
2022-01-18 14:56:31 +03:00
|
|
|
phb->nest_regs[reg] = val;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_NEST_STK_PCI_NEST_FIR_WOF:
|
2022-01-18 14:56:31 +03:00
|
|
|
phb->nest_regs[reg] = 0;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_NEST_STK_ERR_REPORT_0:
|
|
|
|
case PEC_NEST_STK_ERR_REPORT_1:
|
|
|
|
case PEC_NEST_STK_PBCQ_GNRL_STATUS:
|
|
|
|
/* Flag error ? */
|
|
|
|
break;
|
|
|
|
case PEC_NEST_STK_PBCQ_MODE:
|
2022-01-18 14:56:31 +03:00
|
|
|
phb->nest_regs[reg] = val & 0xff00000000000000ull;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_NEST_STK_MMIO_BAR0:
|
|
|
|
case PEC_NEST_STK_MMIO_BAR0_MASK:
|
|
|
|
case PEC_NEST_STK_MMIO_BAR1:
|
|
|
|
case PEC_NEST_STK_MMIO_BAR1_MASK:
|
2022-01-18 14:56:31 +03:00
|
|
|
if (phb->nest_regs[PEC_NEST_STK_BAR_EN] &
|
2022-01-12 13:28:27 +03:00
|
|
|
(PEC_NEST_STK_BAR_EN_MMIO0 |
|
|
|
|
PEC_NEST_STK_BAR_EN_MMIO1)) {
|
2023-06-20 02:36:36 +03:00
|
|
|
phb_pec_error(pec, "Changing enabled BAR unsupported");
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
2022-01-18 14:56:31 +03:00
|
|
|
phb->nest_regs[reg] = val & 0xffffffffff000000ull;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_NEST_STK_PHB_REGS_BAR:
|
2022-01-18 14:56:31 +03:00
|
|
|
if (phb->nest_regs[PEC_NEST_STK_BAR_EN] & PEC_NEST_STK_BAR_EN_PHB) {
|
2023-06-20 02:36:36 +03:00
|
|
|
phb_pec_error(pec, "Changing enabled BAR unsupported");
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
2022-01-18 14:56:31 +03:00
|
|
|
phb->nest_regs[reg] = val & 0xffffffffffc00000ull;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_NEST_STK_INT_BAR:
|
2022-01-18 14:56:31 +03:00
|
|
|
if (phb->nest_regs[PEC_NEST_STK_BAR_EN] & PEC_NEST_STK_BAR_EN_INT) {
|
2023-06-20 02:36:36 +03:00
|
|
|
phb_pec_error(pec, "Changing enabled BAR unsupported");
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
2022-01-18 14:56:31 +03:00
|
|
|
phb->nest_regs[reg] = val & 0xfffffff000000000ull;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_NEST_STK_BAR_EN:
|
2022-01-18 14:56:31 +03:00
|
|
|
phb->nest_regs[reg] = val & 0xf000000000000000ull;
|
2022-01-18 14:56:31 +03:00
|
|
|
pnv_pec_phb_update_map(phb);
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_NEST_STK_DATA_FRZ_TYPE:
|
|
|
|
case PEC_NEST_STK_PBCQ_TUN_BAR:
|
|
|
|
/* Not used for now */
|
2022-01-18 14:56:31 +03:00
|
|
|
phb->nest_regs[reg] = val;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
default:
|
|
|
|
qemu_log_mask(LOG_UNIMP, "phb4_pec: nest_xscom_write 0x%"HWADDR_PRIx
|
|
|
|
"=%"PRIx64"\n", addr, val);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static const MemoryRegionOps pnv_pec_stk_nest_xscom_ops = {
|
|
|
|
.read = pnv_pec_stk_nest_xscom_read,
|
|
|
|
.write = pnv_pec_stk_nest_xscom_write,
|
|
|
|
.valid.min_access_size = 8,
|
|
|
|
.valid.max_access_size = 8,
|
|
|
|
.impl.min_access_size = 8,
|
|
|
|
.impl.max_access_size = 8,
|
|
|
|
.endianness = DEVICE_BIG_ENDIAN,
|
|
|
|
};
|
|
|
|
|
|
|
|
static uint64_t pnv_pec_stk_pci_xscom_read(void *opaque, hwaddr addr,
|
|
|
|
unsigned size)
|
|
|
|
{
|
2022-01-18 14:56:30 +03:00
|
|
|
PnvPHB4 *phb = PNV_PHB4(opaque);
|
2022-01-12 13:28:27 +03:00
|
|
|
uint32_t reg = addr >> 3;
|
|
|
|
|
|
|
|
/* TODO: add list of allowed registers and error out if not */
|
2022-01-18 14:56:30 +03:00
|
|
|
return phb->pci_regs[reg];
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
static void pnv_pec_stk_pci_xscom_write(void *opaque, hwaddr addr,
|
|
|
|
uint64_t val, unsigned size)
|
|
|
|
{
|
2022-01-18 14:56:30 +03:00
|
|
|
PnvPHB4 *phb = PNV_PHB4(opaque);
|
2022-01-12 13:28:27 +03:00
|
|
|
uint32_t reg = addr >> 3;
|
|
|
|
|
|
|
|
switch (reg) {
|
|
|
|
case PEC_PCI_STK_PCI_FIR:
|
2022-01-18 14:56:30 +03:00
|
|
|
phb->pci_regs[reg] = val;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_PCI_STK_PCI_FIR_CLR:
|
2022-01-18 14:56:30 +03:00
|
|
|
phb->pci_regs[PEC_PCI_STK_PCI_FIR] &= val;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_PCI_STK_PCI_FIR_SET:
|
2022-01-18 14:56:30 +03:00
|
|
|
phb->pci_regs[PEC_PCI_STK_PCI_FIR] |= val;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_PCI_STK_PCI_FIR_MSK:
|
2022-01-18 14:56:30 +03:00
|
|
|
phb->pci_regs[reg] = val;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_PCI_STK_PCI_FIR_MSKC:
|
2022-01-18 14:56:30 +03:00
|
|
|
phb->pci_regs[PEC_PCI_STK_PCI_FIR_MSK] &= val;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_PCI_STK_PCI_FIR_MSKS:
|
2022-01-18 14:56:30 +03:00
|
|
|
phb->pci_regs[PEC_PCI_STK_PCI_FIR_MSK] |= val;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_PCI_STK_PCI_FIR_ACT0:
|
|
|
|
case PEC_PCI_STK_PCI_FIR_ACT1:
|
2022-01-18 14:56:30 +03:00
|
|
|
phb->pci_regs[reg] = val;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_PCI_STK_PCI_FIR_WOF:
|
2022-01-18 14:56:30 +03:00
|
|
|
phb->pci_regs[reg] = 0;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
case PEC_PCI_STK_ETU_RESET:
|
2022-01-18 14:56:30 +03:00
|
|
|
phb->pci_regs[reg] = val & 0x8000000000000000ull;
|
2022-01-12 13:28:27 +03:00
|
|
|
/* TODO: Implement reset */
|
|
|
|
break;
|
|
|
|
case PEC_PCI_STK_PBAIB_ERR_REPORT:
|
|
|
|
break;
|
|
|
|
case PEC_PCI_STK_PBAIB_TX_CMD_CRED:
|
|
|
|
case PEC_PCI_STK_PBAIB_TX_DAT_CRED:
|
2022-01-18 14:56:30 +03:00
|
|
|
phb->pci_regs[reg] = val;
|
2022-01-12 13:28:27 +03:00
|
|
|
break;
|
|
|
|
default:
|
|
|
|
qemu_log_mask(LOG_UNIMP, "phb4_pec_stk: pci_xscom_write 0x%"HWADDR_PRIx
|
|
|
|
"=%"PRIx64"\n", addr, val);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static const MemoryRegionOps pnv_pec_stk_pci_xscom_ops = {
|
|
|
|
.read = pnv_pec_stk_pci_xscom_read,
|
|
|
|
.write = pnv_pec_stk_pci_xscom_write,
|
|
|
|
.valid.min_access_size = 8,
|
|
|
|
.valid.max_access_size = 8,
|
|
|
|
.impl.min_access_size = 8,
|
|
|
|
.impl.max_access_size = 8,
|
|
|
|
.endianness = DEVICE_BIG_ENDIAN,
|
|
|
|
};
|
|
|
|
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
static int pnv_phb4_map_irq(PCIDevice *pci_dev, int irq_num)
|
|
|
|
{
|
|
|
|
/* Check that out properly ... */
|
|
|
|
return irq_num & 3;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void pnv_phb4_set_irq(void *opaque, int irq_num, int level)
|
|
|
|
{
|
|
|
|
PnvPHB4 *phb = PNV_PHB4(opaque);
|
|
|
|
uint32_t lsi_base;
|
|
|
|
|
|
|
|
/* LSI only ... */
|
|
|
|
if (irq_num > 3) {
|
|
|
|
phb_error(phb, "IRQ %x is not an LSI", irq_num);
|
|
|
|
}
|
|
|
|
lsi_base = GETFIELD(PHB_LSI_SRC_ID, phb->regs[PHB_LSI_SOURCE_ID >> 3]);
|
|
|
|
lsi_base <<= 3;
|
|
|
|
qemu_set_irq(phb->qirqs[lsi_base + irq_num], level);
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool pnv_phb4_resolve_pe(PnvPhb4DMASpace *ds)
|
|
|
|
{
|
|
|
|
uint64_t rtt, addr;
|
|
|
|
uint16_t rte;
|
|
|
|
int bus_num;
|
|
|
|
int num_PEs;
|
|
|
|
|
|
|
|
/* Already resolved ? */
|
|
|
|
if (ds->pe_num != PHB_INVALID_PE) {
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* We need to lookup the RTT */
|
|
|
|
rtt = ds->phb->regs[PHB_RTT_BAR >> 3];
|
|
|
|
if (!(rtt & PHB_RTT_BAR_ENABLE)) {
|
|
|
|
phb_error(ds->phb, "DMA with RTT BAR disabled !");
|
|
|
|
/* Set error bits ? fence ? ... */
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Read RTE */
|
|
|
|
bus_num = pci_bus_num(ds->bus);
|
|
|
|
addr = rtt & PHB_RTT_BASE_ADDRESS_MASK;
|
2020-10-11 18:18:59 +03:00
|
|
|
addr += 2 * PCI_BUILD_BDF(bus_num, ds->devfn);
|
dma: Let dma_memory_read/write() take MemTxAttrs argument
Let devices specify transaction attributes when calling
dma_memory_read() or dma_memory_write().
Patch created mechanically using spatch with this script:
@@
expression E1, E2, E3, E4;
@@
(
- dma_memory_read(E1, E2, E3, E4)
+ dma_memory_read(E1, E2, E3, E4, MEMTXATTRS_UNSPECIFIED)
|
- dma_memory_write(E1, E2, E3, E4)
+ dma_memory_write(E1, E2, E3, E4, MEMTXATTRS_UNSPECIFIED)
)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Li Qiang <liq3ea@gmail.com>
Reviewed-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Acked-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20211223115554.3155328-6-philmd@redhat.com>
2020-09-03 11:08:29 +03:00
|
|
|
if (dma_memory_read(&address_space_memory, addr, &rte,
|
|
|
|
sizeof(rte), MEMTXATTRS_UNSPECIFIED)) {
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
phb_error(ds->phb, "Failed to read RTT entry at 0x%"PRIx64, addr);
|
|
|
|
/* Set error bits ? fence ? ... */
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
rte = be16_to_cpu(rte);
|
|
|
|
|
|
|
|
/* Fail upon reading of invalid PE# */
|
|
|
|
num_PEs = ds->phb->big_phb ? PNV_PHB4_MAX_PEs : (PNV_PHB4_MAX_PEs >> 1);
|
|
|
|
if (rte >= num_PEs) {
|
|
|
|
phb_error(ds->phb, "RTE for RID 0x%x invalid (%04x", ds->devfn, rte);
|
|
|
|
rte &= num_PEs - 1;
|
|
|
|
}
|
|
|
|
ds->pe_num = rte;
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void pnv_phb4_translate_tve(PnvPhb4DMASpace *ds, hwaddr addr,
|
|
|
|
bool is_write, uint64_t tve,
|
|
|
|
IOMMUTLBEntry *tlb)
|
|
|
|
{
|
|
|
|
uint64_t tta = GETFIELD(IODA3_TVT_TABLE_ADDR, tve);
|
|
|
|
int32_t lev = GETFIELD(IODA3_TVT_NUM_LEVELS, tve);
|
|
|
|
uint32_t tts = GETFIELD(IODA3_TVT_TCE_TABLE_SIZE, tve);
|
|
|
|
uint32_t tps = GETFIELD(IODA3_TVT_IO_PSIZE, tve);
|
|
|
|
|
|
|
|
/* Invalid levels */
|
|
|
|
if (lev > 4) {
|
|
|
|
phb_error(ds->phb, "Invalid #levels in TVE %d", lev);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Invalid entry */
|
|
|
|
if (tts == 0) {
|
|
|
|
phb_error(ds->phb, "Access to invalid TVE");
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* IO Page Size of 0 means untranslated, else use TCEs */
|
|
|
|
if (tps == 0) {
|
|
|
|
/* TODO: Handle boundaries */
|
|
|
|
|
|
|
|
/* Use 4k pages like q35 ... for now */
|
|
|
|
tlb->iova = addr & 0xfffffffffffff000ull;
|
|
|
|
tlb->translated_addr = addr & 0x0003fffffffff000ull;
|
|
|
|
tlb->addr_mask = 0xfffull;
|
|
|
|
tlb->perm = IOMMU_RW;
|
|
|
|
} else {
|
|
|
|
uint32_t tce_shift, tbl_shift, sh;
|
|
|
|
uint64_t base, taddr, tce, tce_mask;
|
|
|
|
|
|
|
|
/* Address bits per bottom level TCE entry */
|
|
|
|
tce_shift = tps + 11;
|
|
|
|
|
|
|
|
/* Address bits per table level */
|
|
|
|
tbl_shift = tts + 8;
|
|
|
|
|
|
|
|
/* Top level table base address */
|
|
|
|
base = tta << 12;
|
|
|
|
|
|
|
|
/* Total shift to first level */
|
|
|
|
sh = tbl_shift * lev + tce_shift;
|
|
|
|
|
|
|
|
/* TODO: Limit to support IO page sizes */
|
|
|
|
|
|
|
|
/* TODO: Multi-level untested */
|
2022-01-28 15:15:02 +03:00
|
|
|
do {
|
|
|
|
lev--;
|
|
|
|
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
/* Grab the TCE address */
|
|
|
|
taddr = base | (((addr >> sh) & ((1ul << tbl_shift) - 1)) << 3);
|
|
|
|
if (dma_memory_read(&address_space_memory, taddr, &tce,
|
dma: Let dma_memory_read/write() take MemTxAttrs argument
Let devices specify transaction attributes when calling
dma_memory_read() or dma_memory_write().
Patch created mechanically using spatch with this script:
@@
expression E1, E2, E3, E4;
@@
(
- dma_memory_read(E1, E2, E3, E4)
+ dma_memory_read(E1, E2, E3, E4, MEMTXATTRS_UNSPECIFIED)
|
- dma_memory_write(E1, E2, E3, E4)
+ dma_memory_write(E1, E2, E3, E4, MEMTXATTRS_UNSPECIFIED)
)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Li Qiang <liq3ea@gmail.com>
Reviewed-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Acked-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20211223115554.3155328-6-philmd@redhat.com>
2020-09-03 11:08:29 +03:00
|
|
|
sizeof(tce), MEMTXATTRS_UNSPECIFIED)) {
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
phb_error(ds->phb, "Failed to read TCE at 0x%"PRIx64, taddr);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
tce = be64_to_cpu(tce);
|
|
|
|
|
|
|
|
/* Check permission for indirect TCE */
|
|
|
|
if ((lev >= 0) && !(tce & 3)) {
|
|
|
|
phb_error(ds->phb, "Invalid indirect TCE at 0x%"PRIx64, taddr);
|
|
|
|
phb_error(ds->phb, " xlate %"PRIx64":%c TVE=%"PRIx64, addr,
|
|
|
|
is_write ? 'W' : 'R', tve);
|
|
|
|
phb_error(ds->phb, " tta=%"PRIx64" lev=%d tts=%d tps=%d",
|
|
|
|
tta, lev, tts, tps);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
sh -= tbl_shift;
|
|
|
|
base = tce & ~0xfffull;
|
2022-01-28 15:15:02 +03:00
|
|
|
} while (lev >= 0);
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
|
|
|
|
/* We exit the loop with TCE being the final TCE */
|
|
|
|
if ((is_write & !(tce & 2)) || ((!is_write) && !(tce & 1))) {
|
|
|
|
phb_error(ds->phb, "TCE access fault at 0x%"PRIx64, taddr);
|
|
|
|
phb_error(ds->phb, " xlate %"PRIx64":%c TVE=%"PRIx64, addr,
|
|
|
|
is_write ? 'W' : 'R', tve);
|
|
|
|
phb_error(ds->phb, " tta=%"PRIx64" lev=%d tts=%d tps=%d",
|
|
|
|
tta, lev, tts, tps);
|
2022-01-28 15:15:02 +03:00
|
|
|
return;
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
}
|
2022-01-28 15:15:02 +03:00
|
|
|
tce_mask = ~((1ull << tce_shift) - 1);
|
|
|
|
tlb->iova = addr & tce_mask;
|
|
|
|
tlb->translated_addr = tce & tce_mask;
|
|
|
|
tlb->addr_mask = ~tce_mask;
|
|
|
|
tlb->perm = tce & 3;
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static IOMMUTLBEntry pnv_phb4_translate_iommu(IOMMUMemoryRegion *iommu,
|
|
|
|
hwaddr addr,
|
|
|
|
IOMMUAccessFlags flag,
|
|
|
|
int iommu_idx)
|
|
|
|
{
|
|
|
|
PnvPhb4DMASpace *ds = container_of(iommu, PnvPhb4DMASpace, dma_mr);
|
|
|
|
int tve_sel;
|
|
|
|
uint64_t tve, cfg;
|
|
|
|
IOMMUTLBEntry ret = {
|
|
|
|
.target_as = &address_space_memory,
|
|
|
|
.iova = addr,
|
|
|
|
.translated_addr = 0,
|
|
|
|
.addr_mask = ~(hwaddr)0,
|
|
|
|
.perm = IOMMU_NONE,
|
|
|
|
};
|
|
|
|
|
|
|
|
/* Resolve PE# */
|
|
|
|
if (!pnv_phb4_resolve_pe(ds)) {
|
|
|
|
phb_error(ds->phb, "Failed to resolve PE# for bus @%p (%d) devfn 0x%x",
|
|
|
|
ds->bus, pci_bus_num(ds->bus), ds->devfn);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Check top bits */
|
|
|
|
switch (addr >> 60) {
|
|
|
|
case 00:
|
|
|
|
/* DMA or 32-bit MSI ? */
|
|
|
|
cfg = ds->phb->regs[PHB_PHB4_CONFIG >> 3];
|
|
|
|
if ((cfg & PHB_PHB4C_32BIT_MSI_EN) &&
|
|
|
|
((addr & 0xffffffffffff0000ull) == 0xffff0000ull)) {
|
|
|
|
phb_error(ds->phb, "xlate on 32-bit MSI region");
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
/* Choose TVE XXX Use PHB4 Control Register */
|
|
|
|
tve_sel = (addr >> 59) & 1;
|
|
|
|
tve = ds->phb->ioda_TVT[ds->pe_num * 2 + tve_sel];
|
|
|
|
pnv_phb4_translate_tve(ds, addr, flag & IOMMU_WO, tve, &ret);
|
|
|
|
break;
|
|
|
|
case 01:
|
|
|
|
phb_error(ds->phb, "xlate on 64-bit MSI region");
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
phb_error(ds->phb, "xlate on unsupported address 0x%"PRIx64, addr);
|
|
|
|
}
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
#define TYPE_PNV_PHB4_IOMMU_MEMORY_REGION "pnv-phb4-iommu-memory-region"
|
2020-09-01 00:07:33 +03:00
|
|
|
DECLARE_INSTANCE_CHECKER(IOMMUMemoryRegion, PNV_PHB4_IOMMU_MEMORY_REGION,
|
|
|
|
TYPE_PNV_PHB4_IOMMU_MEMORY_REGION)
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
|
|
|
|
static void pnv_phb4_iommu_memory_region_class_init(ObjectClass *klass,
|
|
|
|
void *data)
|
|
|
|
{
|
|
|
|
IOMMUMemoryRegionClass *imrc = IOMMU_MEMORY_REGION_CLASS(klass);
|
|
|
|
|
|
|
|
imrc->translate = pnv_phb4_translate_iommu;
|
|
|
|
}
|
|
|
|
|
|
|
|
static const TypeInfo pnv_phb4_iommu_memory_region_info = {
|
|
|
|
.parent = TYPE_IOMMU_MEMORY_REGION,
|
|
|
|
.name = TYPE_PNV_PHB4_IOMMU_MEMORY_REGION,
|
|
|
|
.class_init = pnv_phb4_iommu_memory_region_class_init,
|
|
|
|
};
|
|
|
|
|
2022-01-12 13:28:27 +03:00
|
|
|
/*
|
|
|
|
* Return the index/phb-id of a PHB4 that belongs to a
|
|
|
|
* pec->stacks[stack_index] stack.
|
|
|
|
*/
|
|
|
|
int pnv_phb4_pec_get_phb_id(PnvPhb4PecState *pec, int stack_index)
|
|
|
|
{
|
|
|
|
PnvPhb4PecClass *pecc = PNV_PHB4_PEC_GET_CLASS(pec);
|
|
|
|
int index = pec->index;
|
|
|
|
int offset = 0;
|
|
|
|
|
|
|
|
while (index--) {
|
2022-01-18 14:56:31 +03:00
|
|
|
offset += pecc->num_phbs[index];
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
return offset + stack_index;
|
|
|
|
}
|
|
|
|
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
/*
|
|
|
|
* MSI/MSIX memory region implementation.
|
|
|
|
* The handler handles both MSI and MSIX.
|
|
|
|
*/
|
|
|
|
static void pnv_phb4_msi_write(void *opaque, hwaddr addr,
|
|
|
|
uint64_t data, unsigned size)
|
|
|
|
{
|
|
|
|
PnvPhb4DMASpace *ds = opaque;
|
|
|
|
PnvPHB4 *phb = ds->phb;
|
|
|
|
|
|
|
|
uint32_t src = ((addr >> 4) & 0xffff) | (data & 0x1f);
|
|
|
|
|
|
|
|
/* Resolve PE# */
|
|
|
|
if (!pnv_phb4_resolve_pe(ds)) {
|
|
|
|
phb_error(phb, "Failed to resolve PE# for bus @%p (%d) devfn 0x%x",
|
|
|
|
ds->bus, pci_bus_num(ds->bus), ds->devfn);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* TODO: Check it doesn't collide with LSIs */
|
|
|
|
if (src >= phb->xsrc.nr_irqs) {
|
|
|
|
phb_error(phb, "MSI %d out of bounds", src);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2023-07-14 14:27:04 +03:00
|
|
|
/* TODO: check PE/MSI assignment */
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
|
|
|
|
qemu_irq_pulse(phb->qirqs[src]);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* There is no .read as the read result is undefined by PCI spec */
|
|
|
|
static uint64_t pnv_phb4_msi_read(void *opaque, hwaddr addr, unsigned size)
|
|
|
|
{
|
|
|
|
PnvPhb4DMASpace *ds = opaque;
|
|
|
|
|
|
|
|
phb_error(ds->phb, "Invalid MSI read @ 0x%" HWADDR_PRIx, addr);
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
|
|
|
static const MemoryRegionOps pnv_phb4_msi_ops = {
|
|
|
|
.read = pnv_phb4_msi_read,
|
|
|
|
.write = pnv_phb4_msi_write,
|
|
|
|
.endianness = DEVICE_LITTLE_ENDIAN
|
|
|
|
};
|
|
|
|
|
|
|
|
static PnvPhb4DMASpace *pnv_phb4_dma_find(PnvPHB4 *phb, PCIBus *bus, int devfn)
|
|
|
|
{
|
|
|
|
PnvPhb4DMASpace *ds;
|
|
|
|
|
|
|
|
QLIST_FOREACH(ds, &phb->dma_spaces, list) {
|
|
|
|
if (ds->bus == bus && ds->devfn == devfn) {
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return ds;
|
|
|
|
}
|
|
|
|
|
|
|
|
static AddressSpace *pnv_phb4_dma_iommu(PCIBus *bus, void *opaque, int devfn)
|
|
|
|
{
|
|
|
|
PnvPHB4 *phb = opaque;
|
|
|
|
PnvPhb4DMASpace *ds;
|
|
|
|
char name[32];
|
|
|
|
|
|
|
|
ds = pnv_phb4_dma_find(phb, bus, devfn);
|
|
|
|
|
|
|
|
if (ds == NULL) {
|
2022-03-15 17:41:56 +03:00
|
|
|
ds = g_new0(PnvPhb4DMASpace, 1);
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
ds->bus = bus;
|
|
|
|
ds->devfn = devfn;
|
|
|
|
ds->pe_num = PHB_INVALID_PE;
|
|
|
|
ds->phb = phb;
|
|
|
|
snprintf(name, sizeof(name), "phb4-%d.%d-iommu", phb->chip_id,
|
|
|
|
phb->phb_id);
|
|
|
|
memory_region_init_iommu(&ds->dma_mr, sizeof(ds->dma_mr),
|
|
|
|
TYPE_PNV_PHB4_IOMMU_MEMORY_REGION,
|
|
|
|
OBJECT(phb), name, UINT64_MAX);
|
|
|
|
address_space_init(&ds->dma_as, MEMORY_REGION(&ds->dma_mr),
|
|
|
|
name);
|
|
|
|
memory_region_init_io(&ds->msi32_mr, OBJECT(phb), &pnv_phb4_msi_ops,
|
|
|
|
ds, "msi32", 0x10000);
|
|
|
|
memory_region_init_io(&ds->msi64_mr, OBJECT(phb), &pnv_phb4_msi_ops,
|
|
|
|
ds, "msi64", 0x100000);
|
|
|
|
pnv_phb4_update_msi_regions(ds);
|
|
|
|
|
|
|
|
QLIST_INSERT_HEAD(&phb->dma_spaces, ds, list);
|
|
|
|
}
|
|
|
|
return &ds->dma_as;
|
|
|
|
}
|
|
|
|
|
2022-01-12 13:28:27 +03:00
|
|
|
static void pnv_phb4_xscom_realize(PnvPHB4 *phb)
|
|
|
|
{
|
2022-01-18 14:56:31 +03:00
|
|
|
PnvPhb4PecState *pec = phb->pec;
|
2022-01-12 13:28:27 +03:00
|
|
|
PnvPhb4PecClass *pecc = PNV_PHB4_PEC_GET_CLASS(pec);
|
2022-01-18 14:56:31 +03:00
|
|
|
int stack_no = pnv_phb4_get_phb_stack_no(phb);
|
2022-01-12 13:28:27 +03:00
|
|
|
uint32_t pec_nest_base;
|
|
|
|
uint32_t pec_pci_base;
|
|
|
|
char name[64];
|
|
|
|
|
|
|
|
assert(pec);
|
|
|
|
|
|
|
|
/* Initialize the XSCOM regions for the stack registers */
|
2022-01-18 14:56:31 +03:00
|
|
|
snprintf(name, sizeof(name), "xscom-pec-%d.%d-nest-phb-%d",
|
2022-01-18 14:56:31 +03:00
|
|
|
pec->chip_id, pec->index, stack_no);
|
2022-01-18 14:56:31 +03:00
|
|
|
pnv_xscom_region_init(&phb->nest_regs_mr, OBJECT(phb),
|
|
|
|
&pnv_pec_stk_nest_xscom_ops, phb, name,
|
2022-01-12 13:28:27 +03:00
|
|
|
PHB4_PEC_NEST_STK_REGS_COUNT);
|
|
|
|
|
2022-01-18 14:56:30 +03:00
|
|
|
snprintf(name, sizeof(name), "xscom-pec-%d.%d-pci-phb-%d",
|
2022-01-18 14:56:31 +03:00
|
|
|
pec->chip_id, pec->index, stack_no);
|
2022-01-18 14:56:30 +03:00
|
|
|
pnv_xscom_region_init(&phb->pci_regs_mr, OBJECT(phb),
|
2022-01-18 14:56:30 +03:00
|
|
|
&pnv_pec_stk_pci_xscom_ops, phb, name,
|
2022-01-12 13:28:27 +03:00
|
|
|
PHB4_PEC_PCI_STK_REGS_COUNT);
|
|
|
|
|
|
|
|
/* PHB pass-through */
|
2023-01-27 15:28:48 +03:00
|
|
|
snprintf(name, sizeof(name), "xscom-pec-%d.%d-phb-%d",
|
2022-01-18 14:56:31 +03:00
|
|
|
pec->chip_id, pec->index, stack_no);
|
2022-01-18 14:56:31 +03:00
|
|
|
pnv_xscom_region_init(&phb->phb_regs_mr, OBJECT(phb),
|
2022-01-12 13:28:27 +03:00
|
|
|
&pnv_phb4_xscom_ops, phb, name, 0x40);
|
|
|
|
|
|
|
|
pec_nest_base = pecc->xscom_nest_base(pec);
|
|
|
|
pec_pci_base = pecc->xscom_pci_base(pec);
|
|
|
|
|
|
|
|
/* Populate the XSCOM address space. */
|
|
|
|
pnv_xscom_add_subregion(pec->chip,
|
2022-01-18 14:56:31 +03:00
|
|
|
pec_nest_base + 0x40 * (stack_no + 1),
|
2022-01-18 14:56:31 +03:00
|
|
|
&phb->nest_regs_mr);
|
2022-01-12 13:28:27 +03:00
|
|
|
pnv_xscom_add_subregion(pec->chip,
|
2022-01-18 14:56:31 +03:00
|
|
|
pec_pci_base + 0x40 * (stack_no + 1),
|
2022-01-18 14:56:30 +03:00
|
|
|
&phb->pci_regs_mr);
|
2022-01-12 13:28:27 +03:00
|
|
|
pnv_xscom_add_subregion(pec->chip,
|
|
|
|
pec_pci_base + PNV9_XSCOM_PEC_PCI_STK0 +
|
2022-01-18 14:56:31 +03:00
|
|
|
0x40 * stack_no,
|
2022-01-18 14:56:31 +03:00
|
|
|
&phb->phb_regs_mr);
|
2022-01-12 13:28:27 +03:00
|
|
|
}
|
|
|
|
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
static void pnv_phb4_instance_init(Object *obj)
|
|
|
|
{
|
|
|
|
PnvPHB4 *phb = PNV_PHB4(obj);
|
|
|
|
|
|
|
|
QLIST_INIT(&phb->dma_spaces);
|
|
|
|
|
|
|
|
/* XIVE interrupt source object */
|
qom: Less verbose object_initialize_child()
All users of object_initialize_child() pass the obvious child size
argument. Almost all pass &error_abort and no properties. Tiresome.
Rename object_initialize_child() to
object_initialize_child_with_props() to free the name. New
convenience wrapper object_initialize_child() automates the size
argument, and passes &error_abort and no properties.
Rename object_initialize_childv() to
object_initialize_child_with_propsv() for consistency.
Convert callers with this Coccinelle script:
@@
expression parent, propname, type;
expression child, size;
symbol error_abort;
@@
- object_initialize_child(parent, propname, OBJECT(child), size, type, &error_abort, NULL)
+ object_initialize_child(parent, propname, child, size, type, &error_abort, NULL)
@@
expression parent, propname, type;
expression child;
symbol error_abort;
@@
- object_initialize_child(parent, propname, child, sizeof(*child), type, &error_abort, NULL)
+ object_initialize_child(parent, propname, child, type)
@@
expression parent, propname, type;
expression child;
symbol error_abort;
@@
- object_initialize_child(parent, propname, &child, sizeof(child), type, &error_abort, NULL)
+ object_initialize_child(parent, propname, &child, type)
@@
expression parent, propname, type;
expression child, size, err;
expression list props;
@@
- object_initialize_child(parent, propname, child, size, type, err, props)
+ object_initialize_child_with_props(parent, propname, child, size, type, err, props)
Note that Coccinelle chokes on ARMSSE typedef vs. macro in
hw/arm/armsse.c. Worked around by temporarily renaming the macro for
the spatch run.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Acked-by: Alistair Francis <alistair.francis@wdc.com>
[Rebased: machine opentitan is new (commit fe0fe4735e7)]
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Message-Id: <20200610053247.1583243-37-armbru@redhat.com>
2020-06-10 08:32:25 +03:00
|
|
|
object_initialize_child(obj, "source", &phb->xsrc, TYPE_XIVE_SOURCE);
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
}
|
|
|
|
|
2022-06-24 11:49:13 +03:00
|
|
|
void pnv_phb4_bus_init(DeviceState *dev, PnvPHB4 *phb)
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
{
|
|
|
|
PCIHostState *pci = PCI_HOST_BRIDGE(dev);
|
|
|
|
char name[32];
|
|
|
|
|
|
|
|
/*
|
|
|
|
* PHB4 doesn't support IO space. However, qemu gets very upset if
|
|
|
|
* we don't have an IO region to anchor IO BARs onto so we just
|
|
|
|
* initialize one which we never hook up to anything
|
|
|
|
*/
|
|
|
|
snprintf(name, sizeof(name), "phb4-%d.%d-pci-io", phb->chip_id,
|
|
|
|
phb->phb_id);
|
|
|
|
memory_region_init(&phb->pci_io, OBJECT(phb), name, 0x10000);
|
|
|
|
|
|
|
|
snprintf(name, sizeof(name), "phb4-%d.%d-pci-mmio", phb->chip_id,
|
|
|
|
phb->phb_id);
|
|
|
|
memory_region_init(&phb->pci_mmio, OBJECT(phb), name,
|
|
|
|
PCI_MMIO_TOTAL_SIZE);
|
|
|
|
|
2022-06-24 11:49:13 +03:00
|
|
|
pci->bus = pci_register_root_bus(dev, dev->id ? dev->id : NULL,
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
pnv_phb4_set_irq, pnv_phb4_map_irq, phb,
|
|
|
|
&phb->pci_mmio, &phb->pci_io,
|
|
|
|
0, 4, TYPE_PNV_PHB4_ROOT_BUS);
|
2022-08-11 19:39:41 +03:00
|
|
|
|
|
|
|
object_property_set_int(OBJECT(pci->bus), "phb-id", phb->phb_id,
|
|
|
|
&error_abort);
|
|
|
|
object_property_set_int(OBJECT(pci->bus), "chip-id", phb->chip_id,
|
|
|
|
&error_abort);
|
|
|
|
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
pci_setup_iommu(pci->bus, pnv_phb4_dma_iommu, phb);
|
2021-12-17 19:57:13 +03:00
|
|
|
pci->bus->flags |= PCI_BUS_EXTENDED_CONFIG_SPACE;
|
2022-06-24 11:49:13 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
static void pnv_phb4_realize(DeviceState *dev, Error **errp)
|
|
|
|
{
|
|
|
|
PnvPHB4 *phb = PNV_PHB4(dev);
|
|
|
|
XiveSource *xsrc = &phb->xsrc;
|
|
|
|
int nr_irqs;
|
|
|
|
char name[32];
|
|
|
|
|
|
|
|
/* Set the "big_phb" flag */
|
|
|
|
phb->big_phb = phb->phb_id == 0 || phb->phb_id == 3;
|
|
|
|
|
|
|
|
/* Controller Registers */
|
|
|
|
snprintf(name, sizeof(name), "phb4-%d.%d-regs", phb->chip_id,
|
|
|
|
phb->phb_id);
|
|
|
|
memory_region_init_io(&phb->mr_regs, OBJECT(phb), &pnv_phb4_reg_ops, phb,
|
|
|
|
name, 0x2000);
|
|
|
|
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
/* Setup XIVE Source */
|
|
|
|
if (phb->big_phb) {
|
|
|
|
nr_irqs = PNV_PHB4_MAX_INTs;
|
|
|
|
} else {
|
|
|
|
nr_irqs = PNV_PHB4_MAX_INTs >> 1;
|
|
|
|
}
|
qom: Put name parameter before value / visitor parameter
The object_property_set_FOO() setters take property name and value in
an unusual order:
void object_property_set_FOO(Object *obj, FOO_TYPE value,
const char *name, Error **errp)
Having to pass value before name feels grating. Swap them.
Same for object_property_set(), object_property_get(), and
object_property_parse().
Convert callers with this Coccinelle script:
@@
identifier fun = {
object_property_get, object_property_parse, object_property_set_str,
object_property_set_link, object_property_set_bool,
object_property_set_int, object_property_set_uint, object_property_set,
object_property_set_qobject
};
expression obj, v, name, errp;
@@
- fun(obj, v, name, errp)
+ fun(obj, name, v, errp)
Chokes on hw/arm/musicpal.c's lcd_refresh() with the unhelpful error
message "no position information". Convert that one manually.
Fails to convert hw/arm/armsse.c, because Coccinelle gets confused by
ARMSSE being used both as typedef and function-like macro there.
Convert manually.
Fails to convert hw/rx/rx-gdbsim.c, because Coccinelle gets confused
by RXCPU being used both as typedef and function-like macro there.
Convert manually. The other files using RXCPU that way don't need
conversion.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Message-Id: <20200707160613.848843-27-armbru@redhat.com>
[Straightforwad conflict with commit 2336172d9b "audio: set default
value for pcspk.iobase property" resolved]
2020-07-07 19:05:54 +03:00
|
|
|
object_property_set_int(OBJECT(xsrc), "nr-irqs", nr_irqs, &error_fatal);
|
|
|
|
object_property_set_link(OBJECT(xsrc), "xive", OBJECT(phb), &error_fatal);
|
error: Eliminate error_propagate() with Coccinelle, part 1
When all we do with an Error we receive into a local variable is
propagating to somewhere else, we can just as well receive it there
right away. Convert
if (!foo(..., &err)) {
...
error_propagate(errp, err);
...
return ...
}
to
if (!foo(..., errp)) {
...
...
return ...
}
where nothing else needs @err. Coccinelle script:
@rule1 forall@
identifier fun, err, errp, lbl;
expression list args, args2;
binary operator op;
constant c1, c2;
symbol false;
@@
if (
(
- fun(args, &err, args2)
+ fun(args, errp, args2)
|
- !fun(args, &err, args2)
+ !fun(args, errp, args2)
|
- fun(args, &err, args2) op c1
+ fun(args, errp, args2) op c1
)
)
{
... when != err
when != lbl:
when strict
- error_propagate(errp, err);
... when != err
(
return;
|
return c2;
|
return false;
)
}
@rule2 forall@
identifier fun, err, errp, lbl;
expression list args, args2;
expression var;
binary operator op;
constant c1, c2;
symbol false;
@@
- var = fun(args, &err, args2);
+ var = fun(args, errp, args2);
... when != err
if (
(
var
|
!var
|
var op c1
)
)
{
... when != err
when != lbl:
when strict
- error_propagate(errp, err);
... when != err
(
return;
|
return c2;
|
return false;
|
return var;
)
}
@depends on rule1 || rule2@
identifier err;
@@
- Error *err = NULL;
... when != err
Not exactly elegant, I'm afraid.
The "when != lbl:" is necessary to avoid transforming
if (fun(args, &err)) {
goto out
}
...
out:
error_propagate(errp, err);
even though other paths to label out still need the error_propagate().
For an actual example, see sclp_realize().
Without the "when strict", Coccinelle transforms vfio_msix_setup(),
incorrectly. I don't know what exactly "when strict" does, only that
it helps here.
The match of return is narrower than what I want, but I can't figure
out how to express "return where the operand doesn't use @err". For
an example where it's too narrow, see vfio_intx_enable().
Silently fails to convert hw/arm/armsse.c, because Coccinelle gets
confused by ARMSSE being used both as typedef and function-like macro
there. Converted manually.
Line breaks tidied up manually. One nested declaration of @local_err
deleted manually. Preexisting unwanted blank line dropped in
hw/riscv/sifive_e.c.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Message-Id: <20200707160613.848843-35-armbru@redhat.com>
2020-07-07 19:06:02 +03:00
|
|
|
if (!qdev_realize(DEVICE(xsrc), NULL, errp)) {
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
pnv_phb4_update_xsrc(phb);
|
|
|
|
|
|
|
|
phb->qirqs = qemu_allocate_irqs(xive_source_set_irq, xsrc, xsrc->nr_irqs);
|
2022-01-12 13:28:27 +03:00
|
|
|
|
|
|
|
pnv_phb4_xscom_realize(phb);
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
}
|
|
|
|
|
2022-03-02 08:51:39 +03:00
|
|
|
/*
|
|
|
|
* Address base trigger mode (POWER10)
|
|
|
|
*
|
|
|
|
* Trigger directly the IC ESB page
|
|
|
|
*/
|
|
|
|
static void pnv_phb4_xive_notify_abt(PnvPHB4 *phb, uint32_t srcno,
|
|
|
|
bool pq_checked)
|
|
|
|
{
|
|
|
|
uint64_t notif_port = phb->regs[PHB_INT_NOTIFY_ADDR >> 3];
|
|
|
|
uint64_t data = 0; /* trigger data : don't care */
|
|
|
|
hwaddr addr;
|
|
|
|
MemTxResult result;
|
|
|
|
int esb_shift;
|
|
|
|
|
|
|
|
if (notif_port & PHB_INT_NOTIFY_ADDR_64K) {
|
|
|
|
esb_shift = 16;
|
|
|
|
} else {
|
|
|
|
esb_shift = 12;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Compute the address of the IC ESB management page */
|
|
|
|
addr = (notif_port & ~PHB_INT_NOTIFY_ADDR_64K);
|
|
|
|
addr |= (1ull << (esb_shift + 1)) * srcno;
|
|
|
|
addr |= (1ull << esb_shift);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* When the PQ state bits are checked on the PHB, the associated
|
|
|
|
* PQ state bits on the IC should be ignored. Use the unconditional
|
|
|
|
* trigger offset to inject a trigger on the IC. This is always
|
|
|
|
* the case for LSIs
|
|
|
|
*/
|
|
|
|
if (pq_checked) {
|
|
|
|
addr |= XIVE_ESB_INJECT;
|
|
|
|
}
|
|
|
|
|
|
|
|
trace_pnv_phb4_xive_notify_ic(addr, data);
|
|
|
|
|
|
|
|
address_space_stq_be(&address_space_memory, addr, data,
|
|
|
|
MEMTXATTRS_UNSPECIFIED, &result);
|
|
|
|
if (result != MEMTX_OK) {
|
|
|
|
phb_error(phb, "trigger failed @%"HWADDR_PRIx "\n", addr);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void pnv_phb4_xive_notify_ic(PnvPHB4 *phb, uint32_t srcno,
|
|
|
|
bool pq_checked)
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
{
|
|
|
|
uint64_t notif_port = phb->regs[PHB_INT_NOTIFY_ADDR >> 3];
|
|
|
|
uint32_t offset = phb->regs[PHB_INT_NOTIFY_INDEX >> 3];
|
2022-03-02 08:51:39 +03:00
|
|
|
uint64_t data = offset | srcno;
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
MemTxResult result;
|
|
|
|
|
2022-03-02 08:51:39 +03:00
|
|
|
if (pq_checked) {
|
|
|
|
data |= XIVE_TRIGGER_PQ;
|
|
|
|
}
|
|
|
|
|
2022-03-02 08:51:39 +03:00
|
|
|
trace_pnv_phb4_xive_notify_ic(notif_port, data);
|
2021-01-26 20:10:53 +03:00
|
|
|
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
address_space_stq_be(&address_space_memory, notif_port, data,
|
|
|
|
MEMTXATTRS_UNSPECIFIED, &result);
|
|
|
|
if (result != MEMTX_OK) {
|
|
|
|
phb_error(phb, "trigger failed @%"HWADDR_PRIx "\n", notif_port);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2022-03-02 08:51:39 +03:00
|
|
|
static void pnv_phb4_xive_notify(XiveNotifier *xf, uint32_t srcno,
|
|
|
|
bool pq_checked)
|
|
|
|
{
|
|
|
|
PnvPHB4 *phb = PNV_PHB4(xf);
|
|
|
|
|
|
|
|
if (phb->regs[PHB_CTRLR >> 3] & PHB_CTRLR_IRQ_ABT_MODE) {
|
|
|
|
pnv_phb4_xive_notify_abt(phb, srcno, pq_checked);
|
|
|
|
} else {
|
|
|
|
pnv_phb4_xive_notify_ic(phb, srcno, pq_checked);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
static Property pnv_phb4_properties[] = {
|
2022-06-03 00:53:51 +03:00
|
|
|
DEFINE_PROP_UINT32("index", PnvPHB4, phb_id, 0),
|
|
|
|
DEFINE_PROP_UINT32("chip-id", PnvPHB4, chip_id, 0),
|
|
|
|
DEFINE_PROP_LINK("pec", PnvPHB4, pec, TYPE_PNV_PHB4_PEC,
|
|
|
|
PnvPhb4PecState *),
|
2022-06-24 11:49:14 +03:00
|
|
|
DEFINE_PROP_LINK("phb-base", PnvPHB4, phb_base, TYPE_PNV_PHB, PnvPHB *),
|
2022-06-03 00:53:51 +03:00
|
|
|
DEFINE_PROP_END_OF_LIST(),
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
};
|
|
|
|
|
|
|
|
static void pnv_phb4_class_init(ObjectClass *klass, void *data)
|
|
|
|
{
|
|
|
|
DeviceClass *dc = DEVICE_CLASS(klass);
|
|
|
|
XiveNotifierClass *xfc = XIVE_NOTIFIER_CLASS(klass);
|
|
|
|
|
|
|
|
dc->realize = pnv_phb4_realize;
|
|
|
|
device_class_set_props(dc, pnv_phb4_properties);
|
ppc/pnv: Remove user-created PHB{3,4,5} devices
On a real system with POWER{8,9,10} processors, PHBs are sub-units of
the processor, they can be deactivated by firmware but not plugged in
or out like a PCI adapter on a slot. Nevertheless, having user-created
PHBs in QEMU seemed to be a good idea for testing purposes :
1. having a limited set of PHBs speedups boot time.
2. it is useful to be able to mimic a partially broken topology you
some time have to deal with during bring-up.
PowerNV is also used for distro install tests and having libvirt
support eases these tasks. libvirt prefers to run the machine with
-nodefaults to be sure not to drag unexpected devices which would need
to be defined in the domain file without being specified on the QEMU
command line. For this reason :
3. -nodefaults should not include default PHBs
User-created PHB{3,4,5} devices satisfied all these needs but reality
proves to be a bit more complex, internally when modeling such
devices, and externally when dealing with the user interface.
Req 1. and 2. can be simply addressed differently with a machine option:
"phb-mask=<uint>", which QEMU would use to enable/disable PHB device
nodes when creating the device tree.
For Req 3., we need to make sure we are taking the right approach. It
seems that we should expose a new type of user-created PHB device, a
generic virtualized one, that libvirt would use and not one depending
on the processor revision. This needs more thinking.
For now, remove user-created PHB{3,4,5} devices. All the cleanups we
did are not lost and they will be useful for the next steps.
Fixes: 5bc67b052b51 ("ppc/pnv: Introduce user creatable pnv-phb4 devices")
Fixes: 1f6a88fffc75 ("ppc/pnv: Introduce support for user created PHB3 devices")
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Reviewed-by: Frederic Barrat <fbarrat@linux.ibm.com>
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20220314130514.529931-1-clg@kaod.org>
Signed-off-by: Cédric Le Goater <clg@kaod.org>
2022-03-14 17:57:17 +03:00
|
|
|
dc->user_creatable = false;
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
|
|
|
|
xfc->notify = pnv_phb4_xive_notify;
|
|
|
|
}
|
|
|
|
|
|
|
|
static const TypeInfo pnv_phb4_type_info = {
|
|
|
|
.name = TYPE_PNV_PHB4,
|
2022-06-24 11:49:14 +03:00
|
|
|
.parent = TYPE_DEVICE,
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
.instance_init = pnv_phb4_instance_init,
|
|
|
|
.instance_size = sizeof(PnvPHB4),
|
|
|
|
.class_init = pnv_phb4_class_init,
|
|
|
|
.interfaces = (InterfaceInfo[]) {
|
|
|
|
{ TYPE_XIVE_NOTIFIER },
|
|
|
|
{ },
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
2022-03-14 17:57:17 +03:00
|
|
|
static const TypeInfo pnv_phb5_type_info = {
|
|
|
|
.name = TYPE_PNV_PHB5,
|
|
|
|
.parent = TYPE_PNV_PHB4,
|
|
|
|
.instance_size = sizeof(PnvPHB4),
|
|
|
|
};
|
|
|
|
|
2022-08-11 19:39:41 +03:00
|
|
|
static void pnv_phb4_root_bus_get_prop(Object *obj, Visitor *v,
|
|
|
|
const char *name,
|
|
|
|
void *opaque, Error **errp)
|
|
|
|
{
|
|
|
|
PnvPHB4RootBus *bus = PNV_PHB4_ROOT_BUS(obj);
|
|
|
|
uint64_t value = 0;
|
|
|
|
|
|
|
|
if (strcmp(name, "phb-id") == 0) {
|
|
|
|
value = bus->phb_id;
|
|
|
|
} else {
|
|
|
|
value = bus->chip_id;
|
|
|
|
}
|
|
|
|
|
|
|
|
visit_type_size(v, name, &value, errp);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void pnv_phb4_root_bus_set_prop(Object *obj, Visitor *v,
|
|
|
|
const char *name,
|
|
|
|
void *opaque, Error **errp)
|
|
|
|
|
|
|
|
{
|
|
|
|
PnvPHB4RootBus *bus = PNV_PHB4_ROOT_BUS(obj);
|
|
|
|
uint64_t value;
|
|
|
|
|
|
|
|
if (!visit_type_size(v, name, &value, errp)) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (strcmp(name, "phb-id") == 0) {
|
|
|
|
bus->phb_id = value;
|
|
|
|
} else {
|
|
|
|
bus->chip_id = value;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
static void pnv_phb4_root_bus_class_init(ObjectClass *klass, void *data)
|
|
|
|
{
|
|
|
|
BusClass *k = BUS_CLASS(klass);
|
|
|
|
|
2022-08-11 19:39:41 +03:00
|
|
|
object_class_property_add(klass, "phb-id", "int",
|
|
|
|
pnv_phb4_root_bus_get_prop,
|
|
|
|
pnv_phb4_root_bus_set_prop,
|
|
|
|
NULL, NULL);
|
|
|
|
|
|
|
|
object_class_property_add(klass, "chip-id", "int",
|
|
|
|
pnv_phb4_root_bus_get_prop,
|
|
|
|
pnv_phb4_root_bus_set_prop,
|
|
|
|
NULL, NULL);
|
|
|
|
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
/*
|
|
|
|
* PHB4 has only a single root complex. Enforce the limit on the
|
|
|
|
* parent bus
|
|
|
|
*/
|
|
|
|
k->max_dev = 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
static const TypeInfo pnv_phb4_root_bus_info = {
|
|
|
|
.name = TYPE_PNV_PHB4_ROOT_BUS,
|
|
|
|
.parent = TYPE_PCIE_BUS,
|
2022-09-20 13:31:48 +03:00
|
|
|
.instance_size = sizeof(PnvPHB4RootBus),
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
.class_init = pnv_phb4_root_bus_class_init,
|
|
|
|
};
|
|
|
|
|
|
|
|
static void pnv_phb4_register_types(void)
|
|
|
|
{
|
|
|
|
type_register_static(&pnv_phb4_root_bus_info);
|
|
|
|
type_register_static(&pnv_phb4_type_info);
|
2022-03-14 17:57:17 +03:00
|
|
|
type_register_static(&pnv_phb5_type_info);
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
type_register_static(&pnv_phb4_iommu_memory_region_info);
|
|
|
|
}
|
|
|
|
|
|
|
|
type_init(pnv_phb4_register_types);
|
|
|
|
|
|
|
|
void pnv_phb4_pic_print_info(PnvPHB4 *phb, Monitor *mon)
|
|
|
|
{
|
2022-03-02 08:51:39 +03:00
|
|
|
uint64_t notif_port =
|
|
|
|
phb->regs[PHB_INT_NOTIFY_ADDR >> 3] & ~PHB_INT_NOTIFY_ADDR_64K;
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
uint32_t offset = phb->regs[PHB_INT_NOTIFY_INDEX >> 3];
|
2022-03-02 08:51:39 +03:00
|
|
|
bool abt = !!(phb->regs[PHB_CTRLR >> 3] & PHB_CTRLR_IRQ_ABT_MODE);
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
|
2022-03-02 08:51:39 +03:00
|
|
|
monitor_printf(mon, "PHB4[%x:%x] Source %08x .. %08x %s @%"HWADDR_PRIx"\n",
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
phb->chip_id, phb->phb_id,
|
2022-03-02 08:51:39 +03:00
|
|
|
offset, offset + phb->xsrc.nr_irqs - 1,
|
|
|
|
abt ? "ABT" : "",
|
|
|
|
notif_port);
|
ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge
These changes introduces models for the PCIe Host Bridge (PHB4) of the
POWER9 processor. It includes the PowerBus logic interface (PBCQ),
IOMMU support, a single PCIe Gen.4 Root Complex, and support for MSI
and LSI interrupt sources as found on a POWER9 system using the XIVE
interrupt controller.
POWER9 processor comes with 3 PHB4 PEC (PCI Express Controller) and
each PEC can have several PHBs. By default,
* PEC0 provides 1 PHB (PHB0)
* PEC1 provides 2 PHBs (PHB1 and PHB2)
* PEC2 provides 3 PHBs (PHB3, PHB4 and PHB5)
Each PEC has a set "global" registers and some "per-stack" (per-PHB)
registers. Those are organized in two XSCOM ranges, the "Nest" range
and the "PCI" range, each range contains both some "PEC" registers and
some "per-stack" registers.
No default device layout is provided and PCI devices can be added on
any of the available PCIe Root Port (pcie.0 .. 2 of a Power9 chip)
with address 0x0 as the firwware (skiboot) only accepts a single
device per root port. To run a simple system with a network and a
storage adapters, use a command line options such as :
-device e1000e,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pcie.0,addr=0x0
-netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=hostnet0
-device megasas,id=scsi0,bus=pcie.1,addr=0x0
-drive file=$disk,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
If more are needed, include a bridge.
Multi chip is supported, each chip adding its set of PHB4 controllers
and its PCI busses. The model doesn't emulate the EEH error handling.
This model is not ready for hotplug yet.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
[ clg: - numerous cleanups
- commit log
- fix for broken LSI support
- PHB pic printinfo
- large QOM rework ]
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20200127144506.11132-2-clg@kaod.org>
[dwg: Use device_class_set_props()]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2020-01-27 17:45:05 +03:00
|
|
|
xive_source_pic_print_info(&phb->xsrc, 0, mon);
|
|
|
|
}
|