From: Greg Kurz <groug@kaod.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: lvivier@redhat.com, thuth@redhat.com, ehabkost@redhat.com,
qemu-devel@nongnu.org, abologna@redhat.com,
mdroth@linux.vnet.ibm.com, libvir-list@redhat.com,
qemu-ppc@nongnu.org, marcel@redhat.com
Subject: Re: [Qemu-devel] [Qemu-ppc] Proposal PCI/PCIe device placement on PAPR guests
Date: Thu, 23 Feb 2017 08:23:50 +0100 [thread overview]
Message-ID: <20170223082350.4c118d7e@bahia.lan> (raw)
In-Reply-To: <20170223021152.GR12577@umbus.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
On Thu, 23 Feb 2017 13:11:52 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> On Wed, Feb 22, 2017 at 12:08:25PM +0100, Greg Kurz wrote:
> > David,
> >
> > I don't see the "spapr_pci: Allow PCI-Express devices" patch in your
> > ppc-for-2.9 tree. Do you still consider merging it ?
>
> No. After discussions with Marcel Apfelbaum and others I'm looking at
> a different approach for PCIe support.
>
Oh, I had missed that... Is it the following thread ?
https://lists.gnu.org/archive/html/qemu-ppc/2017-02/msg00203.html
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-02-23 7:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170105054618.GA12106@umbus.fritz.box>
2017-01-06 12:01 ` [Qemu-devel] Proposal PCI/PCIe device placement on PAPR guests Greg Kurz
2017-01-06 17:34 ` Andrea Bolognani
2017-01-08 23:46 ` David Gibson
2017-01-12 10:31 ` Andrea Bolognani
2017-01-12 14:52 ` Laine Stump
2017-01-12 16:35 ` Michael Roth
2017-01-12 17:53 ` Laine Stump
2017-01-12 22:56 ` David Gibson
2017-01-18 12:21 ` Marcel Apfelbaum
2017-01-12 22:57 ` David Gibson
2017-01-13 16:29 ` Greg Kurz
[not found] ` <20170106125758.4643fb35@bahia.lan>
[not found] ` <20170112035219.GK14026@umbus.fritz.box>
[not found] ` <0bfaa82a-d5f5-eb0f-14a9-f7d13239cee5@ozlabs.ru>
[not found] ` <20170112100823.2a906117@bahia.lan>
[not found] ` <20170113044831.GP13656@umbus.fritz.box>
[not found] ` <20170113095828.302b77f2@bahia.lan>
[not found] ` <20170222120825.0253f2d6@bahia.lan>
[not found] ` <20170223021152.GR12577@umbus.fritz.box>
2017-02-23 7:23 ` Greg Kurz [this message]
2017-02-23 22:57 ` [Qemu-devel] [Qemu-ppc] " 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=20170223082350.4c118d7e@bahia.lan \
--to=groug@kaod.org \
--cc=abologna@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=libvir-list@redhat.com \
--cc=lvivier@redhat.com \
--cc=marcel@redhat.com \
--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).