[ros-bugs] [Bug 4600] New: HalpCalibrateStallExecution not implemented
ReactOS.Bugzilla at www.reactos.org
ReactOS.Bugzilla at www.reactos.org
Fri Jun 12 14:27:38 CEST 2009
http://www.reactos.org/bugzilla/show_bug.cgi?id=4600
Summary: HalpCalibrateStallExecution not implemented
Product: ReactOS
Version: TRUNK
Platform: x86 Hardware
OS/Version: ReactOS
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: Kernel
AssignedTo: ros-bugs at reactos.org
ReportedBy: netzimme at aim.com
QAContact: ros-bugs at reactos.org
The function HalpCalibrateStallExecution() is not implemented and so
the internal tick count (Pcr->StallScaleFactor) for the function
KeStallExecutionProcessor() is always the same. This can see in
HalInitializeProcessor() where Pcr->StallScaleFactor set to INITIAL_STALL_COUNT
(64).
So KeStallExecutionProcessor() has difference runs on difference cpus.
In my case i have a 3Com 3c905CX TX-M network card. The driver try
to initialize in this way:
out ioport,value
KeStallExecutionProcessor(10)
in value,ioport
if (value != 0) return error
my test computer have a 1GHz CPU so that the tick count 64 is to fast.
It should be ca. 500 to stall the cpu for 10 usec. Otherwise the ioport will
not toggled to the expected value for the driver.
The function HalpCalibrateStallExecution() was removed in rev. 24964 with
the comment that it will be implemented at a later moment :-)
Daniel Zimmermann
--
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the Ros-bugs
mailing list