linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@gmail.com>
To: John Garry <john.g.garry@oracle.com>,
	Will Deacon <will@kernel.org>, James Clark <james.clark@arm.com>,
	Leo Yan <leo.yan@linaro.org>, Mike Leach <mike.leach@linaro.org>
Cc: Ian Rogers <irogers@google.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
	linux-perf-users <linux-perf-users@vger.kernel.org>,
	Thomas Richter <tmricht@linux.ibm.com>,
	Ravi Bangoria <ravi.bangoria@amd.com>
Subject: perf-tools-next: Request for testing hybrid changes
Date: Thu, 22 Jun 2023 11:57:28 -0700	[thread overview]
Message-ID: <CAM9d7cgmHuhv1U6yAB-2qUr8SuFjUd-Lqw0kew9MaBVeD8xxGw@mail.gmail.com> (raw)

Hello,

In this development cycle, we've got a big change in how to handle
heterogeneous core PMUs. It's mostly tested on Intel hybrid machines
but caused some troubles on others.  So I'd like to confirm it works
on major platforms without problems.  Especially on ARM64 as it has
the big.LITTLE CPUs.

Also we are transitioning from Arnaldo's tree to new repositories in
git.kernel.org:

 * kernel/git/perf/perf-tools (for the fixes on the current dev cycle)
 * kernel/git/perf/perf-tools-next (for new features for the next cycle)

There is a branch with the same name.  Please check out
perf-tools-next and play with it.

Thanks,
Namhyung

             reply	other threads:[~2023-06-22 18:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-22 18:57 Namhyung Kim [this message]
2023-06-22 20:15 ` perf-tools-next: Request for testing hybrid changes Ian Rogers
2023-06-23  8:42   ` James Clark
2023-06-23 14:30     ` Ian Rogers
2023-06-23 17:59       ` Ian Rogers
2023-06-26 12:32       ` Will Deacon
2023-06-26 14:39         ` James Clark
2023-06-26 15:09           ` Will Deacon
2023-06-26 16:11             ` Ian Rogers
2023-06-29 11:13       ` James Clark
2023-06-30 15:30         ` Ian Rogers
2023-06-30 16:14           ` James Clark
2023-06-30 16:45             ` Ian Rogers
2023-07-04 11:30               ` James Clark
2023-07-04 12:33                 ` Ravi Bangoria
2023-07-04 12:44                   ` James Clark
2023-07-04 14:47                     ` Ravi Bangoria
2023-07-04 17:59                       ` Ian Rogers

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=CAM9d7cgmHuhv1U6yAB-2qUr8SuFjUd-Lqw0kew9MaBVeD8xxGw@mail.gmail.com \
    --to=namhyung@gmail.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=irogers@google.com \
    --cc=james.clark@arm.com \
    --cc=john.g.garry@oracle.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mike.leach@linaro.org \
    --cc=ravi.bangoria@amd.com \
    --cc=tmricht@linux.ibm.com \
    --cc=will@kernel.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).