Re: [GIT PATCH] more Driver core patches for 2.6.19
- From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
- Date: Wed, 13 Dec 2006 22:22:13 +0100 (MET)
You can simply mask it, have it handled by userspace and re-enable it
when that's done. Though say hello to horrible interrupt latencies and
hope you aren't sharing it with anything critical...
For the sharing case, some sort of softirq should be created. That is, when a
hard interrupt is generated and the irq handler is executed, set a flag that at
some other point in time, the irq is delivered to userspace. Like you do with
signals in userspace:
void sighandler(int s) {
exit_main_loop_soon = 1;
}
something similar could be done in kernelspace without interrupting important
devices/irq_handlers sharing the same IRQ.
-`J'
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [GIT PATCH] more Driver core patches for 2.6.19
- From: Linus Torvalds
- Re: [GIT PATCH] more Driver core patches for 2.6.19
- References:
- [GIT PATCH] more Driver core patches for 2.6.19
- From: Greg KH
- Re: [GIT PATCH] more Driver core patches for 2.6.19
- From: Linus Torvalds
- Re: [GIT PATCH] more Driver core patches for 2.6.19
- From: Benjamin Herrenschmidt
- [GIT PATCH] more Driver core patches for 2.6.19
- Prev by Date: Re: [GIT PATCH] more Driver core patches for 2.6.19
- Next by Date: Re: [PATCH] binfmt_elf: core dump masking support
- Previous by thread: Re: [GIT PATCH] more Driver core patches for 2.6.19
- Next by thread: Re: [GIT PATCH] more Driver core patches for 2.6.19
- Index(es):
Relevant Pages
|
