From: Ganesh Goudar <ganeshgr@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id.au
Cc: Ganesh Goudar <ganeshgr@linux.ibm.com>,
oohall@gmail.com, mahesh@linux.ibm.com
Subject: [RFC 0/3] Asynchronous EEH recovery
Date: Tue, 13 Jun 2023 07:13:34 +0530 [thread overview]
Message-ID: <20230613014337.286222-1-ganeshgr@linux.ibm.com> (raw)
Hi,
EEH recovery is currently serialized and these patches shorten
the time taken for EEH recovery by making the recovery to run
in parallel. The original author of these patches is Sam Bobroff,
I have rebased and tested these patches.
On powervm with 64 VFs from same PHB, I see approximately 48%
reduction in time taken in EEH recovery.
On powernv with 9 network cards, Where 2 cards installed on one
PHB and 1 card on each of the rest of the PHBs, Providing 20 PFs
in total. I see approximately 33% reduction in time taken in EEH
recovery.
These patches were originally posted as separate RFCs by Sam, And
I rebased and posted these patches almost a year back, I stopped
pursuing these patches as I was not able test this on powernv, Due
to the issues in drivers of cards I was testing this on, Which are
now resolved. Since I am re-posting this after long time, Posting
this as a fresh RFC, Please comment.
Thanks.
Ganesh Goudar (3):
powerpc/eeh: Synchronization for safety
powerpc/eeh: Provide a unique ID for each EEH recovery
powerpc/eeh: Asynchronous recovery
arch/powerpc/include/asm/eeh.h | 7 +-
arch/powerpc/include/asm/eeh_event.h | 10 +-
arch/powerpc/include/asm/pci-bridge.h | 3 +
arch/powerpc/include/asm/ppc-pci.h | 2 +-
arch/powerpc/kernel/eeh.c | 154 +++--
arch/powerpc/kernel/eeh_driver.c | 580 +++++++++++++++----
arch/powerpc/kernel/eeh_event.c | 71 ++-
arch/powerpc/kernel/eeh_pe.c | 33 +-
arch/powerpc/platforms/powernv/eeh-powernv.c | 12 +-
arch/powerpc/platforms/pseries/eeh_pseries.c | 5 +-
arch/powerpc/platforms/pseries/pci_dlpar.c | 5 +-
drivers/pci/hotplug/pnv_php.c | 5 +-
drivers/pci/hotplug/rpadlpar_core.c | 2 +
drivers/vfio/vfio_iommu_spapr_tce.c | 10 +-
include/linux/mmzone.h | 2 +-
15 files changed, 687 insertions(+), 214 deletions(-)
--
2.40.1
next reply other threads:[~2023-06-13 1:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 1:43 Ganesh Goudar [this message]
2023-06-13 1:43 ` [RFC 1/3] powerpc/eeh: Synchronization for safety Ganesh Goudar
2023-06-13 1:43 ` [RFC 2/3] powerpc/eeh: Provide a unique ID for each EEH recovery Ganesh Goudar
2023-06-13 1:43 ` [RFC 3/3] powerpc/eeh: Asynchronous recovery Ganesh Goudar
2023-06-13 2:36 ` [RFC 0/3] Asynchronous EEH recovery Oliver O'Halloran
2023-07-17 8:10 ` Ganesh G R
-- strict thread matches above, loose matches on Subject: below --
2022-08-16 3:27 Ganesh Goudar
2022-08-17 7:16 ` Oliver O'Halloran
2022-09-02 0:19 ` Jason Gunthorpe
2022-09-15 10:15 ` Ganesh
2023-01-25 14:04 ` Christophe Leroy
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=20230613014337.286222-1-ganeshgr@linux.ibm.com \
--to=ganeshgr@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=oohall@gmail.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).