[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Reading BAR0 under WindowsNT
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: Re: Reading BAR0 under WindowsNT
- From: Alan Deikman <alan@znyx.com>
- Date: Fri, 13 Jun 1997 10:51:26 -0700
- Resent-Date: Fri, 13 Jun 1997 10:51:26 -0700
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-Id: <"N-I3k3.0.1e5.QhOep"@dart>
- Resent-Sender: pci-sig-request@znyx.com
>I have written some code that tries to determine the PCI memory
>usage. It does this by going through all the devices and reading each
>BAR, then writing 0xffffffff to each bar and reading it again to
>determine the size. Finally the original BAR value read is written
>back.
Sounds to me like a real good start on a truly nasty Trojan Horse
application. I hope you have found out how to fully lock out
all interrupts during those last three steps!
Even so I would strongly advise the user to re-boot his system
after running such an application.
--------------------------------
Alan Deikman, ZNYX Corporation
alan@znyx.com
º | k