From: Gavin Shan <gwshan@linux.vnet.ibm.com> To: Wei Yang <weiyang@linux.vnet.ibm.com> Cc: linuxppc-dev@lists.ozlabs.org, Mike Qiu <qiudayu@linux.vnet.ibm.com>, Gavin Shan <gwshan@linux.vnet.ibm.com>, kvm-ppc@vger.kernel.org Subject: Re: [PATCH] Bugfix: powerpc/eeh: Create eeh sysfs entry in post_init() Date: Wed, 25 Jun 2014 16:37:22 +1000 [thread overview] Message-ID: <20140625063721.GA5081@shangw> (raw) In-Reply-To: <20140625062353.GB15078@richard> On Wed, Jun 25, 2014 at 02:23:53PM +0800, Wei Yang wrote: >On Wed, Jun 25, 2014 at 03:33:12PM +1000, Gavin Shan wrote: >>On Tue, Jun 24, 2014 at 11:32:07PM -0400, Mike Qiu wrote: >> >>[ cc Richard ] >> >>>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. >>> >> >>Could you please make the commit log more clear? :-) >> >>I guess the issue is introduced by commit 2213fb1 (" >>powerpc/eeh: Skip eeh sysfs when eeh is disabled"). The >>commit checks EEH is enabled while creating PCI device >>EEH sysfs files. If not, the sysfs files won't be created. >>That's to avoid warning reported during PCI hotplug. >> >>The problem you're reporting (if I understand completely): >>You don't see the sysfs files after the system boots up. >>If it's the case, you probably need following changes in >>arch/powerpc/platforms/powernv/pci.c::pnv_pci_ioda_fixup(). >>Could you have a try with it? >> >>#ifdef CONFIG_EEH >> eeh_probe_mode_set(EEH_PROBE_MODE_DEV); >>- eeh_addr_cache_build(); >> eeh_init(); >>+ eeh_addr_cache_build(); >>#endif >> > >I think this is a more proper fix. > >BTW, I have one confusion in this mode set. > >eeh_init() > -> eeh_ops->dev_probe() > -> powernv_eeh_dev_probe() > -> eeh_set_enable(true) <- here the eeh is marked enabled > >We can see this flag would be set for each pci_dev. So is it possible to make >this "set" only once? > It shouldn't be a problem because there might not have PCI devices supporting EEH in the guest. All PCI devices are emulated. >>Eventually PowerNV/pSeries have same function call sequence: >> >>- Set EEH probe mode >>- Doing probe (with device node or PCI device) >>- Build address cache. >> >>>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); Thanks, Gavin
WARNING: multiple messages have this Message-ID (diff)
From: Gavin Shan <gwshan@linux.vnet.ibm.com> To: Wei Yang <weiyang@linux.vnet.ibm.com> Cc: linuxppc-dev@lists.ozlabs.org, Mike Qiu <qiudayu@linux.vnet.ibm.com>, Gavin Shan <gwshan@linux.vnet.ibm.com>, kvm-ppc@vger.kernel.org Subject: Re: [PATCH] Bugfix: powerpc/eeh: Create eeh sysfs entry in post_init() Date: Wed, 25 Jun 2014 06:37:22 +0000 [thread overview] Message-ID: <20140625063721.GA5081@shangw> (raw) In-Reply-To: <20140625062353.GB15078@richard> On Wed, Jun 25, 2014 at 02:23:53PM +0800, Wei Yang wrote: >On Wed, Jun 25, 2014 at 03:33:12PM +1000, Gavin Shan wrote: >>On Tue, Jun 24, 2014 at 11:32:07PM -0400, Mike Qiu wrote: >> >>[ cc Richard ] >> >>>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. >>> >> >>Could you please make the commit log more clear? :-) >> >>I guess the issue is introduced by commit 2213fb1 (" >>powerpc/eeh: Skip eeh sysfs when eeh is disabled"). The >>commit checks EEH is enabled while creating PCI device >>EEH sysfs files. If not, the sysfs files won't be created. >>That's to avoid warning reported during PCI hotplug. >> >>The problem you're reporting (if I understand completely): >>You don't see the sysfs files after the system boots up. >>If it's the case, you probably need following changes in >>arch/powerpc/platforms/powernv/pci.c::pnv_pci_ioda_fixup(). >>Could you have a try with it? >> >>#ifdef CONFIG_EEH >> eeh_probe_mode_set(EEH_PROBE_MODE_DEV); >>- eeh_addr_cache_build(); >> eeh_init(); >>+ eeh_addr_cache_build(); >>#endif >> > >I think this is a more proper fix. > >BTW, I have one confusion in this mode set. > >eeh_init() > -> eeh_ops->dev_probe() > -> powernv_eeh_dev_probe() > -> eeh_set_enable(true) <- here the eeh is marked enabled > >We can see this flag would be set for each pci_dev. So is it possible to make >this "set" only once? > It shouldn't be a problem because there might not have PCI devices supporting EEH in the guest. All PCI devices are emulated. >>Eventually PowerNV/pSeries have same function call sequence: >> >>- Set EEH probe mode >>- Doing probe (with device node or PCI device) >>- Build address cache. >> >>>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); Thanks, Gavin
next prev parent reply other threads:[~2014-06-25 6:37 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-25 3:32 [PATCH] Bugfix: powerpc/eeh: Create eeh sysfs entry in post_init() Mike Qiu 2014-06-25 3:32 ` Mike Qiu 2014-06-25 5:33 ` Gavin Shan 2014-06-25 5:33 ` Gavin Shan 2014-06-25 6:23 ` Wei Yang 2014-06-25 6:23 ` Wei Yang 2014-06-25 6:37 ` Gavin Shan [this message] 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=20140625063721.GA5081@shangw \ --to=gwshan@linux.vnet.ibm.com \ --cc=kvm-ppc@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=qiudayu@linux.vnet.ibm.com \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.