public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <cminyard@mvista.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@transmeta.com>,
	Alan Cox <alan@redhat.com>
Subject: Re: IPMI driver version 19 release
Date: Thu, 03 Apr 2003 10:45:22 -0600	[thread overview]
Message-ID: <3E8C6522.2010208@mvista.com> (raw)
In-Reply-To: <20030403163700.GA13769@gtf.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This only occurs in "run to completion" mode, which is a special mode
the driver goes into after a panic.  This allows the driver to get
messages out during a panic to do things like extend the watchdog timer
and send panic information.

- -Corey

Jeff Garzik wrote:

>On Thu, Apr 03, 2003 at 10:24:02AM -0600, Corey Minyard wrote:
>
>>@@ -563,8 +576,9 @@
>>         spin_lock_irqsave(&(kcs_info->kcs_lock), flags);
>>         result = kcs_event_handler(kcs_info, 0);
>>         while (result != KCS_SM_IDLE) {
>>-            udelay(500);
>>-            result = kcs_event_handler(kcs_info, 500);
>>+            udelay(KCS_SHORT_TIMEOUT_USEC);
>>+            result = kcs_event_handler(kcs_info,
>>+                           KCS_SHORT_TIMEOUT_USEC);
>>         }
>>         spin_unlock_irqrestore(&(kcs_info->kcs_lock), flags);
>>         return;
>
>
>
>Do you really want to udelay this long with interrupts disabled?
>Certainly comments in kcs_event[_handler] indicate you're aware of the
>issue, but the code does not belie this fact :)
>
>Not only is the udelay itself "long" relatively speaking, but it's in a
>loop.  Which also calls a function that contains a loop that is
>potentially infinite is hardware is being wonky.
>
>    Jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+jGUhmUvlb4BhfF4RAp2ZAJ40cXa1O1tv1wITiFzMsTuaTDejEgCfeOzM
Uw0PgpEhlmDkyF9yejO/r4A=
=l5ia
-----END PGP SIGNATURE-----



      reply	other threads:[~2003-04-03 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-03 16:24 IPMI driver version 19 release Corey Minyard
2003-04-03 16:37 ` Jeff Garzik
2003-04-03 16:45   ` Corey Minyard [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=3E8C6522.2010208@mvista.com \
    --to=cminyard@mvista.com \
    --cc=alan@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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