[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060726164246.GE9871@suse.de>
Date: Wed, 26 Jul 2006 09:42:46 -0700
From: Greg KH <gregkh@...e.de>
To: "Michael S. Tsirkin" <mst@...lanox.co.il>
Cc: linux-kernel@...r.kernel.org, openib-general@...nib.org,
Roland Dreier <rolandd@...co.com>,
Justin Forbes <jmforbes@...uxtx.org>,
Zwane Mwaikambo <zwane@....linux.org.uk>,
Theodore Ts'o <tytso@....edu>,
Randy Dunlap <rdunlap@...otime.net>,
Dave Jones <davej@...hat.com>,
Chuck Wolber <chuckw@...ntumlinux.com>,
Chris Wedgwood <reviews@...cw.f00f.org>, torvalds@...l.org,
akpm@...l.org, alan@...rguk.ukuu.org.uk,
Chris Wright <chrisw@...s-sol.org>
Subject: Re: restore missing PCI registers after reset
On Wed, Jul 26, 2006 at 07:32:26PM +0300, Michael S. Tsirkin wrote:
> Quoting r. Greg KH <gregkh@...e.de>:
> > I think pci_restore_state() already restores the msi and msix state,
> > take a look at the latest kernel version :)
>
> Yes, I know :)
> but I am not talking abotu MSI/MSI-X, I am talking about the following:
> > > > PCI-X device: PCI-X command register
> > > > PCI-X bridge: upstream and downstream split transaction registers
> > > > PCI Express : PCI Express device control and link control registers
>
> these register values include maxumum MTU for PCI express and other vital
> data.
Make up a patch that shows how you would save these in a generic way and
we can discuss it. I know people have talked about saving the extended
PCI config space for devices that need it, so that might be all you
need to do here.
thanks,
greg k-h
-
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