From: linas@austin.ibm.com (Linas Vepstas)
To: Wen Xiong <wenxiong@us.ibm.com>
Cc: "Kok, Auke" <auke-jan.h.kok@intel.com>,
"David S. Miller" <davem@davemloft.net>,
linux-pci@atrey.karlin.mff.cuni.cz, mcarlson@broadcom.com,
mchan@broadcom.com, netdev@vger.kernel.org
Subject: Re: [PATCH] PCI: export pci_restore_msi_state()
Date: Fri, 9 Nov 2007 10:42:39 -0600 [thread overview]
Message-ID: <20071109164239.GK4239@austin.ibm.com> (raw)
In-Reply-To: <OFD31717CC.A38DF9AF-ON8725738E.00069FB3-8625738E.00077F2A@us.ibm.com>
On Thu, Nov 08, 2007 at 07:21:01PM -0600, Wen Xiong wrote:
> Hi Linas,
>
> I saw you have submitted several patches to support pci-express network
> adapters EEH. But looks only this patch fixed something in linux kernel
> code.
And its an old patch, submitted long ago ... I've resubmitted, because
it seems that its the best/most correct thing to do.
> Do you mean I can test EEH callback functions in device driver after I
> apply this patch in the kernel?
Yes, please. Note, however, I was never able to make the pci-e
version of the e1000 work. It comes up, generates interrupts, and
registeres are readable and writeable. But it behvaes as if the PHY
is turned off -- no network traffic goes thorugh. (I tried turning
PHY on explicitly; that didn't help). So there is still something
wrong somewhere, probably in the e1000 deice driver. I'm guessing
the pci-e to pci-x bridge chip on that card is not quite resetting
the card completely.
> Do you do "pci_save_msi_state" somewhere in the kernel? Or you suggest to
> do "pci_save_msi_state" and "pci_restore_msi_state" in each device driver?
There is no "save state", the msi state can't be saved. The MSI regs
are write-only, and they are controlled by firmware. The restore_state
function is the only one you need.
--linas
prev parent reply other threads:[~2007-11-09 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 21:43 [PATCH] PCI: export pci_restore_msi_state() Linas Vepstas
2007-11-07 22:07 ` Linas Vepstas
[not found] ` <OFD31717CC.A38DF9AF-ON8725738E.00069FB3-8625738E.00077F2A@us.ibm.com>
2007-11-09 16:42 ` Linas Vepstas [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=20071109164239.GK4239@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=auke-jan.h.kok@intel.com \
--cc=davem@davemloft.net \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=mcarlson@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=wenxiong@us.ibm.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;
as well as URLs for NNTP newsgroup(s).