Yes, I agree, it is strange and could be coded either way.
I doubt there was any real intent here, is is simply how we coded it.
The 970 (our only port) has issues with external interrupt latencies
already, I doubt this code really effects performance.
At the moment we "share" control if the P
On Fri, May 18, 2007 at 01:03:35AM +, HYEONSEUNG JANG wrote:
> Is there anyone who can tell me the reason why do_softirq() is not
> called after external interrupt handling? Or is it just a simple
> missing(but important) code in XenPPC port ?
Others on this list can comment about Xen/PPC's mo
There are currently three places in xen code where do_softirq() is
called.
- return to the guest from the hypervisor decrementer interrupt handler
- return to the guest from a hypercall()
- in idle_loop()
But it is kind of strange that do_softirq() is not called after external
interrupt handle
