From: Avi Kivity <avi@argo.co.il>
To: arjan@infradead.org
Cc: Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: Userspace I/O driver core
Date: Thu, 14 Dec 2006 12:56:29 +0200 [thread overview]
Message-ID: <45812DDD.4080907@argo.co.il> (raw)
In-Reply-To: <1166093641.27217.989.camel@laptopd505.fenrus.org>
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
next prev parent reply other threads:[~2006-12-14 10:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 1:06 Userspace I/O driver core Greg KH
2006-12-14 5:48 ` Ben Nizette
2006-12-14 9:44 ` Avi Kivity
2006-12-14 10:19 ` Arjan van de Ven
2006-12-14 10:46 ` Avi Kivity
2006-12-14 10:54 ` Arjan van de Ven
2006-12-14 10:56 ` Avi Kivity [this message]
2006-12-14 17:54 ` Greg KH
2006-12-16 14:48 ` Dr. David Alan Gilbert
2006-12-14 10:25 ` Hans-Jürgen Koch
2006-12-14 10:48 ` Avi Kivity
2006-12-14 12:39 ` Jan Engelhardt
2006-12-14 13:38 ` Avi Kivity
2006-12-14 17:48 ` Jan Engelhardt
2006-12-14 18:00 ` Greg KH
2006-12-14 10:52 ` Alan
2006-12-14 11:22 ` Thomas Gleixner
2006-12-14 11:39 ` Alan
2006-12-14 11:37 ` Hans-Jürgen Koch
2006-12-14 12:45 ` Alan
2006-12-14 12:37 ` Jan Engelhardt
2006-12-14 16:10 ` linux-os (Dick Johnson)
2006-12-14 21:55 ` Ben Nizette
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45812DDD.4080907@argo.co.il \
--to=avi@argo.co.il \
--cc=arjan@infradead.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox