From: Juan Alvarez <jjalvare@linux.vnet.ibm.com>
To: Russell Currey <ruscur@russell.cc>,
Bjorn Helgaas <helgaas@kernel.org>,
"Bryant G. Ly" <bryantly@linux.vnet.ibm.com>
Cc: benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
seroyer@linux.vnet.ibm.com, alex.williamson@redhat.com,
aik@ozlabs.ru, linux-pci@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, bodong@mellanox.com,
eli@mellanox.com, saeedm@mellanox.com,
Keith Busch <keith.busch@intel.com>,
Gabriele Paoloni <gabriele.paoloni@huawei.com>,
Dongdong Liu <liudongdong3@huawei.com>
Subject: Re: [PATCH v2 2/7] powerpc/kernel: Add uevents in EEH error/resume
Date: Wed, 20 Dec 2017 21:04:10 -0600 [thread overview]
Message-ID: <cb6afad3-b0f9-f60c-eeaf-7f0aec88f7ef@linux.vnet.ibm.com> (raw)
In-Reply-To: <1513659576.2151.6.camel@russell.cc>
On 12/18/17 10:59 PM, Russell Currey wrote:
> On Mon, 2017-12-18 at 22:50 -0600, Bjorn Helgaas wrote:
>> [+cc Keith, Gabriele, Dongdong]
>>
>> On Mon, Dec 18, 2017 at 04:38:03PM -0600, Bryant G. Ly wrote:
>>> Devices can go offline when EEH is reported. This patch adds
>>> a change to the kernel object and lets udev know of error.
>>> When device resumes a change is also set reporting device as
>>> online. Therefore, EEH events are better propagated to user
>>> space for devices in powerpc arch.
>> I'm on vacation and can't review this in detail, but I wonder if you
>> can compare this with the uevents we emit for DPC, AER, and hotplug
>> events (if any). I hope we don't end up with userspace having to be
>> aware of the differences between EEH, DPC, AER, etc.
>>
>> From a very quick look, I only see a few uevents even mentioned in
>> drivers/pci: KOBJ_ADD in __pci_hp_register() and KOBJ_CHANGE in the
>> SR-IOV code. I'm worried that we're missing some important uevents
>> in
>> the PCI core.
The only place where I see the KOBJ_REMOVE being used is when the device is
removed in pci_destroy_dev -> device_del whic will be called implicitly
in permanent failure path of EEH code
>> That's not an argument against what you're doing here;
>> it just would be nice to fill in any missing pieces in the core also,
>> and hopefully make them consistent with these EEH events.
> I don't think this needs to be particularly complex, could we get away
> with events for when devices do the following?
>
> - begin recovery
> - successfully recover
> - fail recovery
If there are no objections in the on going review of this patch
I can change them to these names:
- BEGIN_RECOVERY
- SUCCESSFUL_RECOVERY
- FAILED_RECOVERY
>
> It might be worthwhile sorting out some consistent, non-EEH-specific
> naming, and then other device error recovery systems can do the same
> later.
>
Do you have a more consistent naming in mind for these events?
- Juan
next prev parent reply other threads:[~2017-12-21 3:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 22:38 [PATCH v1 0/7] SR-IOV Enablement on PowerVM Bryant G. Ly
2017-12-18 22:38 ` [PATCH v2 1/7] platform/pseries: Update VF config space after EEH Bryant G. Ly
2017-12-18 22:38 ` [PATCH v2 2/7] powerpc/kernel: Add uevents in EEH error/resume Bryant G. Ly
2017-12-19 4:50 ` Bjorn Helgaas
2017-12-19 4:59 ` Russell Currey
2017-12-21 3:04 ` Juan Alvarez [this message]
2017-12-19 6:27 ` Benjamin Herrenschmidt
2017-12-21 3:04 ` Juan Alvarez
2017-12-28 23:22 ` Bjorn Helgaas
2017-12-29 0:02 ` Benjamin Herrenschmidt
2017-12-18 22:38 ` [PATCH v2 3/7] platforms/pseries: Set eeh_pe of EEH_PE_VF type Bryant G. Ly
2017-12-18 22:38 ` [PATCH v2 4/7] powerpc/kernel Add EEH operations to notify resume Bryant G. Ly
2017-12-18 22:38 ` [PATCH v2 5/7] powerpc/kernel: Add EEH notify resume sysfs Bryant G. Ly
2017-12-18 22:38 ` [PATCH v2 6/7] pseries/pci: Associate PEs to VFs in configure SR-IOV Bryant G. Ly
2017-12-18 22:38 ` [PATCH v2 7/7] pseries/setup: Add Initialization of VF Bars Bryant G. Ly
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=cb6afad3-b0f9-f60c-eeaf-7f0aec88f7ef@linux.vnet.ibm.com \
--to=jjalvare@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=bodong@mellanox.com \
--cc=bryantly@linux.vnet.ibm.com \
--cc=eli@mellanox.com \
--cc=gabriele.paoloni@huawei.com \
--cc=helgaas@kernel.org \
--cc=keith.busch@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liudongdong3@huawei.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=ruscur@russell.cc \
--cc=saeedm@mellanox.com \
--cc=seroyer@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: 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).