qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: aik@ozlabs.ru, qemu-ppc@nongnu.org, agraf@suse.de,
	nikunj@linux.vnet.ibm.com, david@gibson.dropbear.id.au
Subject: [Qemu-devel] [RFC PATCH 0/2] spapr: move pci device creation to Qemu
Date: Wed, 22 Apr 2015 16:05:32 +0530	[thread overview]
Message-ID: <1429698934-28915-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. 

Also, patches for populating ibm,loc-code was getting very complicated
with use of RTAS/HCALL

Nikunj A Dadhania (2):
  spapr: enumerate and add PCI device tree
  spapr: populate ibm,loc-code

 hw/ppc/spapr_pci.c | 166 ++++++++++++++++++++++++++++++++++++++++++++++++-----
 1 file changed, 153 insertions(+), 13 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2015-04-22 10:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 10:35 Nikunj A Dadhania [this message]
2015-04-22 10:35 ` [Qemu-devel] [RFC PATCH 1/2] spapr: enumerate and add PCI device tree Nikunj A Dadhania
2015-04-28  7:46   ` David Gibson
2015-04-28 11:15     ` Nikunj A Dadhania
2015-04-29  3:10   ` Alexey Kardashevskiy
2015-04-29  5:15     ` Nikunj A Dadhania
2015-04-22 10:35 ` [Qemu-devel] [RFC PATCH 2/2] spapr: populate ibm,loc-code Nikunj A Dadhania
2015-04-28  7:48   ` David Gibson
2015-04-28 11:10     ` Nikunj A Dadhania
2015-04-23  4:13 ` [Qemu-devel] [RFC PATCH 0/2] spapr: move pci device creation to Qemu 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=1429698934-28915-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=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).