Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 1 May 2019 15:16:55 -0400
From:   Steven Rostedt <rostedt@goodmis.org>
To:     "Paul E. McKenney" <paulmck@linux.ibm.com>
Cc:     Peter Zijlstra <peterz@infradead.org>,
        linux-kernel@vger.kernel.org, andrea.parri@amarulasolutions.com
Subject: Re: Question about sched_setaffinity()
Message-ID: <20190501151655.51469a4c@gandalf.local.home>
In-Reply-To: <20190501191213.GX3923@linux.ibm.com>
References: <20190427180246.GA15502@linux.ibm.com>
        <20190430100318.GP2623@hirez.programming.kicks-ass.net>
        <20190430105129.GA3923@linux.ibm.com>
        <20190430115551.GT2623@hirez.programming.kicks-ass.net>
        <20190501191213.GX3923@linux.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, 1 May 2019 12:12:13 -0700
"Paul E. McKenney" <paulmck@linux.ibm.com> wrote:


> OK, what I did was to apply the patch at the end of this email to -rcu
> branch dev, then run rcutorture as follows:
> 
> nohup tools/testing/selftests/rcutorture/bin/kvm.sh --cpus 8 --duration 2 --configs "TRIVIAL" --bootargs "trace_event=sched:sched_switch,sched:sched_wakeup ftrace=function_graph ftrace_graph_filter=sched_setaffinity,migration_cpu_stop"
> 
> This resulted in the console output that I placed here:
> 
> http://www2.rdrop.com/~paulmck/submission/console.log.gz
> 
> But I don't see calls to sched_setaffinity() or migration_cpu_stop().
> Steve, is something else needed on the kernel command line in addition to
> the following?
> 
> ftrace=function_graph ftrace_graph_filter=sched_setaffinity,migration_cpu_stop

Do you have function graph enabled in the config?

[    2.098303] ftrace bootup tracer 'function_graph' not registered.


-- Steve