linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Denis Kirjanov <kda@linux-powerpc.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] powerpc: tracing: don't trace hcalls on offline CPUs
Date: Thu, 26 Nov 2015 20:26:40 +1100	[thread overview]
Message-ID: <1448530000.22295.4.camel@ellerman.id.au> (raw)
In-Reply-To: <CAOJe8K0ggTkoBX8=N6qo=Ftnjm5V3z50QL+R1jPnawfrC2fJ5g@mail.gmail.com>

On Thu, 2015-11-26 at 11:15 +0300, Denis Kirjanov wrote:
> On 11/26/15, Michael Ellerman <mpe@ellerman.id.au> wrote:
> > On Tue, 2015-11-24 at 21:23 +0300, Denis Kirjanov wrote:
> > I can't get this to hit.
> > 
> > I've got LOCKDEP=y, I've enabled the hcall tracepoints, and then I offline
> > a cpu via sysfs.

> I haven't tried it via sysfs. Could you share the command
> so I give a try to reproduce.

Either manually:

$ echo 0 > /sys/devices/system/cpuN/online

Or using:

$ ppc64_cpu --cores-on=1
and/or
$ ppc64_cpu --smt=1

Which uses sysfs.

cheers

  reply	other threads:[~2015-11-26  9:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 18:23 [PATCH 1/2] tracing: introduce TRACE_EVENT_FN_COND macro Denis Kirjanov
2015-11-24 18:23 ` [PATCH 2/2] powerpc: tracing: don't trace hcalls on offline CPUs Denis Kirjanov
2015-11-26  6:39   ` Michael Ellerman
2015-11-26  8:15     ` Denis Kirjanov
2015-11-26  9:26       ` Michael Ellerman [this message]
2015-11-26 20:10         ` Denis Kirjanov
2015-12-07 20:52   ` Steven Rostedt
2015-12-07 21:02     ` Benjamin Herrenschmidt
2015-12-07 21:33       ` Steven Rostedt
2015-12-14 10:00         ` Michael Ellerman
2015-12-14 10:05           ` Denis Kirjanov
2015-12-07 14:42 ` [PATCH 1/2] tracing: introduce TRACE_EVENT_FN_COND macro Denis Kirjanov
2015-12-07 14:57   ` Steven Rostedt
2015-12-11 19:40   ` Steven Rostedt

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=1448530000.22295.4.camel@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=kda@linux-powerpc.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).