On Fri, Dec 11 2020 at 09:29, boris ostrovsky wrote:

On 12/11/20 7:37 AM, Thomas Gleixner wrote:

quoted

On Fri, Dec 11 2020 at 13:10, Jürgen Groß wrote:

quoted

On 11.12.20 00:20, boris.ostrovsky@oracle.com wrote:

quoted

On 12/10/20 2:26 PM, Thomas Gleixner wrote:

quoted

Change the implementation so that the channel is bound to CPU0 at the XEN
level and leave the affinity mask alone. At startup of the interrupt
affinity will be assigned out of the affinity mask and the XEN binding will
be updated.

If that's the case then I wonder whether we need this call at all and instead bind at startup time.

After some discussion with Thomas on IRC and xen-devel archaeology the
result is: this will be needed especially for systems running on a
single vcpu (e.g. small guests), as the .irq_set_affinity() callback
won't be called in this case when starting the irq.

On UP are we not then going to end up with an empty affinity mask? Or
are we guaranteed to have it set to 1 by interrupt generic code?

An UP kernel does not ever look on the affinity mask. The
chip::irq_set_affinity() callback is not invoked so the mask is
irrelevant.

A SMP kernel on a UP machine sets CPU0 in the mask so all is good.

This is actually why I brought this up in the first place --- a
potential mismatch between the affinity mask and Xen-specific data
(e.g. info->cpu and then protocol-specific data in event channel
code). Even if they are re-synchronized later, at startup time (for
SMP).

Which is not a problem either. The affinity mask is only relevant for
setting the affinity, but it's not relevant for delivery and never can
be.

I don't see anything that would cause a problem right now but I worry
that this inconsistency may come up at some point.

As long as the affinity mask becomes not part of the event channel magic
this should never matter.

Look at it from hardware:

interrupt is affine to CPU0

     CPU0 runs:
     
     set_affinity(CPU0 -> CPU1)
        local_irq_disable()
        
 --> interrupt is raised in hardware and pending on CPU0

        irq hardware is reconfigured to be affine to CPU1

        local_irq_enable()

 --> interrupt is handled on CPU0

the next interrupt will be raised on CPU1

So info->cpu which is registered via the hypercall binds the 'hardware
delivery' and whenever the new affinity is written it is rebound to some
other CPU and the next interrupt is then raised on this other CPU.

It's not any different from the hardware example at least not as far as
I understood the code.

Thanks,

        tglx