>>> On 03.05.19 at 17:21, <roger....@citrix.com> wrote: > On Mon, Apr 29, 2019 at 05:23:20AM -0600, Jan Beulich wrote: >> --- >> TBD: The proper recording of the IPI destinations actually makes the >> move_cleanup_count field redundant. Do we want to drop it, at the >> price of a few more CPU-mask operations? > > AFAICT this is not a hot path, so I would remove the > move_cleanup_count field and just weight the cpu bitmap when needed.
FTR: It's not fully redundant - the patch removing it that I had added was actually the reason for seeing the ASSERT() trigger that you did ask to add in patch 1. The reason is that the field serves as a flag for irq_move_cleanup_interrupt() whether to act on an IRQ in the first place. Without it, the function will prematurely clean up the vector, thus confusing subsequent code trying to do the cleanup when it's actually due. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
