[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] xen/evtchn and forced threaded irq
- To: Roger Pau Monné <roger.pau@xxxxxxxxxx>
- From: Julien Grall <julien.grall@xxxxxxxxx>
- Date: Thu, 21 Feb 2019 08:38:39 +0000
- Cc: Juergen Gross <jgross@xxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Andrew Cooper <Andrew.Cooper3@xxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Julien Grall <julien.grall@xxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>, Dave P Martin <dave.martin@xxxxxxx>
- Delivery-date: Thu, 21 Feb 2019 08:39:01 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
Hi Roger,
FWIW, you can also mask the interrupt while waiting for the thread to
execute the interrupt handler. Ie:
Thank you for providing steps, however where would the masking be done? By the irqchip or a custom solution?
1. Interrupt injected
2. Execute guest event channel callback
3. Scan for pending interrupts
4. Mask interrupt
5. Clear pending field
6. Queue threaded handler
7. Go to 3 until all interrupts are drained
[...]
8. Execute interrupt handler in thread
9. Unmask interrupt
That should prevent you from stacking interrupts?
Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel
|