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: jing2.liu@intel.com
Subject: [Qemu-devel] [Question] Hotplug rescan/remove by manual
Date: Thu, 29 Nov 2018 15:32:21 +0800	[thread overview]
Message-ID: <62de590c-b752-1946-1a53-b0e94a4022d3@linux.intel.com> (raw)

Hi guys,
When I tested hotplug on pci.0 on pc platform, it seems that we have to
echo 1 > /sys/bus/pci/rescan manually in guest? Is this a non-complete 
feature because of something like gpe interrupt issue?
For hot-unplug, I uses echo 1 > /sys/bus/pci/<device>/remove but this
seems only remove the device in guest but we still can see it in qemu 
monitor by "info pci". I guess this is not a right way to unplug. I'm
not sure if I missed something?

Looking forwards to your response.
Thanks!

Jing

                 reply	other threads:[~2018-11-29  7:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=62de590c-b752-1946-1a53-b0e94a4022d3@linux.intel.com \
    --to=jing2.liu@linux.intel.com \
    --cc=jing2.liu@intel.com \
    --cc=qemu-devel@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).