From: Andi Kleen <ak@suse.de>
To: Martin Wilck <Martin.Wilck@fujitsu-siemens.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: IO delay, port 0x80, and BIOS POST codes
Date: Fri, 15 Mar 2002 13:52:40 +0100 [thread overview]
Message-ID: <20020315135240.A5979@wotan.suse.de> (raw)
In-Reply-To: <p73lmcuyrov.fsf@oldwotan.suse.de> <Pine.LNX.4.33.0203151347110.1477-100000@biker.pdb.fsc.net>
In-Reply-To: <Pine.LNX.4.33.0203151347110.1477-100000@biker.pdb.fsc.net>
On Fri, Mar 15, 2002 at 01:47:39PM +0100, Martin Wilck wrote:
> On 15 Mar 2002, Andi Kleen wrote:
>
> > > It doesn't even have to be a config option - a line
> > >
> > > /* Port used for dummy writes for I/O delays */
> > > /* Change this only if you know what you're doing ! */
> > > #define DUMMY_IO_PORT 0x80
> > >
> > > in a header file would perfectly suffice.
> >
> > That effectively already exists. You just need to change the __SLOW_DOWN_IO
> > macro in include/asm-i387/io.h
>
> No, that doesn't cover all accesses to port 80. I am still searching.
It should. I would consider all other accesses a bug.
It is possible that some driver used it for private debugging and left it in by
mistake. These should be removed.
-Andi
next prev parent reply other threads:[~2002-03-15 12:53 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C90E983.5AC769B8@ngforever.de.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.33.0203151243430.1477-100000@biker.pdb.fsc.net.suse.lists.linux.kernel>
2002-03-15 11:51 ` Andi Kleen
2002-03-15 12:47 ` Martin Wilck
2002-03-15 12:52 ` Andi Kleen [this message]
2002-03-15 17:41 ` [PATCH] Cleanup port 0x80 use (was: Re: IO delay ...) Martin Wilck
2002-03-15 18:05 ` Alan Cox
2002-03-15 20:41 ` H. Peter Anvin
2002-03-15 21:33 ` Linus Torvalds
2002-03-15 21:37 ` Alan Cox
2002-03-16 0:01 ` H. Peter Anvin
2002-03-15 18:57 ` Andreas Dilger
2002-03-15 20:17 ` Martin Wilck
2002-03-17 2:01 ` Jamie Lokier
2002-03-18 9:18 ` Martin Wilck
2002-03-18 9:39 ` Keith Owens
2002-03-18 11:20 ` Martin Wilck
2002-03-18 15:22 ` Jamie Lokier
2002-03-15 17:39 IO delay, port 0x80, and BIOS POST codes Gerald Champagne
-- strict thread matches above, loose matches on Subject: below --
2002-03-15 15:07 Thunder from the hill
2002-03-14 18:18 Thunder from the hill
2002-03-15 11:46 ` Martin Wilck
2002-03-14 17:11 Martin Wilck
2002-03-14 17:54 ` Richard B. Johnson
2002-03-14 18:10 ` Alan Cox
2002-03-14 19:23 ` Linus Torvalds
2002-03-14 19:46 ` H. Peter Anvin
2002-03-14 20:43 ` John Heil
2002-03-14 21:03 ` Richard B. Johnson
2002-03-14 21:19 ` Pedro M. Rodrigues
2002-03-14 21:26 ` John Heil
2002-03-14 21:41 ` Richard B. Johnson
2002-03-14 21:26 ` Linus Torvalds
2002-03-14 21:44 ` Richard B. Johnson
2002-03-14 21:56 ` H. Peter Anvin
2002-03-14 22:11 ` Richard B. Johnson
2002-03-14 22:20 ` H. Peter Anvin
2002-03-14 22:25 ` Richard B. Johnson
2002-03-14 22:58 ` Alan Cox
2002-03-14 22:56 ` Alan Cox
2002-03-14 21:11 ` H. Peter Anvin
2002-03-14 21:24 ` Linus Torvalds
2002-03-14 21:57 ` H. Peter Anvin
2002-03-14 22:06 ` John Heil
2002-03-14 22:55 ` Alan Cox
2002-03-14 22:39 ` John Heil
2002-03-14 23:29 ` Alan Cox
2002-03-15 0:12 ` David Golden
2002-03-15 0:11 ` John Heil
2002-03-19 14:25 ` Pavel Machek
2002-03-15 11:30 ` Eric W. Biederman
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=20020315135240.A5979@wotan.suse.de \
--to=ak@suse.de \
--cc=Martin.Wilck@fujitsu-siemens.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®