From: Mike Qiu <qiudayu@linux.vnet.ibm.com>
To: kvm-ppc@vger.kernel.org
Cc: Mike Qiu <qiudayu@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, gwshan@linux.vnet.ibm.com
Subject: [PATCH] Bugfix: powerpc/eeh: Create eeh sysfs entry in post_init()
Date: Tue, 24 Jun 2014 23:32:07 -0400 [thread overview]
Message-ID: <1403667127-1622-1-git-send-email-qiudayu@linux.vnet.ibm.com> (raw)
Eeh sysfs entry created must be after EEH_ENABLED been set
in eeh_subsystem_flags.
In PowerNV platform, it try to create sysfs entry before
EEH_ENABLED been set, when boot up. So nothing will be
created for eeh in sysfs.
Signed-off-by: Mike Qiu <qiudayu@linux.vnet.ibm.com>
---
arch/powerpc/platforms/powernv/eeh-ioda.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/powerpc/platforms/powernv/eeh-ioda.c b/arch/powerpc/platforms/powernv/eeh-ioda.c
index 8ad0c5b..5f95581 100644
--- a/arch/powerpc/platforms/powernv/eeh-ioda.c
+++ b/arch/powerpc/platforms/powernv/eeh-ioda.c
@@ -136,6 +136,9 @@ static int ioda_eeh_post_init(struct pci_controller *hose)
struct pnv_phb *phb = hose->private_data;
int ret;
+ /* Creat sysfs after EEH_ENABLED been set */
+ eeh_add_sysfs_files(hose->bus);
+
/* Register OPAL event notifier */
if (!ioda_eeh_nb_init) {
ret = opal_notifier_register(&ioda_eeh_nb);
--
1.8.1.4
next reply other threads:[~2014-06-25 3:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 3:32 Mike Qiu [this message]
2014-06-25 5:33 ` [PATCH] Bugfix: powerpc/eeh: Create eeh sysfs entry in post_init() Gavin Shan
2014-06-25 6:23 ` Wei Yang
2014-06-25 6:37 ` Gavin Shan
2014-06-25 7:27 ` Mike Qiu
2014-06-26 0:12 ` Gavin Shan
2014-06-26 6:34 ` Mike Qiu
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=1403667127-1622-1-git-send-email-qiudayu@linux.vnet.ibm.com \
--to=qiudayu@linux.vnet.ibm.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--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).