Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932371AbWLNKqa (ORCPT ); Thu, 14 Dec 2006 05:46:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932395AbWLNKq3 (ORCPT ); Thu, 14 Dec 2006 05:46:29 -0500 Received: from il.qumranet.com ([62.219.232.206]:53124 "EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932371AbWLNKq3 (ORCPT ); Thu, 14 Dec 2006 05:46:29 -0500 Message-ID: <45812B83.90006@argo.co.il> Date: Thu, 14 Dec 2006 12:46:27 +0200 From: Avi Kivity User-Agent: Thunderbird 1.5.0.8 (X11/20061107) MIME-Version: 1.0 To: Arjan van de Ven CC: Greg KH , linux-kernel@vger.kernel.org, tglx@linutronix.de Subject: Re: Userspace I/O driver core References: <20061214010608.GA13229@kroah.com> <45811D0F.2070705@argo.co.il> <1166091570.27217.983.camel@laptopd505.fenrus.org> In-Reply-To: <1166091570.27217.983.camel@laptopd505.fenrus.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 710 Lines: 24 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? that means exposing the entire kernel API to the bytecode interpreter. A monumental task. Or did I misunderstand you? -- 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/