mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Kay, Allen M" <allen.m.kay@intel.com>
Cc: "linux-pci-owner@vger.kernel.org"
	<linux-pci-owner@vger.kernel.org>,
	"Barnes, Jesse" <jesse.barnes@intel.com>,
	"Wilcox, Matthew R" <matthew.r.wilcox@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"jean.guyader@eu.citrix.com" <jean.guyader@eu.citrix.com>,
	"eric.chanudet@citrix.com" <eric.chanudet@citrix.com>
Subject: Re: [PATCH 1/1][resend]  check for pci bar restore completion and retry
Date: Fri, 27 Jan 2012 11:44:16 -0800	[thread overview]
Message-ID: <20120127114416.2621963a@jbarnes-desktop> (raw)
In-Reply-To: <1327602353-30966-1-git-send-email-allen.m.kay@intel.com>

[-- Attachment #1: Type: text/plain, Size: 540 bytes --]

On Thu, 26 Jan 2012 10:25:53 -0800
"Kay, Allen M" <allen.m.kay@intel.com> wrote:

> On some OEM systems, pci_restore_state() is called while FLR has not yet
> completed.  As a result, PCI BAR register restore is not successful.  This fix
> reads back the restored value and compares it with saved value and re-tries 10
> times before giving up.

Applied, but I don't think I got an answer as to why we don't do this
delay/check when we perform the FLR in the first place?

-- 
Jesse Barnes, Intel Open Source Technology Center

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-01-27 19:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 18:25 Allen Kay
2012-01-27 19:44 ` Jesse Barnes [this message]
2012-02-07 19:49   ` Kay, Allen M

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=20120127114416.2621963a@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=allen.m.kay@intel.com \
    --cc=eric.chanudet@citrix.com \
    --cc=jean.guyader@eu.citrix.com \
    --cc=jesse.barnes@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci-owner@vger.kernel.org \
    --cc=matthew.r.wilcox@intel.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

all inboxes | Powered by JetHome®