From: Andi Kleen <andi@firstfloor.org>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: reason for delay in arch/x86/kernel/traps.c::io_check_error()?
Date: Tue, 10 Mar 2009 04:49:39 +0100 [thread overview]
Message-ID: <20090310034939.GC11935@one.firstfloor.org> (raw)
In-Reply-To: <49B56F18.1050904@nortel.com>
On Mon, Mar 09, 2009 at 01:33:44PM -0600, Chris Friesen wrote:
>
> Hi all,
>
> I was just wondering about the basis for the delay in io_check_error().
> The ICH7 manual doesn't have any mention of a delay being required
> here--is it necessary for other hardware, something not mentioned in the
> manual, or just an accident?
The complete NMI error logging handling does not really apply to any modern
chipset; it's for ancient hardware (286, 386 generation). Those often
needed strange delays too.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-03-10 3:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 19:33 reason for delay in arch/x86/kernel/traps.c::io_check_error()? Chris Friesen
2009-03-10 3:49 ` Andi Kleen [this message]
2009-03-10 15:32 ` Ingo Molnar
2009-03-12 16:20 ` Chris Friesen
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=20090310034939.GC11935@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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