linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: Gavin Shan <gwshan@linux.vnet.ibm.com>
Subject: Re: powerpc/eeh: Disable automatically blocked PCI config
Date: Thu, 20 Aug 2015 09:14:14 +1000 (AEST)	[thread overview]
Message-ID: <20150819231415.0D8B6140783@ozlabs.org> (raw)
In-Reply-To: <1438212411-11368-1-git-send-email-gwshan@linux.vnet.ibm.com>

On Wed, 2015-29-07 at 23:26:51 UTC, Gavin Shan wrote:
> pcibios_set_pcie_reset_state() could be called to complete
> reset request when passing through PCI device, flag
> EEH_PE_ISOLATED is set before saving the PCI config sapce.
> On some Broadcom adapters, EEH_PE_CFG_BLOCKED is automatically
> set when the flag EEH_PE_ISOLATED is marked. It caused bogus
> data saved from the PCI config space, which will be restored
> to the PCI adapter after the reset. Eventually, the hardware
> can't work with corrupted data in PCI config space.
> 
> The patch fixes the issue with eeh_pe_state_mark_no_cfg(), which
> doesn't set EEH_PE_CFG_BLOCKED when seeing EEH_PE_ISOLATED on the
> PE, in order to avoid the bogus data saved and restored to the PCI
> config space.
> 
> Reported-by: Rajanikanth H. Adaveeshaiah <rajanikanth.ha@in.ibm.com>
> Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>

Applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/39bfd715b4837433a86c

cheers

      reply	other threads:[~2015-08-19 23:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 23:26 [PATCH] powerpc/eeh: Disable automatically blocked PCI config Gavin Shan
2015-08-19 23:14 ` Michael Ellerman [this message]

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=20150819231415.0D8B6140783@ozlabs.org \
    --to=mpe@ellerman.id.au \
    --cc=gwshan@linux.vnet.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).