From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: Richard Yang <weiyang@linux.vnet.ibm.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Gavin Shan <gwshan@linux.vnet.ibm.com>,
bhelgaas@google.com, mpe@ellerman.id.au,
linuxppc-dev@lists.ozlabs.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH V9 11/11] powerpc/powernv: compound PE for VFs
Date: Thu, 17 Sep 2015 10:28:33 +1000 [thread overview]
Message-ID: <20150917002832.GA2034@gwshan> (raw)
In-Reply-To: <20150909060129.GC7684@Richards-MacBook-Pro.local>
On Wed, Sep 09, 2015 at 02:01:29PM +0800, Richard Yang wrote:
>On Wed, Sep 09, 2015 at 03:22:08PM +1000, Alexey Kardashevskiy wrote:
>>On 09/09/2015 01:36 PM, Richard Yang wrote:
>>>On Wed, Sep 09, 2015 at 12:48:21PM +1000, Gavin Shan wrote:
>>>>On Wed, Jul 29, 2015 at 11:17:18AM +0800, Wei Yang wrote:
>>>>>Hi, Michael
>>>>>
>>>>>Hope you didn't take this yet. We may change this patch a little.
>>>>>
>>>>
>>>>[Cc Alexey who might concern the SRIOV status]
>>>>
>>>>Richard, do you have plan to get it upstream? It seems it's hanged
>>>>over here for long time.
>>>>
>>>
>>>The VF EEH is hung since we re-designed the SRIOV. After the re-design, we
>>>don't have VF groups.
>>>
>>>My plan is to push the VF EEH patch set after the SRIOV Redesign is accepted.
>>
>>
>>Can you please rebase on v4.2 (or v4.2 + sriov rework) and repost VF EEH
>>patchset just to me? Or share the tree somewhere where I can pull it from?
>>Thanks.
>>
>
>Yep, this is what I am planning to do.
>
Can you rebase your patchset on v4.3.rc1+sriov rework and then repost to
linux-ppc-dev maillist?
>>As for now, I cannot tell what difference your SRIOV patchset actually makes.
>>
>>--
>>Alexey
>
>--
>Richard Yang
>Help you, Help me
prev parent reply other threads:[~2015-09-17 0:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 6:02 [PATCH V9 00/11] VF EEH on Power8 Wei Yang
2015-07-17 6:02 ` [PATCH V9 01/11] PCI/IOV: Rename and export virtfn_add/virtfn_remove Wei Yang
2015-07-17 6:02 ` [PATCH V9 02/11] PCI: Add pcibios_bus_add_device() weak function Wei Yang
2015-07-17 6:02 ` [PATCH V9 03/11] powerpc/pci: Cache VF index in pci_dn Wei Yang
2015-07-17 6:02 ` [PATCH V9 04/11] powerpc/pci: Remove VFs prior to PF Wei Yang
2015-07-17 6:02 ` [PATCH V9 05/11] powerpc/eeh: Cache only BARs, not windows or IOV BARs Wei Yang
2015-07-17 6:02 ` [PATCH V9 06/11] powerpc/powernv: EEH device for VF Wei Yang
2015-07-17 6:02 ` [PATCH V9 07/11] powerpc/eeh: Create PE for VFs Wei Yang
2015-07-17 6:02 ` [PATCH V9 08/11] powerpc/powernv: Support EEH reset for VF PE Wei Yang
2015-07-17 6:02 ` [PATCH V9 09/11] powerpc/powernv: Support PCI config restore for VFs Wei Yang
2015-07-17 6:02 ` [PATCH V9 10/11] powerpc/eeh: Support error recovery for VF PE Wei Yang
2015-07-17 6:02 ` [PATCH V9 11/11] powerpc/powernv: compound PE for VFs Wei Yang
2015-07-29 3:17 ` Wei Yang
2015-09-09 2:48 ` Gavin Shan
2015-09-09 3:36 ` Richard Yang
2015-09-09 3:52 ` Gavin Shan
2015-09-09 6:00 ` Richard Yang
2015-09-09 4:59 ` Benjamin Herrenschmidt
2015-09-09 5:53 ` Richard Yang
2015-09-09 5:22 ` Alexey Kardashevskiy
2015-09-09 6:01 ` Richard Yang
2015-09-17 0:28 ` Gavin Shan [this message]
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=20150917002832.GA2034@gwshan \
--to=gwshan@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=weiyang@linux.vnet.ibm.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).