From: Cornelia Huck <cohuck@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
David Hildenbrand <david@redhat.com>,
Cornelia Huck <cohuck@redhat.com>
Subject: [Qemu-devel] [PULL 09/10] s390x/pci: Warn when adding PCI devices without the 'zpci' feature
Date: Tue, 5 Feb 2019 17:41:08 +0100 [thread overview]
Message-ID: <20190205164109.25413-10-cohuck@redhat.com> (raw)
In-Reply-To: <20190205164109.25413-1-cohuck@redhat.com>
From: David Hildenbrand <david@redhat.com>
We decided to always create the PCI host bridge, even if 'zpci' is not
enabled (due to migration compatibility). This however right now allows
to add zPCI/PCI devices to a VM although the guest will never actually see
them, confusing people that are using a simple CPU model that has no
'zpci' enabled - "Why isn't this working" (David Hildenbrand)
Let's check for 'zpci' and at least print a warning that this will not
work as expected. We could also bail out, however that might break
existing QEMU commandlines.
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20190130155733.32742-4-david@redhat.com>
Reviewed-by: Collin Walling <walling@linux.ibm.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
---
hw/s390x/s390-pci-bus.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/hw/s390x/s390-pci-bus.c b/hw/s390x/s390-pci-bus.c
index d85bc34617..3816fb1f11 100644
--- a/hw/s390x/s390-pci-bus.c
+++ b/hw/s390x/s390-pci-bus.c
@@ -860,6 +860,12 @@ static void s390_pcihost_pre_plug(HotplugHandler *hotplug_dev, DeviceState *dev,
{
S390pciState *s = S390_PCI_HOST_BRIDGE(hotplug_dev);
+ if (!s390_has_feat(S390_FEAT_ZPCI)) {
+ warn_report("Plugging a PCI/zPCI device without the 'zpci' CPU "
+ "feature enabled; the guest will not be able to see/use "
+ "this device");
+ }
+
if (object_dynamic_cast(OBJECT(dev), TYPE_PCI_DEVICE)) {
PCIDevice *pdev = PCI_DEVICE(dev);
--
2.17.2
next prev parent reply other threads:[~2019-02-05 16:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 16:40 [Qemu-devel] [PULL 00/10] s390x update Cornelia Huck
2019-02-05 16:41 ` [Qemu-devel] [PULL 01/10] target/s390x: define TCG_GUEST_DEFAULT_MO for MTTCG Cornelia Huck
2019-02-05 16:41 ` [Qemu-devel] [PULL 02/10] s390x: remove direct reference to mem_path global from s390x code Cornelia Huck
2019-02-05 16:41 ` [Qemu-devel] [PULL 03/10] s390x/pci: Introduce unplug requests and split unplug handler Cornelia Huck
2019-02-05 16:41 ` [Qemu-devel] [PULL 04/10] s390x/pci: Drop release timer and replace it with a flag Cornelia Huck
2019-02-05 16:41 ` [Qemu-devel] [PULL 05/10] s390x/pci: mark zpci devices as unmigratable Cornelia Huck
2019-02-05 16:41 ` [Qemu-devel] [PULL 06/10] s390x/tcg: Don't model FP registers as globals Cornelia Huck
2019-02-05 16:41 ` [Qemu-devel] [PULL 07/10] s390x/pci: Fix primary bus number for PCI bridges Cornelia Huck
2019-02-05 16:41 ` [Qemu-devel] [PULL 08/10] s390x/pci: Fix hotplugging of " Cornelia Huck
2019-02-05 16:41 ` Cornelia Huck [this message]
2019-02-05 16:41 ` [Qemu-devel] [PULL 10/10] s390x/pci: Unplug remaining requested devices on pcihost reset Cornelia Huck
2019-02-05 18:21 ` [Qemu-devel] [PULL 00/10] s390x update Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190205164109.25413-10-cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).