18 December 2014, 16:49 | #1 |
Registered User
Join Date: Dec 2014
Location: France
Posts: 104
|
[Suggest] Display FPU: x%
Hi,
In some case i would like to verify if the FPU is in use, for instance to check which apps make use of the fpu, if present, and when. I don't think it's possible atm. Is it feasible ? By the way, as i'm new here, i take the opportunity to thank you for your hard word |
19 December 2014, 10:00 | #2 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,507
|
It can't work very well because AmigaOS task scheduler always uses some FPU instructions (to store/restore FPU context) when FPU is available.
|
19 December 2014, 10:42 | #3 |
Registered User
Join Date: Dec 2014
Location: France
Posts: 104
|
oh, sad. i undestand. no filtering specific task possible ? hmm, complicated, and maybe superslow. ho well...
|
20 December 2014, 18:36 | #4 |
Amiga user since 1990
Join Date: Aug 2004
Location: Kingsport, TN / USA
Age: 44
Posts: 295
|
Wonder if it would be possible within the emulation framework to report similar to CPU usage? That way, it would be understood that standard AOS usage would always report a low percentage, but when running a more FPU-intensive program then it would be obvious based on the percentage that the program itself was making good use of the FPU. Alternately, perhaps a threshold that's high enough to filter out system FPU usage but still be triggered when something more FPU-intensive is running. By FPU-intensive I mean like the countless '881 builds of popular software such as Imagine, VistaPro, etc.
Alternately, maybe it would be possible to use AOS-side software to do this? I know that some software can report CPU usage (I remember this feature from DOpus among others). Perhaps a small piece of AOS software could serve the same purpose? Also alternately, maybe even a combination of AOS software along with host-side code to present the information outside the emulated Amiga window (so that it would be present in the emulation window no matter which screen is frontmost, nor which windows are present on said screen). |
21 December 2014, 15:09 | #5 |
Registered User
Join Date: Dec 2014
Location: France
Posts: 104
|
Yes, maybe amigaos side tool but what toni said about task scheduler will still be true.
|
21 December 2014, 16:02 | #6 |
Registered User
Join Date: Apr 2005
Location: digital hell, Germany, after 1984, but worse
Posts: 3,366
|
The CPU-usage of a task is calculated with the help of the multitasking scheduler. There are sleeping tasks, tasks waiting in the ready state and one running task which is using the CPU for a limited period, a time slice. The scheduler uses the task priorities to decide which of the waiting tasks comes next to get the CPU. So the CPU-usage of a task depends on the time it is in the running state in relation to the overall time.
But there is no FPU scheduler. FPU instructions are just some special commands that the running task can make use of. Of course it would be possible to count the access to any FPU instruction and set it in relation to the standard CPU instruction calls. But this would only make sense for an optional debug mode, because it will probably cause a big slowdown. If you only want to know whether a program uses the FPU then simply disassemble it and scan for the mathlib strings or for FMOVE, FADD, FMUL instructions etc. Use your editor and count the occurrences of these or other Fxxx commands. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Suggest coding stickies! | Photon | Coders. General | 3 | 04 October 2011 08:33 |
Any suggest about cdrom audio out? | piemmeweb | support.Hardware | 13 | 09 October 2009 22:05 |
Suggest KG some arcade style games. | killergorilla | Retrogaming General Discussion | 74 | 06 October 2006 18:52 |
Suggest filetype for Upload files. | whiteb | project.EAB | 1 | 11 June 2006 16:00 |
Suggest some stunning demos! | Jan | request.Demos | 26 | 27 March 2005 18:05 |
|
|