[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YQwDiORI3jsh8vNw@hirez.programming.kicks-ass.net>
Date:   Thu, 5 Aug 2021 17:28:08 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     Rahul Gopakumar <gopakumarr@...are.com>,
        Valentin Schneider <valentin.schneider@....com>,
        Abdul Anshad Azeez <aazees@...are.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "mingo@...hat.com" <mingo@...hat.com>,
        "juri.lelli@...hat.com" <juri.lelli@...hat.com>,
        "vincent.guittot@...aro.org" <vincent.guittot@...aro.org>,
        Rajender M <manir@...are.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [Linux Kernel 5.13 GA] ESXi Performance regression
On Thu, Aug 05, 2021 at 11:24:37AM -0400, Steven Rostedt wrote:
> On Thu, 5 Aug 2021 17:05:00 +0200
> Peter Zijlstra <peterz@...radead.org> wrote:
> 
> > > Hmm, is this a user space breakage?  
> > 
> > All those files were under CONFIG_SCHED_DEBUG and a !DEBUG build would
> > not have them to begin with.
> 
> But you can have a config with CONFIG_DEBUG_FS disabled, and DEBUG and
> SCHED_DEBUG enabled, which means that there's now configs where this
> value is no longer available.
You already had that, notably: CONFIG_SCHED_DEBUG=n.
These have always been debug knobs, if you touch them you get to keep
the pieces.
Powered by blists - more mailing lists
 
