From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Thomas Richter <tmricht@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
brueckner@linux.vnet.ibm.com, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com
Subject: Re: [PATCH 1/2] perf record: Support s390 random socket_id assignment
Date: Wed, 13 Jun 2018 16:55:56 -0300 [thread overview]
Message-ID: <20180613195556.GD2686@kernel.org> (raw)
In-Reply-To: <20180611073153.15592-1-tmricht@linux.ibm.com>
Em Mon, Jun 11, 2018 at 09:31:52AM +0200, Thomas Richter escreveu:
> On s390 the socket identifier assigned to a CPU identifier is
> random and (depending on the configuration of the LPAR) may be higher
> than the CPU identifier. This is currently not supported.
>
> Fix this by allowing arbitrary socket identifiers being assigned to
> CPU id.
>
> Output before:
Thanks, applied both patches in this series,
- Arnaldo
prev parent reply other threads:[~2018-06-13 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 7:31 [PATCH 1/2] perf record: Support s390 random socket_id assignment Thomas Richter
2018-06-11 7:31 ` [PATCH 2/2] perf test: Fix test 39 Session topology for s390 Thomas Richter
2018-06-13 19:55 ` Arnaldo Carvalho de Melo [this message]
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=20180613195556.GD2686@kernel.org \
--to=acme@kernel.org \
--cc=brueckner@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=tmricht@linux.ibm.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 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).