Change Details

Question: where does the EOI belong for a RAS interrupt? Does it belong In the [common] RAS priority handler or in the [individual] RAS error handler? Currently, the RAS priority handler, 'ras_interrupt_handler()', does not perform EOI processing (i.e. it does not invoke 'plat_ic_end_of_interrupt()' after calling the [individual] RAS error handler). I am encountering a problem when I dispatch an SDEI event from a RAS error handler. Although the SDEI event completes and returns to the RAS error handler, the system subsequently hangs. If I invoke 'plat_ic_end_of_interrupt()' after the RAS error handler completes, the system operates normally. I would expect that the platform EOI processing be invoked from the [common] RAS priority handler, rather than requiring it to be included in each and every RAS error handler.

Resolved: I agree with comment by odeprez; the EOI belongs in the INDIVIDUAL RAS error handler since not all RAS errors involve the interrupt controller (as in a CPU exception). Question: where does the EOI belong for a RAS interrupt? Does it belong In the [common] RAS priority handler or in the [individual] RAS error handler? Currently, the RAS priority handler, 'ras_interrupt_handler()', does not perform EOI processing (i.e. it does not invoke 'plat_ic_end_of_interrupt()' after calling the [individual] RAS error handler). I am encountering a problem when I dispatch an SDEI event from a RAS error handler. Although the SDEI event completes and returns to the RAS error handler, the system subsequently hangs. If I invoke 'plat_ic_end_of_interrupt()' after the RAS error handler completes, the system operates normally. I would expect that the platform EOI processing be invoked from the [common] RAS priority handler, rather than requiring it to be included in each and every RAS error handler.

Resolved: I agree with comment by odeprez; the EOI belongs in the INDIVIDUAL RAS error handler since not all RAS errors involve the interrupt controller (as in a CPU exception). Question: where does the EOI belong for a RAS interrupt? Does it belong In the [common] RAS priority handler or in the [individual] RAS error handler? Currently, the RAS priority handler, 'ras_interrupt_handler()', does not perform EOI processing (i.e. it does not invoke 'plat_ic_end_of_interrupt()' after calling the [individual] RAS error handler). I am encountering a problem when I dispatch an SDEI event from a RAS error handler. Although the SDEI event completes and returns to the RAS error handler, the system subsequently hangs. If I invoke 'plat_ic_end_of_interrupt()' after the RAS error handler completes, the system operates normally. I would expect that the platform EOI processing be invoked from the [common] RAS priority handler, rather than requiring it to be included in each and every RAS error handler.