On 17/03/16 16:53, Boris Ostrovsky wrote:
> On 03/17/2016 12:03 PM, David Vrabel wrote:
>> On 17/03/16 12:45, Boris Ostrovsky wrote:
>>> Moving an unmasked irq may result in irq handler being invoked on both
>>> source and target CPUs.
>>>
>>> With 2-level this can happen as follows:
>>>
>>> On sou
On 03/17/2016 12:03 PM, David Vrabel wrote:
On 17/03/16 12:45, Boris Ostrovsky wrote:
Moving an unmasked irq may result in irq handler being invoked on both
source and target CPUs.
With 2-level this can happen as follows:
On source CPU:
evtchn_2l_handle_events() ->
generi
On 03/17/2016 01:29 PM, David Vrabel wrote:
On 17/03/16 16:53, Boris Ostrovsky wrote:
On 03/17/2016 12:03 PM, David Vrabel wrote:
On 17/03/16 12:45, Boris Ostrovsky wrote:
Moving an unmasked irq may result in irq handler being invoked on both
source and target CPUs.
With 2-level this can happ
On 17/03/16 12:45, Boris Ostrovsky wrote:
> Moving an unmasked irq may result in irq handler being invoked on both
> source and target CPUs.
>
> With 2-level this can happen as follows:
>
> On source CPU:
> evtchn_2l_handle_events() ->
> generic_handle_irq() ->
>
Moving an unmasked irq may result in irq handler being invoked on both
source and target CPUs.
With 2-level this can happen as follows:
On source CPU:
evtchn_2l_handle_events() ->
generic_handle_irq() ->
handle_edge_irq() ->
eoi_pirq():
