In-Reply-To: <1143016607.2955.14.camel@laptopd505.fenrus.org>
References: <20060322063040.960068000@sorel.sous-sol.org> <20060322063758.453555000@sorel.sous-sol.org> <1143016607.2955.14.camel@laptopd505.fenrus.org>
Mime-Version: 1.0 (Apple Message framework v623)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <280dfa6948b4c3321e4630d75fa9f5b5@cl.cam.ac.uk>
Content-Transfer-Encoding: 7bit
Cc: virtualization@lists.osdl.org, Ian Pratt <ian.pratt@xensource.com>,
       xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org,
       Chris Wright <chrisw@sous-sol.org>
From: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Subject: Re: [RFC PATCH 23/35] Add support for Xen event channels.
Date: Wed, 22 Mar 2006 11:30:09 +0000
To: Arjan van de Ven <arjan@infradead.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1141
Lines: 39


On 22 Mar 2006, at 08:36, Arjan van de Ven wrote:

>> +#include <linux/interrupt.h>
>> +#include <linux/sched.h>
>> +#include <linux/kernel_stat.h>
>> +#include <linux/version.h>
>
> this highly looks that it's not possible to be used outside the linux
> kernel so the license is odd

It can't be used directly, but other OS ports steal fairly directly 
from this file (and others). For example OpenSolaris and the BSDs.

>> +static int find_unbound_irq(void)
>> +{
>> +	int irq;
>> +
>> +	for (irq = 0; irq < NR_IRQS; irq++)
>> +		if (irq_bindcount[irq] == 0)
>> +			break;
>> +
>> +	if (irq == NR_IRQS) {
>> +		printk(KERN_ERR "No available IRQ to bind to: increase 
>> NR_IRQS!\n");
>
> there is no way to share interrupts? A shame

256 allocatable IRQs seems plenty to be getting on with. Shared IRQs 
can certainly be added later -- there are no hidden gotchas I'm pretty 
sure.

  -- Keir

-
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/