From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: linuxppc-dev@ozlabs.org, Thomas Huth <thuth@redhat.com>,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
david@gibson.dropbear.id.au
Subject: Re: [PATCH 2/2] pci: Use Qemu created PCI device nodes
Date: Sat, 25 Apr 2015 21:25:57 +1000 [thread overview]
Message-ID: <1429961157.16571.43.camel@kernel.crashing.org> (raw)
In-Reply-To: <553B42EB.6080803@ozlabs.ru>
On Sat, 2015-04-25 at 17:31 +1000, Alexey Kardashevskiy wrote:
> 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.
Doing BAR setup in the guest is a violation of PAPR though .... we do it now
to workaround bugs I believe but normally the BARs are expected to be owned
and setup by FW on a PAPR system.
Ben.
next prev parent reply other threads:[~2015-04-25 11:26 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
2015-04-25 11:25 ` Benjamin Herrenschmidt [this message]
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=1429961157.16571.43.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=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).