From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,6394e5e171f847d1
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2001-09-07 05:40:40 PST
Path: 
 archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!130.133.1.3!fu-berlin.de!uni-berlin.de!ailinel.cbb-automation.DE!not-for-mail
From: dmitry@elros.cbb-automation.de (Dmitry Kazakov)
Newsgroups: comp.lang.ada
Subject: Re: Ada OS Kernel features
Date: Fri, 07 Sep 2001 12:40:37 GMT
Message-ID: <3b98bddb.18504734@news.cis.dfn.de>
References: <9n4euv$t9m$1@slb6.atl.mindspring.net>
 <3B964C7A.BC04374E@icn.siemens.de> <9n5o9n$37a$1@slb7.atl.mindspring.net>
 <3%ul7.3362$9z1.440040@news6-win.server.ntlworld.com>
 <wjwKHdGfRR9P@eisner.encompasserve.org>
 <UWOl7.11352$592.628767@news2-win.server.ntlworld.com>
 <3b987e18.2182875@news.cis.dfn.de>
 <slrn9ph0md.mou.d97svema@licia.dtek.chalmers.se>
NNTP-Posting-Host: ailinel.cbb-automation.de (212.79.194.99)
X-Trace: fu-berlin.de 999866438 6709246 212.79.194.99 (16 [77047])
X-Newsreader: Forte Free Agent 1.21/32.243
Xref: archiver1.google.com comp.lang.ada:12885
Date: 2001-09-07T12:40:37+00:00
List-Id: <comp.lang.ada>

On 7 Sep 2001 08:18:21 GMT, d97svema@dtek.chalmers.se (Mattias
Svensson) wrote:

>In article <3b987e18.2182875@news.cis.dfn.de>, Dmitry Kazakov wrote:
>>On Thu, 6 Sep 2001 19:06:29 +0100, "chris.danx"
>><chris.danx@ntlworld.com> wrote:
>>Any shared device should be not allowed to be directly used in the
>>user mode. If a video driver operates in the user mode, then it is
>>possible to have an application that reads and updates the parts of
>>the screen of another application. Now consider that another
>>application is a part of home-banking software. Wellcome in the
>>MS-Windows world!
>
>Why? If the video driver has exclusive access to the video memory and
>just presents an API to other programs by some menas of IPC.

If the driver runs on the context of the caller's process, then there
is no way to share the device safely.

>In what
>way is this different from having the video driver in the kernel? 

Not in the kernel, but in a separate process which has other
privilegies than the caller. There IMO should be no monolitic kernel,
but a set of objects having no more access than they should.

>The hard part I think is to give access to the video memory from
>userspace.

Regards,
Dmitry Kazakov