From: benh@kernel.crashing.org
To: <frowand@mvista.com>, <trini@mvista.com>,
<linuxppc-dev@lists.linuxppc.org>
Cc: <frowand@mvista.com>
Subject: Re: linuxppc_2_4_devel patch for enable_irq()
Date: Fri, 1 Feb 2002 01:26:51 +0100 [thread overview]
Message-ID: <20020201002651.19940@mailhost.mipsys.com> (raw)
In-Reply-To: <3C59FDD1.2F290996@mvista.com>
> disable_irq() and enable_irq() do use the depth field to determine when
> to actually re-enable the irq. If enable_irq() is called from within
> the irq handling path then interrupts for that irq may be enabled even
> though the irq handling path thinks that it has disabled them.
>
> I encountered the problem while stress testing an ethernet driver
> error path.
Good catch, I'll see how this can be fixed generically.
Thanks,
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-02-01 0:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 2:30 linuxppc_2_4_devel patch for enable_irq() Frank Rowand
2002-02-01 0:26 ` benh [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=20020201002651.19940@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=frowand@mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@mvista.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).