qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Cc: "Liu, Jing2" <jing2.liu@linux.intel.com>,
	yang.zhong@intel.com, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Issues] PCI hotplug does not work well on pc platform?
Date: Thu, 14 Feb 2019 15:15:20 +0100	[thread overview]
Message-ID: <20190214151520.2763805d@redhat.com> (raw)
In-Reply-To: <6cd527d2-b8d8-0eb9-78eb-a59c3ee4ccc7@gmail.com>

On Thu, 14 Feb 2019 15:12:35 +0200
Marcel Apfelbaum <marcel.apfelbaum@gmail.com> wrote:

> Hi Igor, Jing
> 
> On 2/14/19 1:31 PM, Igor Mammedov wrote:
> > On Wed, 13 Feb 2019 15:40:57 +0800
> > "Liu, Jing2" <jing2.liu@linux.intel.com> wrote:
> >  
> >> Hi Igor,
> >>
> >> Thanks for your reply!
> >>
> >> On 2/5/2019 11:47 PM, Igor Mammedov wrote:  
> >>> On Wed, 30 Jan 2019 21:02:10 +0800
> >>> "Liu, Jing2" <jing2.liu@linux.intel.com> wrote:
> >>>      
> >>>> 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)  
> 
> What about |CONFIG_HOTPLUG_PCI_SHPC=y ?
> 
> |
> >>>> Whether this is a kind of design or a known issue? Does guest receive
> >>>> the request, where can I find the  
> >>> does it work with known to work kernels (RHEL7)?
> >>>
> >>> Also sharing used QEMU version and command line could help.
> >>>      
> >> Is there any key config of kernel in guest, besides those I listed above?  
> > Maybe Marcel knows something about it
> > (CCed)  
> 
> May I ask why do you need SHPC hotplug and not the ACPI based hotplug?
I'd say SHPC one is preferred one, ACPI hotplug is rather complicated
QEMU hack to make legacy Windows guest support hotplug of PCI devices.
 
[...]

  reply	other threads:[~2019-02-14 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 13:02 [Qemu-devel] [Issues] PCI hotplug does not work well on pc platform? Liu, Jing2
2019-02-05 15:47 ` 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 [this message]
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=20190214151520.2763805d@redhat.com \
    --to=imammedo@redhat.com \
    --cc=jing2.liu@linux.intel.com \
    --cc=marcel.apfelbaum@gmail.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).