> (i.e. counted). An alternative to queuing (user selectable) is to block > interrupt generation at hardware level in kernel space immediately > before notification. > > I'm missing something? IRQ 9 shared between user space app and disk. IRQ arrives is disabled and reported, app wakes up, app wants to page in code, IRQ is disabled, box dies You have to handle that in kernel space, at least enough to handle the irq event, ack it and queue the data - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Re: Is it useful to support user level drivers Balbir Singh
- Re: Is it useful to support user level drivers Alan Cox
- Re: Is it useful to support user level drivers Pavel Machek
- Re: Is it useful to support user level drivers Dmitry A. Fedorov
- Re: Is it useful to support user level drivers Oliver Neukum
- Re: Is it useful to support user level dri... Dmitry A. Fedorov
- Re: Is it useful to support user level... Oliver Neukum
- Re: Is it useful to support user ... Dmitry A. Fedorov
- Re: Is it useful to support u... Balbir Singh
- Re: Is it useful to support user level... Abramo Bagnara
- Re: Is it useful to support user ... Alan Cox
- Re: Is it useful to support u... Abramo Bagnara
- Re: Is it useful to support u... Richard B. Johnson
- Re: Is it useful to support u... Abramo Bagnara
- Re: Is it useful to support u... Oliver Neukum
- Re: Is it useful to support u... Pavel Machek
- Re: Is it useful to support user level drivers Alan Cox
- Re: Is it useful to support user level dri... Matthias Urlichs
- Re: Is it useful to support user level... Pavel Machek
- Re: Is it useful to support user level dri... Dmitry A. Fedorov
- Re: Is it useful to support user level drivers Dmitry A. Fedorov