[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Delayed Xaction and LOCK#
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: Delayed Xaction and LOCK#
- From: Devendra K Tripathi <tripathi@Synopsys.COM>
- Date: Mon, 26 Aug 1996 12:37:23 -0700
- Resent-Date: Mon, 26 Aug 1996 12:37:23 -0700
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-Id: <"1vW5e3.0.rg5.8rV8o"@dart>
- Resent-Sender: pci-sig-request@znyx.com
Hi all,
There is possibility of deadlock, the way specification for delayed xaction for
exclusive accesses has been specified (PCI2.1 PP 52). It says that target needs to
compare (latched) LOCK# signal to find if request is being repeated. On the other hand
there is no requirement for initiator (PCI 2.1 PP 76) that it must retry
an exclusive access as exculsive access only. I am not clear why matching of LOCK#
is required on target side. I think it should be good enough that target consider
itself locked and do not allow any access other than the pending one. Once the
pending request comes, it should honor irrespective of whether or not the access is
exclusive one.
Any comments ?
Thanks,
Tripathi.
ˆ ¨ ˜