All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Tan Xiaojun <tanxiaojun@huawei.com>,
	peterz@infradead.org, mingo@redhat.com,
	alexander.shishkin@linux.intel.com, namhyung@kernel.org,
	songliubraving@fb.com, rostedt@goodmis.org,
	kan.liang@linux.intel.com, tz.stoyanov@gmail.com,
	alexey.budankov@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf record: Support aarch64 random socket_id assignment
Date: Tue, 13 Aug 2019 11:23:34 -0300	[thread overview]
Message-ID: <20190813142334.GE12299@kernel.org> (raw)
In-Reply-To: <20190802130926.GB27223@krava>

Em Fri, Aug 02, 2019 at 03:09:26PM +0200, Jiri Olsa escreveu:
> On Fri, Aug 02, 2019 at 11:48:57AM +0800, Tan Xiaojun wrote:
> > Same as the commit 01766229533f ("perf record: Support s390 random
> > socket_id assignment"), aarch64 also have this problem.
> > 
> > Without this fix:
> >   [root@localhost perf]# ./perf report --header -I -v
> >   ...
> >   socket_id number is too big.You may need to upgrade the perf tool.
> > 
> >   # ========
> >   # captured on    : Thu Aug  1 22:58:38 2019
> >   # header version : 1
> >   ...
> >   # Core ID and Socket ID information is not available
> >   ...
> > 
> > With this fix:
> >   [root@localhost perf]# ./perf report --header -I -v

Thanks, applied.

- Arnaldo

  reply	other threads:[~2019-08-13 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02  3:48 [PATCH] perf record: Support aarch64 random socket_id assignment Tan Xiaojun
2019-08-02 13:09 ` Jiri Olsa
2019-08-13 14:23   ` Arnaldo Carvalho de Melo [this message]
2019-08-15  9:35 ` [tip:perf/core] " tip-bot for Tan Xiaojun

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=20190813142334.GE12299@kernel.org \
    --to=arnaldo.melo@gmail.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=alexey.budankov@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=songliubraving@fb.com \
    --cc=tanxiaojun@huawei.com \
    --cc=tz.stoyanov@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.