linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Kim Phillips <kim.phillips@freescale.com>
Cc: Wang Dongsheng <dongsheng.wang@freescale.com>,
	linux-kernel@vger.kernel.org,
	Himangi Saraogi <himangi774@gmail.com>,
	Anton Blanchard <anton@samba.org>,
	Paul Mackerras <paulus@samba.org>,
	Aaron Sierra <asierra@xes-inc.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/fsl_pci: Fix pci stack build bug with FRAME_WARN
Date: Thu, 22 Jan 2015 18:43:45 -0600	[thread overview]
Message-ID: <1421973825.4961.253.camel@freescale.com> (raw)
In-Reply-To: <20150122182056.cc3436bd90a6cbba70da538a@freescale.com>

On Thu, 2015-01-22 at 18:20 -0600, Kim Phillips wrote:
> On Wed, 21 Jan 2015 21:02:27 -0600
> Scott Wood <scottwood@freescale.com> wrote:
> 
> > On Wed, 2015-01-21 at 20:48 -0600, Kim Phillips wrote:
> > > fake_pci_bus()' version is static, so it's not on the stack.
> > > 
> > > given that, maybe fsl_pcie_check_link()'s should be static too?
> > 
> > Oh.  How would you ensure that it's only called once at a time?  It
> > doesn't look like this is only called during early boot.
> > fsl_pcie_check_link() is called every time we do any config read through
> > the normal interface.  This is also a concern for the call to
> > early_read_config_dword().
> 
> I really don't know how that works: that code has been there since
> before linux was maintained in git.

Regardless, now that it's been noticed we should figure it out.
fsl_pcie_check_link() is using the early_*() functions in a context that
is not early and thus appears to be breaking the assumption that
fake_pci_bus() makes.

fsl_pcie_check_link() is fairly recent, FWIW.

> Below is the v2.

Please send as a standalone patch so I don't have to edit all the
discussion out of the commit message.

-Scott

  reply	other threads:[~2015-01-23  0:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 20:03 [PATCH] powerpc/fsl_pci: Fix pci stack build bug with FRAME_WARN Kim Phillips
2015-01-21  0:31 ` Scott Wood
2015-01-22  2:48   ` Kim Phillips
2015-01-22  3:02     ` Scott Wood
2015-01-23  0:20       ` Kim Phillips
2015-01-23  0:43         ` Scott Wood [this message]
2015-01-23  1:05           ` [PATCH v2] " Kim Phillips

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=1421973825.4961.253.camel@freescale.com \
    --to=scottwood@freescale.com \
    --cc=anton@samba.org \
    --cc=asierra@xes-inc.com \
    --cc=dongsheng.wang@freescale.com \
    --cc=himangi774@gmail.com \
    --cc=kim.phillips@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.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).