All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bjorn Helgaas <helgaas@kernel.org>,
	Juan Alvarez <jjalvare@linux.vnet.ibm.com>
Cc: "Bryant G. Ly" <bryantly@linux.vnet.ibm.com>,
	paulus@samba.org, mpe@ellerman.id.au, seroyer@linux.vnet.ibm.com,
	alex.williamson@redhat.com, aik@ozlabs.ru, ruscur@russell.cc,
	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: Fri, 29 Dec 2017 11:02:38 +1100	[thread overview]
Message-ID: <1514505758.2743.101.camel@kernel.crashing.org> (raw)
In-Reply-To: <20171228232253.GC19819@bhelgaas-glaptop.roam.corp.google.com>

On Thu, 2017-12-28 at 17:22 -0600, Bjorn Helgaas wrote:
> Both paths end up calling the pci_error_handlers.error_detected()
> hook.
> 
> Drivers are not supposed to care what arch they're running on.  If the
> driver supplies an .error_detected() entry point, it's up to the PCI
> core and powerpc code to use it consistently across arches.  That
> means the same uevents (if any) should be emitted from both paths.
> 
> The best way would be to unify the call of .error_detected() so the
> AER path and the powerpc path do it via the same function.  The AER
> report_error_detected() and the powerpc eeh_report_error() do look
> fairly similar, so this seems possible in principle, but I'm not
> holding my breath.

Factoring these callers into a common function that can then do the
uevent for errors makes a lot of sense.

The "resume" path might be trickier, but even then, rather than calling
directly the driver op, it would be easy to have a little wrapper that
does it, which can then also do the uevent.

Ben.

  reply	other threads:[~2017-12-29  0:02 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
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 [this message]
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=1514505758.2743.101.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=bodong@mellanox.com \
    --cc=bryantly@linux.vnet.ibm.com \
    --cc=eli@mellanox.com \
    --cc=gabriele.paoloni@huawei.com \
    --cc=helgaas@kernel.org \
    --cc=jjalvare@linux.vnet.ibm.com \
    --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 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.