Re: protected type interrupts
"REH" <spamjunk@xxxxxxxxxxx> writes:
With newer versions of their compiler, the computer resets. They
say it is because they are calling the entry at the interrupt level,
and not the task level (we process this in a task because we have to
do things you cannot do in a interrupt). They say the LRM allows
them to do this.
So why do they support POs as interrupt handlers at all? what do they
expect you to do?
.
Relevant Pages
- [PATCH 11/13] [RFC] ipath verbs, part 2
... + * Called at interrupt level with the QP s_lock held. ... + * This is called from ipath_intrat interrupt level when a PIO buffer ... + * This may be called from interrupt context. ...
(Linux-Kernel) - Re: [PATCH 0/2] eventfd: new EFD_STATE flag
... A single other process (hypervisor) is interested in a condition ... (interrupt level) ... an interrupt level value needs to be read and copied to ... shared memory where each device writes interrupt ...
(Linux-Kernel) - Interrupt level sharing,
... An interrupt interface circuit for interrupt level sharing comprising a pulse generator having an open-collector or tri-state output connected to an external interrupt line shared by other similar circuits. ...
(comp.sys.ibm.ps2.hardware) - [PATCH 17 of 20] ipath - infiniband verbs support, part 3 of 3
... + * Called at interrupt level. ... + * This is called from ipath_intrat interrupt level when a PIO buffer ... + * This may be called from interrupt context. ...
(Linux-Kernel) - Re: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered
... The system reports the timer IRQ to be routed to pin 2, ... There's no workaround in the kernel as working it ... That entry appears due to conditions making the following entry being ... I don't know why the SCI interrupt is set up the second time here. ...
(Linux-Kernel) |
|
