[lkml]   [2020]   [Feb]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH V4] sched/isolation: isolate from handling managed interrupt
On Wed, Jan 22, 2020 at 02:25:38PM +0100, Thomas Gleixner wrote:
> Ming,
> Ming Lei <> writes:
> >
> > +static bool hk_should_isolate(struct irq_data *data,
> > + const struct cpumask *affinity, unsigned int cpu)
> > +{
> the *affinity argument is unused.
> I'll remove it myself.

Hi, Ming, Thomas,

The new "managed_irq" works for us, thanks for both of your work!

However I just noticed that this new sub-parameter might break users
if applied incorrectly to old kernels, because iiuc "isolcpus="
parameter will not apply at all when there's unknown sub-parameters:

static int __init housekeeping_isolcpus_setup(char *str)
unsigned int flags = 0;

while (isalpha(*str)) {
pr_warn("isolcpus: Error, unknown flag\n");
return 0;

Then the same kernel parameter will break isolcpus= if the user
reboots and switches to an older kernel.

A solution to this could be that we introduce an isolated parameter
for "managed_irq", then on the old kernels only the new parameter will
be ignored rather than the whole "isolcpus=" parameter, so nothing
will break.

I'm not sure whether it's already too late for this, or if there's any
better alternative. Just raise this question up to see whether we
still have chance to fix this up.


Peter Xu

 \ /
  Last update: 2020-02-03 20:23    [W:0.580 / U:0.004 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site