Messages in this thread |  | | From | "Luck, Tony" <> | Subject | RE: [PATCH 1/2] x86/intel_rdt/mbm: Fix MBM overflow handler during hot cpu | Date | Wed, 16 Aug 2017 14:53:52 +0000 |
| |
> You could alternatively use flush and make the worker code schedule the > work on a still online CPU in the domain instead of blindly rescheduling it > on the same CPU.
We looked at that when you suggested flush. The problem is that we have already deleted the current cpu from the bitmask for the domain. So the worker code doesn't know which domain it is running on, so can't pick another.
If we try to do the flush before dropping the cpu from the bitmask, then the worker code doesn't have any reason to pick a different CPU.
Is there is some cheap "I'm running on a CPU that is in the process of going offline" test that we could make in the worker code?
-Tony
|  |