linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Thomas Huth <thuth@redhat.com>,
	Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, david@gibson.dropbear.id.au
Subject: Re: [PATCH 2/2] pci: Use Qemu created PCI device nodes
Date: Sat, 25 Apr 2015 17:31:55 +1000	[thread overview]
Message-ID: <553B42EB.6080803@ozlabs.ru> (raw)
In-Reply-To: <20150424213058.2889af29@thh440s>

On 04/25/2015 05:30 AM, Thomas Huth wrote:
>
>   Hi Nikunj,
>
> On Wed, 22 Apr 2015 16:27:20 +0530
> Nikunj A Dadhania <nikunj@linux.vnet.ibm.com> wrote:
>
>> PCI Enumeration has been part of SLOF. Now with hotplug code addition
>> in Qemu, it makes more sense to have this code a one place, i.e. Qemu.
>
> s/Qemu/QEMU/ and s/code a one place/code in one place/ ?
>
>> Adding routines to walk through the device nodes created by Qemu. SLOF
>> will configure the device/bridges and program the BARs for
>> communicating with the devices.
>
> I wonder whether it would make more sense to also set up the BARs etc.
> in QEMU instead of SLOF?

We need BAR setup in 2 cases: when SLOF needs to boot from a PCI device 
(and SLOF can do BAR setup) and when we do PCI hotplug - and BARs are set 
by the guest, otherwise we hit races here (Michael Roth can tell more). So 
as for today there is no reason for doing this in QEMU.




-- 
Alexey

  reply	other threads:[~2015-04-25  7:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 10:57 [PATCH 2/2] pci: Use Qemu created PCI device nodes Nikunj A Dadhania
2015-04-24 19:30 ` Thomas Huth
2015-04-25  7:31   ` Alexey Kardashevskiy [this message]
2015-04-25 11:25     ` Benjamin Herrenschmidt
2015-04-27  4:47   ` 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=553B42EB.6080803@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=nikunj@linux.vnet.ibm.com \
    --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).