Re: KITLinterruptthread
- From: "ramki_katta via PocketPCJunkies.com" <u45996@uwe>
- Date: Wed, 10 Sep 2008 17:18:19 GMT
Hi Bruce,
Thanks for your reply,
I am executing Idle Time While Sleeping test case to test GetIdletime
implementation
Generally as per msdn GetIdleTime function fails in two cases
1) Any noisy drivers are running in parallel
2) Error in OEMIDLE implementation
In my case I am suspecting second case
What is the general procedure to implement OEMIDLE function
( I mean how can we calculate cpu idle time based on clock ticks)
Please suggest solution, Thanks in advance
Bruce Eitman [eMVP] wrote:
Huh?
The way to achive that would be to kill all of the threads in your system,
or at least cause all of them to block and disable all interrupts to insure
that other threads don't become unblocked. Of course then you won't able to
resume your thread becuase Sleep will not return.
Why would you expect idle time to be so close to the amount of time that a
single thread is blocked?
Hi all,[quoted text clipped - 17 lines]
Iam testing GetIdletime functionality with following code
I want Idletime at least near to sleeptime, how can achive this
please suggest solution
--
Message posted via PocketPCJunkies.com
http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-programming/200809/1
.
- References:
- KITLinterruptthread
- From: ramki_katta
- Re: KITLinterruptthread
- From: Bruce Eitman [eMVP]
- KITLinterruptthread
- Prev by Date: Re: Problem Loading a 3rd party driver into WM6.0
- Next by Date: RE: Test automation for windows CE
- Previous by thread: Re: KITLinterruptthread
- Next by thread: Disable debug messages on serial port.
- Index(es):