2013-02-05 19:03:15 +08:00
|
|
|
# shared objects
|
2020-01-01 02:32:13 +08:00
|
|
|
obj-y += ppc.o ppc_booke.o
|
|
|
|
obj-$(CONFIG_FDT_PPC) += fdt.o
|
2020-01-01 02:32:12 +08:00
|
|
|
obj-$(CONFIG_FW_CFG_PPC) += fw_cfg.o
|
2013-02-05 19:03:15 +08:00
|
|
|
# IBM pSeries (sPAPR)
|
spapr: Capabilities infrastructure
Because PAPR is a paravirtual environment access to certain CPU (or other)
facilities can be blocked by the hypervisor. PAPR provides ways to
advertise in the device tree whether or not those features are available to
the guest.
In some places we automatically determine whether to make a feature
available based on whether our host can support it, in most cases this is
based on limitations in the available KVM implementation.
Although we correctly advertise this to the guest, it means that host
factors might make changes to the guest visible environment which is bad:
as well as generaly reducing reproducibility, it means that a migration
between different host environments can easily go bad.
We've mostly gotten away with it because the environments considered mature
enough to be well supported (basically, KVM on POWER8) have had consistent
feature availability. But, it's still not right and some limitations on
POWER9 is going to make it more of an issue in future.
This introduces an infrastructure for defining "sPAPR capabilities". These
are set by default based on the machine version, masked by the capabilities
of the chosen cpu, but can be overriden with machine properties.
The intention is at reset time we verify that the requested capabilities
can be supported on the host (considering TCG, KVM and/or host cpu
limitations). If not we simply fail, rather than silently modifying the
advertised featureset to the guest.
This does mean that certain configurations that "worked" may now fail, but
such configurations were already more subtly broken.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Greg Kurz <groug@kaod.org>
2017-12-08 07:35:35 +08:00
|
|
|
obj-$(CONFIG_PSERIES) += spapr.o spapr_caps.o spapr_vio.o spapr_events.o
|
2013-02-05 19:20:00 +08:00
|
|
|
obj-$(CONFIG_PSERIES) += spapr_hcall.o spapr_iommu.o spapr_rtas.o
|
2018-10-08 20:39:42 +08:00
|
|
|
obj-$(CONFIG_PSERIES) += spapr_pci.o spapr_rtc.o spapr_drc.o
|
2018-07-30 22:11:32 +08:00
|
|
|
obj-$(CONFIG_PSERIES) += spapr_cpu_core.o spapr_ovec.o spapr_irq.o
|
spapr: initial implementation for H_TPM_COMM/spapr-tpm-proxy
This implements the H_TPM_COMM hypercall, which is used by an
Ultravisor to pass TPM commands directly to the host's TPM device, or
a TPM Resource Manager associated with the device.
This also introduces a new virtual device, spapr-tpm-proxy, which
is used to configure the host TPM path to be used to service
requests sent by H_TPM_COMM hcalls, for example:
-device spapr-tpm-proxy,id=tpmp0,host-path=/dev/tpmrm0
By default, no spapr-tpm-proxy will be created, and hcalls will return
H_FUNCTION.
The full specification for this hypercall can be found in
docs/specs/ppc-spapr-uv-hcalls.txt
Since SVM-related hcalls like H_TPM_COMM use a reserved range of
0xEF00-0xEF80, we introduce a separate hcall table here to handle
them.
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com
Message-Id: <20190717205842.17827-3-mdroth@linux.vnet.ibm.com>
[dwg: Corrected #include for upstream change]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
2019-07-18 04:58:42 +08:00
|
|
|
obj-$(CONFIG_PSERIES) += spapr_tpm_proxy.o
|
2018-10-08 20:39:42 +08:00
|
|
|
obj-$(CONFIG_SPAPR_RNG) += spapr_rng.o
|
2020-01-01 02:32:11 +08:00
|
|
|
obj-$(call land,$(CONFIG_PSERIES),$(CONFIG_LINUX)) += spapr_pci_vfio.o spapr_pci_nvlink2.o
|
2016-10-22 17:46:35 +08:00
|
|
|
# IBM PowerNV
|
2017-04-11 23:30:05 +08:00
|
|
|
obj-$(CONFIG_POWERNV) += pnv.o pnv_xscom.o pnv_core.o pnv_lpc.o pnv_psi.o pnv_occ.o pnv_bmc.o
|
2019-10-21 21:12:11 +08:00
|
|
|
obj-$(CONFIG_POWERNV) += pnv_homer.o pnv_pnor.o
|
|
|
|
|
2016-07-04 11:33:07 +08:00
|
|
|
obj-$(CONFIG_PSERIES) += spapr_rtas_ddw.o
|
2013-02-05 19:03:15 +08:00
|
|
|
# PowerPC 4xx boards
|
2019-02-02 15:24:40 +08:00
|
|
|
obj-$(CONFIG_PPC405) += ppc405_boards.o ppc405_uc.o
|
|
|
|
obj-$(CONFIG_PPC440) += ppc440_bamboo.o ppc440_pcix.o ppc440_uc.o
|
|
|
|
obj-$(CONFIG_PPC4XX) += ppc4xx_pci.o ppc4xx_devs.o
|
2018-07-02 09:59:35 +08:00
|
|
|
obj-$(CONFIG_SAM460EX) += sam460ex.o
|
2013-01-27 03:41:58 +08:00
|
|
|
# PReP
|
2014-01-23 18:22:16 +08:00
|
|
|
obj-$(CONFIG_PREP) += prep.o
|
2017-01-07 23:23:41 +08:00
|
|
|
obj-$(CONFIG_PREP) += prep_systemio.o
|
2017-01-07 23:23:42 +08:00
|
|
|
obj-${CONFIG_RS6000_MC} += rs6000_mc.o
|
2013-01-24 07:03:54 +08:00
|
|
|
# OldWorld PowerMac
|
2019-02-02 15:24:40 +08:00
|
|
|
obj-$(CONFIG_MAC_OLDWORLD) += mac_oldworld.o
|
2013-01-24 07:03:54 +08:00
|
|
|
# NewWorld PowerMac
|
2019-02-02 15:24:40 +08:00
|
|
|
obj-$(CONFIG_MAC_NEWWORLD) += mac_newworld.o
|
2013-01-24 07:03:54 +08:00
|
|
|
# e500
|
2013-02-05 19:52:23 +08:00
|
|
|
obj-$(CONFIG_E500) += e500.o mpc8544ds.o e500plat.o
|
2013-02-05 22:22:56 +08:00
|
|
|
obj-$(CONFIG_E500) += mpc8544_guts.o ppce500_spin.o
|
2013-02-05 19:03:15 +08:00
|
|
|
# PowerPC 440 Xilinx ML507 reference board.
|
2019-02-02 15:24:40 +08:00
|
|
|
obj-$(CONFIG_VIRTEX) += virtex_ml507.o
|