From: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: nikunj@linux.vnet.ibm.com, aik@ozlabs.ru,
mdroth@linux.vnet.ibm.com, agraf@suse.de, qemu-ppc@nongnu.org,
david@gibson.dropbear.id.au
Subject: [Qemu-devel] [PATCH v2 0/2] spapr: move pci device creation to Qemu
Date: Wed, 29 Apr 2015 13:31:33 +0530 [thread overview]
Message-ID: <1430294495-22128-1-git-send-email-nikunj@linux.vnet.ibm.com> (raw)
The patch series creates PCI 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.
Based on sPAPR PCI Hotplug patches by Michael Roth
https://github.com/mdroth/qemu/commits/spapr-hotplug-pci
Also, patches for populating ibm,loc-code was getting very complicated
with use of RTAS/HCALL
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 (2):
spapr: enumerate and add PCI device tree
spapr: populate ibm,loc-code
hw/ppc/spapr_pci.c | 183 +++++++++++++++++++++++++++++++++++++++++++++++++----
1 file changed, 170 insertions(+), 13 deletions(-)
--
1.8.3.1
next reply other threads:[~2015-04-29 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 8:01 Nikunj A Dadhania [this message]
2015-04-29 8:01 ` [Qemu-devel] [PATCH v2 1/2] spapr: enumerate and add PCI device tree Nikunj A Dadhania
2015-04-29 8:01 ` [Qemu-devel] [PATCH v2 2/2] spapr: populate ibm,loc-code Nikunj A Dadhania
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=1430294495-22128-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 \
/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).