From fnaumann@mail.cs.uni-magdeburg.de Tue Jun 29 16:41:21 2004 Date: Tue, 29 Jun 2004 16:32:15 +0200 From: mikro To: mint@fishpool.com Subject: Re: [MiNT] mint & mmu Message-ID: <20040629143215.GA7029@hysteria.sk> References: <20040629082901.GA17656@hysteria.sk> <004001c45ddb$de231a80$770963d9@blaszak> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <004001c45ddb$de231a80$770963d9@blaszak> User-Agent: Mutt/1.4.2i X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on onyx.hysteria.sk X-Spam-Status: No, hits=-4.9 required=5.0 X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at fishpool.fi Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: mikro@hysteria.sk Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel > So you also have to emulate them (as TOS 4.04 emulates "move from SR" in > user mode). > of course! > And also, everything you mentioned as needs for supermode is perfectly > possible without using the Super() call. Obviously, under MiNT, not under > TOS. but the application has to use MiNT calls. and since we're talking about dirty (obviously old) apps or about demos... > The only way I can think of, which would save the Super() call and made it > safe, is somehow emulate all the code, or some other way catch every > instruction, that is executed between two Super() calls or inside Supexec(), > and heavily check that these instructions do "legal" things, and kill the > program otherwise. > hmm, in my opinion, this is extrem, but why not. we can let the user to choose the level of security (it's always speed vs ellegance) > I am sure that demo coders will love this idea :> > be sure, they do. why? probably you know how looks typical demo coding: ... typing asm lines... compiling... running... [blank screen, system freezes] ... $%^@# !!! ...reset and once again. my solution allows you to have FULL control under OS and, this is important, you have still access to hardware. so it's a coder's heaven to have stable and "immortal" OS and the possibility to use all things he like... ok, if you did something wrong with dsp communication (polling with no answer) or set the vectors incorectly, that's no way, but in other cases... it could help A LOT. -- --------------------------------------------------------------------------- MiKRO Atari XE/XL/Mega STE/Falcon060 http://mikro.atari.org ---------------------------------------------------------------------------