Article View: comp.sys.intel
Article #1684Re: how long is a bus-lock?
From: Bob-B
Date: Tue, 01 Dec 1987 08:01
Date: Tue, 01 Dec 1987 08:01
30 lines
1434 bytes
1434 bytes
>When the bus-lock prefix is asserted (either explicitly, or as an >automatic result of XCHG), how many interlocked bus-cycle are >possible before the locking expires? in particular, can a misaligned >LOCK STOSD instruction cause the 386 to write twice to memory in >interlocked fashion? how many bus-transactions are interlocked on a >misaligned LOCK MOVSD? God only knows. :-) In theory, though, a LOCK STOSD or LOCK MOVSD would cause an '86 processor to lock the buss for the entire length of the buss transaction. That is, if STOSD were to execute with one write, the LOCK would be just for that period. But, if the STOSD was to a misaligned place, the LOCK would be just extended ... it would cover both writes. ----- done help page forward back skip add_article unsubscribe transfer rotate oommand: SCREEN DUMP ANSI-BBS FDX 1200 N81 LOG CLOSED PRT OFF CR CR
Technical Details
Message-ID:
<1697@cup.portal.com>Path:
arc1-ca.pugleaf.net!utzoo!mnetor!uunet!portal!cup.portal.com!Bob-BReferences:
<404@taux01.UUCP>Show Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: arc1-ca.pugleaf.net!utzoo!mnetor!uunet!portal!cup.portal.com!Bob-B From: Bob-B@cup.portal.com Newsgroups: comp.sys.intel Subject: Re: how long is a bus-lock? Message-ID: <1697@cup.portal.com> Date: Tue, 1-Dec-87 03:01:33 EST Article-I.D.: cup.1697 Posted: Tue Dec 1 03:01:33 1987 Date-Received: Fri, 4-Dec-87 03:24:51 EST References: <404@taux01.UUCP> Organization: The Portal System (TM) Lines: 29 XPortal-User-Id: 1.1001.2401