From: acme@kernel.org (Arnaldo Carvalho de Melo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] perf-tools: cs-etm: Properly deal with cpu maps
Date: Thu, 15 Feb 2018 11:56:17 -0300 [thread overview]
Message-ID: <20180215145617.GD30974@kernel.org> (raw)
In-Reply-To: <1518478737-24649-1-git-send-email-mathieu.poirier@linaro.org>
Em Mon, Feb 12, 2018 at 04:38:57PM -0700, Mathieu Poirier escreveu:
> This patch allows the CoreSight AUX info section to fit topologies where
> only a subset of all available CPUs are present, avoiding at the same time
> accessing the ETM configuration areas of CPUs that have been offlined.
Thanks, applied.
- Arnaldo
WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf-tools: cs-etm: Properly deal with cpu maps
Date: Thu, 15 Feb 2018 11:56:17 -0300 [thread overview]
Message-ID: <20180215145617.GD30974@kernel.org> (raw)
In-Reply-To: <1518478737-24649-1-git-send-email-mathieu.poirier@linaro.org>
Em Mon, Feb 12, 2018 at 04:38:57PM -0700, Mathieu Poirier escreveu:
> This patch allows the CoreSight AUX info section to fit topologies where
> only a subset of all available CPUs are present, avoiding at the same time
> accessing the ETM configuration areas of CPUs that have been offlined.
Thanks, applied.
- Arnaldo
next prev parent reply other threads:[~2018-02-15 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 23:38 [PATCH] perf-tools: cs-etm: Properly deal with cpu maps Mathieu Poirier
2018-02-12 23:38 ` Mathieu Poirier
2018-02-15 14:56 ` Arnaldo Carvalho de Melo [this message]
2018-02-15 14:56 ` Arnaldo Carvalho de Melo
2018-02-17 11:30 ` [tip:perf/core] perf " tip-bot for Mathieu Poirier
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=20180215145617.GD30974@kernel.org \
--to=acme@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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 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.