qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Liu, Jing2" <jing2.liu@linux.intel.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: yang.zhong@intel.com
Subject: [Qemu-devel] [Issues] PCI hotplug does not work well on pc platform?
Date: Wed, 30 Jan 2019 21:02:10 +0800	[thread overview]
Message-ID: <49127da6-814d-4675-21a5-48a8aa764e34@linux.intel.com> (raw)

Hi everyone,

I have two questions.
1. PCI hotplug on pci.0 must manually rescan in guest. The ACPI hotplug 
handler sends the GPE event to guest but it seems guest doesn't receive 
it? I tried to open ACPI debug level/layer to 0xffffffff, in order to 
see if there is any message after device_add in monitor, but no message 
comes out until I manually rescan. Also tried printk in 
acpi_ev_gpe_xrupt_handler() and acpi_ev_sci_xrupt_handler(). No output 
in dmesg.
(I'm sure that CONFIG_HOTPLUG_PCI_PCIE=y, CONFIG_HOTPLUG_PCI_CPCI=y, 
CONFIG_HOTPLUG_PCI=y, CONFIG_HOTPLUG_PCI_ACPI=y)

Whether this is a kind of design or a known issue? Does guest receive 
the request, where can I find the

2. I want to try hotplugging on pci-bridge on pc platform, using shpc. I 
set shpc=on, but when I do device_add, qemu still calls 
acpi_pcihp_device_plug_cb? Why it does not call pci_bridge_dev_hotplug_cb?
(CONFIG_HOTPLUG_PCI_SHPC=y)

Thanks very much!
Jing

             reply	other threads:[~2019-01-30 13:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 13:02 Liu, Jing2 [this message]
2019-02-05 15:47 ` [Qemu-devel] [Issues] PCI hotplug does not work well on pc platform? Igor Mammedov
2019-02-13  7:40   ` Liu, Jing2
2019-02-14 11:31     ` Igor Mammedov
2019-02-14 13:12       ` Marcel Apfelbaum
2019-02-14 14:15         ` Igor Mammedov
2019-02-14 14:42           ` Marcel Apfelbaum
2019-02-18  4:24             ` Liu, Jing2

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=49127da6-814d-4675-21a5-48a8aa764e34@linux.intel.com \
    --to=jing2.liu@linux.intel.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yang.zhong@intel.com \
    /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).