Re: Supervisor mode & multitasking

["Petr Stehlik" <pstehlik@zln.cz>]

>> >Yes, it may be. But sometimes it may be nice to have an option to
>> >write/run a program, which takes an advantage of being the only task in
>> >the system to utilize the full processing power of the CPU. As the
>>
>> I don't agree. We should improve MiNT scheduling so a time intensive task
>> will  get 97% (or more) of CPU power. Then, you wouldn't need to switch
to
>> singlemode.
>
>It's almost the same, as 3% of the 68030 processing power won't be
>sufficient for almost anything. Anyways, I have an impression that MiNT
>scheduler can't be improved to a big extent (like twice as fast).

How much time is stolen by background tasks in current, fully loaded MiNTOS
setup? I would say it's less than 10%. And with better prioritization there
shouldn't be real difference between processing power of CPU under TOS and
MiNT.

As for the 3% number - the point is to get enough time to the actual
application automatically, without any system call for stopping
multitasking.

>Pure Debugger doesn't work on 040? :)) Aren't those your own words, that
>"everything works on Afterburner"? :)) So, what else is not "everything"?

programs that play directly with 68030 MMU or special 68030 CPU registers
usually do not run on Afterburner, Medusa, Hades or Milan. This includes
debuggers (PureDebugger) and operating systems (MiNT with memory
protection). You could expect that... However I patched MonST and was
working on a patch for PureDebugger.

>> So we actually need a new debugger for MiNTOS, not singlemode in MiNT.
OK, I
>> agree - so let's develop a new, MiNT friendly debugger. Sven started work
on
>> something, it could even utilize special MiNT debugging features.
>
>And where is Sven?

I have no idea. But I got the source code of his debugger.

Petr