From: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
To: qemu-ppc@nongnu.org, david@gibson.dropbear.id.au
Cc: agraf@suse.de, thuth@redhat.com, nikunj@linux.vnet.ibm.com,
aik@ozlabs.ru, mdroth@linux.vnet.ibm.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v8 0/3] spapr_pci: PCI DT node creation in QEMU
Date: Thu, 18 Jun 2015 16:50:26 +0530 [thread overview]
Message-ID: <1434626429-9488-1-git-send-email-nikunj@linux.vnet.ibm.com> (raw)
The patch series creates PCI device tree(DT) nodes in QEMU. The new
hotplug code needs the device node creation in QEMU. While during
boot, nodes were created in SLOF. It makes more sense to consolidate
the code to one place for better maintainability.
New slof.bin is already there in spapr-next
Changelog V7:
* Rebased to spapr-next
* Dropped three patches that have been picked upstream
* Limited usage of sPAPRFDT to pci enumeration code (David Gibson)
* Reworked all the patches and moved cleanup in last patch.
Changelog V6:
* Open coded fdt_setprop_string as the return would
leak memory (Thomas Huth)
Changelog V5:
* Reworked enumerate bridges to reduce scopes (Alexey)
* Fixed unit address which should be hex
* Added FDT_NAME_MAX and use snprintf for composing name (Alexey)
* Added patch to drop redundant args and change prototype (Alexey)
* Added bus number in the ibm,loc-code for qemu emulated or failed
vfio device.
* Now qemu_<name>:<phb-index>:<bus>:<slot>.<fn> is having
hex encoding (Alexey)
Changelog V4:
* Refactored and simplified the "ibm,loc-code" patch
Changelog V3:
* Dropped duplicate macro patches
* Squashed Michael's drc_index changes to enumeration patch
* Use common create routine for boottime and hotplug case
* Proper error handling not depending on g_assert
* Encode vfio loc-code if getting loc-code from host fails
Changelog V2:
* Fix device tree for 64-bit encoding
* Fix the class code, was failing xhci
* Remove macro duplication
* Fix DT fields generation for boot time device (Michael Roth)
Changelog v1:
* Correct indent problems reported by checkpatch(David Gibson)
* Declare sPAPRFDT structure as local (David Gibson)
* Re-arrange code to avoid multiple indentation (Alexey Kardashevskiy)
Nikunj A Dadhania (3):
spapr_pci: enumerate and add PCI device tree
spapr_pci: populate ibm,loc-code
spapr_pci: drop redundant args in spapr_[populate,create]_pci_child_dt
hw/ppc/spapr_pci.c | 228 +++++++++++++++++++++++++++++++++++++++++++++++------
1 file changed, 202 insertions(+), 26 deletions(-)
--
1.8.3.1
next reply other threads:[~2015-06-18 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 11:20 Nikunj A Dadhania [this message]
2015-06-18 11:20 ` [Qemu-devel] [PATCH v8 1/3] spapr_pci: enumerate and add PCI device tree Nikunj A Dadhania
2015-06-18 11:20 ` [Qemu-devel] [PATCH v8 2/3] spapr_pci: populate ibm,loc-code Nikunj A Dadhania
2015-06-18 11:20 ` [Qemu-devel] [PATCH v8 3/3] spapr_pci: drop redundant args in spapr_[populate, create]_pci_child_dt Nikunj A Dadhania
2015-06-22 2:59 ` [Qemu-devel] [PATCH v8 0/3] spapr_pci: PCI DT node creation in QEMU David Gibson
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=1434626429-9488-1-git-send-email-nikunj@linux.vnet.ibm.com \
--to=nikunj@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.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).