From: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
To: Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 1/2] powerpc: add refcount to struct pci_controller
Date: Wed, 10 Aug 2016 09:03:52 -0300 [thread overview]
Message-ID: <d1fd4576-8011-45b5-0bf8-0b1045e932db@linux.vnet.ibm.com> (raw)
In-Reply-To: <5c42993e-208e-34a5-0d5e-48d9df86fa49@au1.ibm.com>
On 08/09/2016 10:45 PM, Andrew Donnellan wrote:
>> [snip] Notably, only
>> the pseries platform calls pcibios_free_controller() for some purpose
>> other than to release the pci_controller in case of errors just after
>> the call to pcibios_alloc_controller() (i.e., 'goto error' scenarios).
>
> cxl's vPHB API also uses pcibios_free_controller() [snip]
Cool. I see I missed this report line from grep; thanks. I was mostly
biased at arch/powerpc/ and driver/pci/ these days.
> I'm currently working on a cxl defect found by an IBM test team where we
> run into this - will review this patch more thoroughly and test it shortly.
That's great; thanks!
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
next prev parent reply other threads:[~2016-08-10 12:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 0:44 [PATCH v2 0/2] powerpc: fix oops in pcibios_release_device() after pcibios_free_controller() Mauricio Faria de Oliveira
2016-08-10 0:44 ` [PATCH v2 1/2] powerpc: add refcount to struct pci_controller Mauricio Faria de Oliveira
2016-08-10 1:45 ` Andrew Donnellan
2016-08-10 12:03 ` Mauricio Faria de Oliveira [this message]
2016-08-10 13:53 ` Mauricio Faria de Oliveira
2016-08-10 21:46 ` Mauricio Faria de Oliveira
2016-08-10 0:44 ` [PATCH v2 2/2] powerpc: update pci_controller.refcount for PCI devices and buses Mauricio Faria de Oliveira
2016-08-10 3:35 ` Andrew Donnellan
2016-08-10 12:30 ` Mauricio Faria de Oliveira
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=d1fd4576-8011-45b5-0bf8-0b1045e932db@linux.vnet.ibm.com \
--to=mauricfo@linux.vnet.ibm.com \
--cc=andrew.donnellan@au1.ibm.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).