From: Oliver O'Halloran <oohall@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: EEH cleanups and reworks
Date: Thu, 10 Sep 2020 15:45:23 +1000 [thread overview]
Message-ID: <20200910054532.2043724-1-oohall@gmail.com> (raw)
This is really two series joined together since they end up conflicting
with each other lighty slightly and I figured this is easier for all
involved.
Patches 1-5 streamline how the generic and platform specfic parts of EEH
are initialised at boot so more of the setup process happens in linear code
rather in initcalls.
Patches 6-9 re-work how the per-device EEH probing works on pseries to
make it line up better with the process outlined in PAPR. It also
removes the pe->config_addr field which has always confused me since
it's not really clear what or why it's needed (spoiler: it's not).
Oliver
next reply other threads:[~2020-09-10 5:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 5:45 Oliver O'Halloran [this message]
2020-09-10 5:45 ` [PATCH 1/9] powerpc/eeh: Rework EEH initialisation Oliver O'Halloran
2020-09-10 5:45 ` [PATCH 2/9] powerpc/powernv: Stop using eeh_ops->init() Oliver O'Halloran
2020-09-10 5:45 ` [PATCH 3/9] powerpc/pseries: " Oliver O'Halloran
2020-09-10 5:45 ` [PATCH 4/9] powerpc/eeh: Delete eeh_ops->init Oliver O'Halloran
2020-09-10 5:45 ` [PATCH 5/9] powerpc/eeh: Move EEH initialisation to an arch initcall Oliver O'Halloran
2020-09-10 5:45 ` [PATCH 6/9] powerpc/pseries/eeh: Clean up pe_config_addr lookups Oliver O'Halloran
2020-09-10 5:45 ` [PATCH 7/9] powerpc/pseries/eeh: Rework device EEH PE determination Oliver O'Halloran
2020-09-10 5:45 ` [PATCH 8/9] powerpc/pseries/eeh: Allow zero to be a valid PE configuration address Oliver O'Halloran
2020-09-10 5:45 ` [PATCH 9/9] powerpc/eeh: Clean up PE addressing Oliver O'Halloran
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=20200910054532.2043724-1-oohall@gmail.com \
--to=oohall@gmail.com \
--cc=linuxppc-dev@lists.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).