public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Chris Friesen <chris.friesen@windriver.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jim Somerville <Jim.Somerville@windriver.com>,
	Christoph Lameter <cl@linux.com>
Subject: Re: [patch 3/3] isolcpus: undeprecate on documentation
Date: Tue, 31 Mar 2020 17:57:08 +0200	[thread overview]
Message-ID: <20200331155708.GU20730@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200331154146.GA28556@fuller.cnet>

On Tue, Mar 31, 2020 at 12:41:46PM -0300, Marcelo Tosatti wrote:
> On Tue, Mar 31, 2020 at 05:22:17PM +0200, Peter Zijlstra wrote:
> > On Sat, Mar 28, 2020 at 12:21:20PM -0300, Marcelo Tosatti wrote:
> > > isolcpus is used to control steering of interrupts to managed_irqs and
> > > kernel threads, therefore its incorrect to state that its deprecated.
> > > 
> > > Remove deprecation warning.
> > > 
> > > Suggested-by: Chris Friesen <chris.friesen@windriver.com>
> > > Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
> > > 
> > > ---
> > >  Documentation/admin-guide/kernel-parameters.txt |    1 -
> > >  1 file changed, 1 deletion(-)
> > > 
> > > Index: linux-2.6/Documentation/admin-guide/kernel-parameters.txt
> > > ===================================================================
> > > --- linux-2.6.orig/Documentation/admin-guide/kernel-parameters.txt
> > > +++ linux-2.6/Documentation/admin-guide/kernel-parameters.txt
> > > @@ -1926,7 +1926,6 @@
> > >  			Format: <RDP>,<reset>,<pci_scan>,<verbosity>
> > >  
> > >  	isolcpus=	[KNL,SMP,ISOL] Isolate a given set of CPUs from disturbance.
> > > -			[Deprecated - use cpusets instead]
> > >  			Format: [flag-list,]<cpu-list>
> > >  
> > 
> > It's still an absolute horrible piece of crap though. nozh_full piling
> > more and more shit on it doesn't make it more shiny.
> 
> Hi Peter,
> 
> Why do you dislike it? What you think would be a decent approach?

Try and reconfigure it after boot.

  reply	other threads:[~2020-03-31 15:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-28 15:21 [patch 0/3] affine kernel threads to specified cpumask (v3) Marcelo Tosatti
2020-03-28 15:21 ` [patch 1/3] kthread: switch to cpu_possible_mask Marcelo Tosatti
2020-03-28 15:21 ` [patch 2/3] isolcpus: affine kernel threads to specified cpumask Marcelo Tosatti
2020-03-31  0:57   ` Frederic Weisbecker
2020-03-31 11:50     ` Marcelo Tosatti
2020-03-31 13:36       ` Frederic Weisbecker
2020-03-28 15:21 ` [patch 3/3] isolcpus: undeprecate on documentation Marcelo Tosatti
2020-03-31 15:22   ` Peter Zijlstra
2020-03-31 15:41     ` Marcelo Tosatti
2020-03-31 15:57       ` Peter Zijlstra [this message]
2020-04-04 23:05         ` Christopher Lameter
2020-03-31 15:43     ` Frederic Weisbecker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200331155708.GU20730@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=Jim.Somerville@windriver.com \
    --cc=akpm@linux-foundation.org \
    --cc=chris.friesen@windriver.com \
    --cc=cl@linux.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox