[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1153889791.3984.3.camel@ymzhang-perf.sh.intel.com>
Date: Wed, 26 Jul 2006 12:56:31 +0800
From: "Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>
To: Linas Vepstas <linas@...tin.ibm.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
linux-pci maillist <linux-pci@...ey.karlin.mff.cuni.cz>,
Greg KH <greg@...ah.com>,
Tom Long Nguyen <tom.l.nguyen@...el.com>
Subject: Re: [PATCH 5/5] PCI-Express AER implemetation: pcie_portdrv error
handler
On Tue, 2006-07-25 at 03:37, Linas Vepstas wrote:
> Hi,
>
> Sorry for a late reply...
>
> On Fri, Jul 14, 2006 at 01:35:38PM +0800, Zhang, Yanmin wrote:
> >
> > --- linux-2.6.17/drivers/pci/pcie/portdrv_pci.c 2006-06-22 16:27:35.000000000 +0800
> > +++ linux-2.6.17_aer/drivers/pci/pcie/portdrv_pci.c 2006-06-22 16:46:29.000000000 +0800
> > +
> > +static pci_ers_result_t pcie_portdrv_error_detected(struct pci_dev *dev,
> > + enum pci_channel_state error)
> > +{
> > + /* If fatal, save cfg space for possible link reset at upstream */
> > + if (error == pci_channel_io_frozen)
> > + pcie_portdrv_save_config(dev);
>
> If the channel is frozen, is the config space still readable?
> In my case, I had to save config space data early on before
> the bus error.
You are right.
>
> What's more, I discovered that I had to save the pci config
> space data before device drivers do thier probe. During the probe,
> device drivers will change the config. For example, they'll enable
> interrupts and dma. If you turn these on, and then do the probe,
> you'll get spectacuar failures.
>
> To be safe, I found the best thing to do was to save the pci
> config space state as it was during boot, before the PCI probe
> routines ran.
Thanks. I will try.
>
> --linas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists