From: "H. Peter Anvin" <hpa@zytor.com>
To: root@chaos.analogic.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: IO delay, port 0x80, and BIOS POST codes
Date: Thu, 14 Mar 2002 14:20:23 -0800 [thread overview]
Message-ID: <3C912227.3080806@zytor.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1020314165931.715A-100000@chaos.analogic.com>
Richard B. Johnson wrote:
>
> Yeh? Then "how do it know?". It doesn't. I/O instructions are ordered,
> however, that's all. There is no bus-interface state machine that exists
> except on the addressed device. The CPU driven interface device just
> makes sure that the data is valid before the address and I/O-read or
> I/O-write are valid after this. The address is decoded by the device
> and is used to enable the device. It either puts its data onto the
> bus in the case of a read, or gets data off the bus, in the case of
> a write. The interface timing is specified and is handled by hardware.
> In the meantime the CPU has not waited because there is nothing to
> wait for. On a READ, if the device cannot put its data on the bus
> fast enough, it puts its finger io IO-chan-ready. This forces the
> CPU (through its bus-interface) to wait.
>
> Writes to nowhere are just that, writes to nowhere.
>
On the ISA bus, yes. The PCI and front side busses will be held in wait
until the transaction is completed.
The exact requirement is a bit more complicated, something along the
lines of "an SMI triggered in response to an OUT will be taken before
the OUT is retired."
-hpa
next prev parent reply other threads:[~2002-03-14 22:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 17:11 IO delay, port 0x80, and BIOS POST codes 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2002-03-14 18:18 Thunder from the hill
2002-03-15 11:46 ` Martin Wilck
[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
2002-03-15 15:07 Thunder from the hill
2002-03-15 17:39 Gerald Champagne
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=3C912227.3080806@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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