We tried to make pci support optional on s390x in the past; unfortunately, we still require the s390 phb to be created unconditionally due to backwards compatibility issues. Instead of sinking more effort into this (including compat handling for older machines etc.) for non-obvious gains, let's just make CONFIG_PCI something that is always set on s390x. Note that you can still fence off pci for the _guest_ if you provide a cpu model without the zpci feature. Message-Id: <20190211113255.3837-1-cohuck@redhat.com> Reviewed-by: Thomas Huth <thuth@redhat.com> Reviewed-by: David Hildenbrand <david@redhat.com> Acked-by: Christian Borntraeger <borntraeger@de.ibm.com> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
35 lines
1.1 KiB
Makefile
35 lines
1.1 KiB
Makefile
obj-y += s390-virtio-hcall.o
|
|
obj-y += sclp.o
|
|
obj-y += event-facility.o
|
|
obj-y += sclpquiesce.o
|
|
obj-y += sclpcpu.o
|
|
obj-y += ipl.o
|
|
obj-y += css.o
|
|
obj-$(CONFIG_S390_CCW_VIRTIO) += s390-virtio-ccw.o
|
|
obj-y += 3270-ccw.o
|
|
obj-y += virtio-ccw.o
|
|
obj-$(CONFIG_VIRTIO_SERIAL) += virtio-ccw-serial.o
|
|
obj-$(CONFIG_VIRTIO_BALLOON) += virtio-ccw-balloon.o
|
|
obj-$(CONFIG_VIRTIO_SCSI) += virtio-ccw-scsi.o
|
|
obj-$(CONFIG_VIRTIO_RNG) += virtio-ccw-rng.o
|
|
obj-$(CONFIG_VIRTIO_CRYPTO) += virtio-ccw-crypto.o
|
|
obj-$(CONFIG_VIRTIO_GPU) += virtio-ccw-gpu.o
|
|
obj-$(CONFIG_VIRTIO_INPUT) += virtio-ccw-input.o
|
|
obj-$(CONFIG_VIRTIO_NET) += virtio-ccw-net.o
|
|
obj-$(CONFIG_VIRTIO_BLK) += virtio-ccw-blk.o
|
|
obj-$(call land,$(CONFIG_VIRTIO_9P),$(CONFIG_VIRTFS)) += virtio-ccw-9p.o
|
|
obj-$(CONFIG_VHOST_VSOCK) += vhost-vsock-ccw.o
|
|
obj-y += css-bridge.o
|
|
obj-y += ccw-device.o
|
|
obj-y += s390-pci-bus.o s390-pci-inst.o
|
|
obj-y += s390-skeys.o
|
|
obj-y += s390-stattrib.o
|
|
obj-y += tod.o
|
|
obj-y += tod-qemu.o
|
|
obj-$(CONFIG_KVM) += tod-kvm.o
|
|
obj-$(CONFIG_KVM) += s390-skeys-kvm.o
|
|
obj-$(CONFIG_KVM) += s390-stattrib-kvm.o
|
|
obj-y += s390-ccw.o
|
|
obj-y += ap-device.o
|
|
obj-y += ap-bridge.o
|