linux-kernel - Re: Userspace I/O driver core

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <45812DDD.4080907@argo.co.il>
Date:	Thu, 14 Dec 2006 12:56:29 +0200
From:	Avi Kivity <avi@...o.co.il>
To:	arjan@...radead.org
CC:	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org,
	tglx@...utronix.de
Subject: Re: Userspace I/O driver core

Arjan van de Ven wrote:
> On Thu, 2006-12-14 at 12:46 +0200, Avi Kivity wrote:
>   
>> Arjan van de Ven wrote:
>>     
>>>> I understand one still has to write a kernel driver to shut up the irq.  
>>>> How about writing a small bytecode interpreter to make event than 
>>>> unnecessary?
>>>>     
>>>>         
>>> if you do that why not do a real driver.
>>>
>>>   
>>>       
>> An entire driver in bytecode? 
>>     
>
> no a real, non-bytecode driver.
>
>   

Isn't the whole point of uio is to avoid writing a kernel mode driver?

As proposed, it doesn't quite accomplish it.  With an additional 
bytecode interpreter, you can have a 100% userspace driver (the bytecode 
interpreter would be part of uio, not the driver).


-- 
error compiling committee.c: too many arguments to function

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/