From: David Gibson <david@gibson.dropbear.id.au>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Did we lose monitor commands pci_add, pci_del?
Date: Sat, 14 Feb 2015 09:54:21 +1100 [thread overview]
Message-ID: <20150213225421.GB30518@voom.redhat.com> (raw)
In-Reply-To: <87a90hoiup.fsf@blackfin.pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
On Fri, Feb 13, 2015 at 05:51:26PM +0100, Markus Armbruster wrote:
> Commit 79ca616 "pci: Cleanup configuration for pci-hotplug.c" (June
> 2013, released in v1.6.0) made linking pci-hotplug-old.o conditional on
> make variable CONFIG_PCI_HOTPLUG_OLD, and the actual monitor commands
> conditional on preprocessor macro CONFIG_PCI_HOTPLUG_OLD. Where is that
> macro defined?
>
> In my local build: nowhere. The two commands are not available.
>
> Am I doing something wrong, or have the commands been gone for five
> major releases already?
>
> If the latter, I think we can safely drop them now :)
So AFAICT, CONFIG_PCI_HOTPLUG_OLD is still defined for x86 targets:
$ git grep PCI_HOTPLUG_OLD
default-configs/i386-softmmu.mak:CONFIG_PCI_HOTPLUG_OLD=y
default-configs/x86_64-softmmu.mak:CONFIG_PCI_HOTPLUG_OLD=y
...
I believe the reasoning was that for other targets, pci_add/del were
never properly supported and we should go directly to device_add/del
instead.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-13 22:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 16:51 [Qemu-devel] Did we lose monitor commands pci_add, pci_del? Markus Armbruster
2015-02-13 22:54 ` David Gibson [this message]
2015-02-14 13:19 ` Paolo Bonzini
2015-02-15 3:02 ` David Gibson
2015-02-15 11:12 ` Peter Maydell
2015-02-16 7:57 ` Markus Armbruster
2015-02-16 10:06 ` Michael Tokarev
2015-02-16 8:56 ` Paolo Bonzini
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=20150213225421.GB30518@voom.redhat.com \
--to=david@gibson.dropbear.id.au \
--cc=armbru@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.