From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Gavin Shan <gwshan@linux.vnet.ibm.com>
Subject: Re: [PATCH v1 0/5] powerpc/pci: PCI slot unified reset
Date: Wed, 26 Nov 2014 11:04:51 +1100 [thread overview]
Message-ID: <20141126000451.GA21271@shangw> (raw)
In-Reply-To: <1416956093.5089.1.camel@kernel.crashing.org>
On Wed, Nov 26, 2014 at 09:54:53AM +1100, Benjamin Herrenschmidt wrote:
>On Tue, 2014-11-25 at 09:38 +1100, Gavin Shan wrote:
>> The patchset corresponds to skiboot changes, which manages PCI slots
>> in a unified way: OPAL APIs used to do slot reset, power management,
>> presence status retrival. The patchset shouldn't be merged before
>> the OPAL firmware counterpart is merged.
>
>This doesn't work. We need to have both backward and forward
>compatibility.
>
>IE. New kernels must work with old OPAL and vice-versa.
>
Yes, it's known issue as you remind me yesterday. I'll fix it in next
revision, from skiboot (I guess it would be official name to be used
now) side.
>> The kernel changes have been split into 2 parts: (A) Use the unified
>> PCI slot reset OPAL API - this patchset; (B) Changes to rpaphp.ko to
>> support PCI slot hotplug via sysfs entries for PowerPC PowerNV platform.
>
>I don't think we should be using rpaphp... we should be creating our new
>backend, there is almost no commonalities between RPA/PAPR and OPAL.
>
Ok. I'll create powernv-php as you suggested in another thread. Thank you
for your time on this.
Thanks,
Gavin
>> This patchset affects EEH, PCI reset logics, which is used mainly by
>> VFIO. A couple of cases have been tested out on P7/P8 boxes and looks
>> good: EEH on PowerNV, EEH support for guest, PCI passthrou.
>>
>> Gavin Shan (5):
>> powerpc/powernv: Use PCI slot reset infrastructure
>> powerpc/powernv: Refactor ioda_eeh_reset()
>> powerpc/powernv: Avoid do complete reset for twice
>> powerpc/powernv: Issue fundamental reset if required
>> powerpc/powernv: Drop opal_pci_reinit()
>>
>> arch/powerpc/include/asm/eeh.h | 2 +-
>> arch/powerpc/include/asm/opal.h | 31 +---
>> arch/powerpc/kernel/eeh_pe.c | 3 -
>> arch/powerpc/platforms/powernv/eeh-ioda.c | 230 ++++++++++++++-----------
>> arch/powerpc/platforms/powernv/eeh-powernv.c | 24 +--
>> arch/powerpc/platforms/powernv/opal-wrappers.S | 1 -
>> arch/powerpc/platforms/powernv/pci-ioda.c | 5 +-
>> arch/powerpc/platforms/pseries/eeh_pseries.c | 3 +-
>> 8 files changed, 139 insertions(+), 160 deletions(-)
>>
>> Thanks,
>> Gavin
>
>
next prev parent reply other threads:[~2014-11-26 0:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 22:38 [PATCH v1 0/5] powerpc/pci: PCI slot unified reset Gavin Shan
2014-11-24 22:38 ` [PATCH 1/5] powerpc/powernv: Use PCI slot reset infrastructure Gavin Shan
2014-11-24 22:38 ` [PATCH 2/5] powerpc/powernv: Refactor ioda_eeh_reset() Gavin Shan
2014-11-24 22:38 ` [PATCH 3/5] powerpc/powernv: Avoid do complete reset for twice Gavin Shan
2014-11-24 22:38 ` [PATCH 4/5] powerpc/powernv: Issue fundamental reset if required Gavin Shan
2014-11-24 22:38 ` [PATCH 5/5] powerpc/powernv: Drop opal_pci_reinit() Gavin Shan
2014-11-25 22:54 ` [PATCH v1 0/5] powerpc/pci: PCI slot unified reset Benjamin Herrenschmidt
2014-11-26 0:04 ` Gavin Shan [this message]
2014-12-04 5:25 ` Gavin Shan
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=20141126000451.GA21271@shangw \
--to=gwshan@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).