From: Mike Mason <mmlnx@us.ibm.com>
To: michael@ellerman.id.au
Cc: linuxppc-dev@ozlabs.org, linasvepstas@gmail.com, paulus@samba.org
Subject: Re: [PATCH] Only disable/enable LSI interrupts in EEH
Date: Thu, 12 Feb 2009 08:06:51 -0800 [thread overview]
Message-ID: <4994491B.2090306@us.ibm.com> (raw)
In-Reply-To: <1234309181.8323.12.camel@localhost>
Michael Ellerman wrote:
> On Tue, 2009-02-10 at 13:12 -0800, Mike Mason wrote:
>> I'm resubmitting this patch with a couple changes
>> suggested by Michael Ellerman. 1) the new functions
>> should be static, and 2) some people may object to
>> including unrelated formating changes.
>>
>> =========================================================
>>
>> The EEH code disables and enables interrupts during the
>> device recovery process. This is unnecessary for MSI
>> and MSI-X interrupts because they are effectively disabled
>> by the DMA Stopped state when an EEH error occurs. The
>> current code is also incorrect for MSI-X interrupts. It
>> doesn't take into account that MSI-X interrupts are tracked
>> in a different way than LSI/MSI interrupts. This patch
>> ensures only LSI interrupts are disabled/enabled.
>>
>> Signed-off-by: Mike Mason <mmlnx@us.ibm.com>
>> Acked-by: Linas Vepstas <linasvepstas@gmail.com>
>
>
> Looks good. Assuming you've tested it :)
Yes, it's been tested with network devices that use LSI, MSI and MSI-X interrupts. All recovered fine.
>
> Acked-by: Michael Ellerman <michael@ellerman.id.au>
>
>
prev parent reply other threads:[~2009-02-12 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 3:07 [PATCH] Only disable/enable LSI interrupts in EEH Mike Mason
2009-02-10 17:14 ` Linas Vepstas
2009-02-10 23:38 ` Michael Ellerman
2009-02-10 23:46 ` Linas Vepstas
2009-02-10 21:12 ` Mike Mason
2009-02-10 23:39 ` Michael Ellerman
2009-02-12 16:06 ` Mike Mason [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=4994491B.2090306@us.ibm.com \
--to=mmlnx@us.ibm.com \
--cc=linasvepstas@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=paulus@samba.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).