From fnaumann@mail.cs.uni-magdeburg.de Wed Jan 28 15:11:09 2004 To: mint@fishpool.com Subject: Re: [MiNT] fVDI issues Date: 28 Jan 2004 14:48:14 From: "Adam Klobukowski" MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 In-Reply-To: <07ba01c3e58b$26865ae0$0e0a63d9@blaszak> X-Priority: Normal X-Mailer: Marijuana Mail 0.1.67n [pl] (Atari Falcon 030; TOS 4.04 & MiNT / NVDI 5.01) Message-Id: <20040128133429.9F91835450@komp7.euh-e.edu.pl> 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: atari@gabo.pl Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by prinz.cs.uni-magdeburg.de id i0SEB7o08748 > I hope we all agree that the current situation is hm... unacceptable > in longer terms. I have no clear thoughts about VDI, but for the AES > I think that Atari have made a mistake hooking it onto trap #2. Or > any trap, to be strict. As a consequence we now have an AES running > as a separate process, which creates all sort of problems and > enforces many kludges because the AES designed so must have an > access to other programs' private memory which is normally not > allowed. VDI should be a kernel module. The main reason for this is speed. AES should be a userland app. I see strong reasons fro adding XGem to it (ie. AES+XGem hybrid) Some time agor Frank made (or tried to make) kernel module from Xaaes. Frank, you never said what was the results of it, could you tell us a little about it? The other way could be having both VDI and AES as kernel modules, and AES should call VDI directly (ie. without using traps). I think this is the fastest solution (CPU wise) and also could save some work. We could beat MagiC ;) -- Semper Fidelis Adam Klobukowski atari@gabo.pl