From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, andrea.parri@amarulasolutions.com
Subject: Re: Question about sched_setaffinity()
Date: Wed, 1 May 2019 13:27:13 -0700 [thread overview]
Message-ID: <20190501202713.GY3923@linux.ibm.com> (raw)
In-Reply-To: <20190501151655.51469a4c@gandalf.local.home>
On Wed, May 01, 2019 at 03:16:55PM -0400, Steven Rostedt wrote:
> 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.
I guess I don't! Thank you, will fix.
Let's see...
My .config has CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y. It looks like I
need CONFIG_FUNCTION_GRAPH_TRACER=y, which I don't have. And it looks
like that needs CONFIG_FUNCTION_TRACER=y, which I also don't have.
But I do have CONFIG_HAVE_FUNCTION_TRACER=y. So I should add this
to my rcutorture command line:
--kconfig "CONFIG_FUNCTION_TRACER=y CONFIG_FUNCTION_GRAPH_TRACER=y".
I fired this up. Here is hoping! ;-)
And it does have sched_setaffinity(), woo-hoo!!! I overwrote the old file:
http://www2.rdrop.com/~paulmck/submission/console.log.gz
Thanx, Paul
next prev parent reply other threads:[~2019-05-01 20:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 18:02 Paul E. McKenney
2019-04-30 10:03 ` Peter Zijlstra
2019-04-30 10:51 ` Paul E. McKenney
2019-04-30 11:55 ` Peter Zijlstra
2019-05-01 19:12 ` Paul E. McKenney
2019-05-01 19:16 ` Steven Rostedt
2019-05-01 20:27 ` Paul E. McKenney [this message]
2019-05-07 22:16 ` Paul E. McKenney
2019-05-09 17:36 ` Paul E. McKenney
2019-05-09 19:36 ` Paul E. McKenney
2019-05-10 12:08 ` Peter Zijlstra
2019-05-10 23:07 ` Paul E. McKenney
2019-05-11 21:45 ` Andrea Parri
2019-05-12 0:39 ` Paul E. McKenney
2019-05-12 1:05 ` Andrea Parri
2019-05-13 12:20 ` Paul E. McKenney
2019-05-13 15:37 ` Joel Fernandes
2019-05-13 15:53 ` Paul E. McKenney
2019-05-13 8:10 ` Peter Zijlstra
2019-05-13 12:19 ` Paul E. McKenney
2019-05-09 21:40 ` Andrea Parri
2019-05-09 21:56 ` Andrea Parri
2019-05-09 22:17 ` Paul E. McKenney
2019-05-10 6:32 ` Andrea Parri
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=20190501202713.GY3923@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=andrea.parri@amarulasolutions.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
/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
Powered by JetHome