All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	peterz@infradead.org, Robin Murphy <robin.murphy@arm.com>,
	Suzuki Poulose <suzuki.poulose@arm.com>,
	James Clark <james.clark@arm.com>, Ingo Molnar <mingo@redhat.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V5 0/8] perf: Expand perf_branch_entry
Date: Thu, 28 Apr 2022 10:45:37 -0300	[thread overview]
Message-ID: <YmqagfywsvGXaIVl@kernel.org> (raw)
In-Reply-To: <a304d9e4-2632-1ba9-249f-1d87c90f82de@arm.com>

Em Mon, Apr 18, 2022 at 12:17:53PM +0530, Anshuman Khandual escreveu:
> On 4/11/22 11:16, Anshuman Khandual wrote:
> > On 4/4/22 10:20, Anshuman Khandual wrote:
> >> - Rebased series on v5.18-rc1
> > 
> > Gentle ping, any updates on this series ?
> 
> Gentle ping, any updates on this series ?
> 
> I have posted BRBE RFC V2 accommodating all these new perf ABI changes being
> proposed here. I would really appreciate reviews and/or suggestions on this
> series, which is essential and also prerequisite for the BRBE driver itself.
> 
> https://lore.kernel.org/all/20220412115455.293119-1-anshuman.khandual@arm.com/

Has the kernel bits been merged? When that happens I'll cherry pick the
tools/ ones.

In future series, please, on the final patch submission, please send two
series, one for the kernel and another for tooling.

- Arnaldo

WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	peterz@infradead.org, Robin Murphy <robin.murphy@arm.com>,
	Suzuki Poulose <suzuki.poulose@arm.com>,
	James Clark <james.clark@arm.com>, Ingo Molnar <mingo@redhat.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V5 0/8] perf: Expand perf_branch_entry
Date: Thu, 28 Apr 2022 10:45:37 -0300	[thread overview]
Message-ID: <YmqagfywsvGXaIVl@kernel.org> (raw)
In-Reply-To: <a304d9e4-2632-1ba9-249f-1d87c90f82de@arm.com>

Em Mon, Apr 18, 2022 at 12:17:53PM +0530, Anshuman Khandual escreveu:
> On 4/11/22 11:16, Anshuman Khandual wrote:
> > On 4/4/22 10:20, Anshuman Khandual wrote:
> >> - Rebased series on v5.18-rc1
> > 
> > Gentle ping, any updates on this series ?
> 
> Gentle ping, any updates on this series ?
> 
> I have posted BRBE RFC V2 accommodating all these new perf ABI changes being
> proposed here. I would really appreciate reviews and/or suggestions on this
> series, which is essential and also prerequisite for the BRBE driver itself.
> 
> https://lore.kernel.org/all/20220412115455.293119-1-anshuman.khandual@arm.com/

Has the kernel bits been merged? When that happens I'll cherry pick the
tools/ ones.

In future series, please, on the final patch submission, please send two
series, one for the kernel and another for tooling.

- Arnaldo

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-04-28 13:46 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04  4:50 [PATCH V5 0/8] perf: Expand perf_branch_entry Anshuman Khandual
2022-04-04  4:50 ` Anshuman Khandual
2022-04-04  4:50 ` [PATCH V5 1/8] perf: Add system error and not in transaction branch types Anshuman Khandual
2022-04-04  4:50   ` Anshuman Khandual
2022-04-19 13:55   ` James Clark
2022-04-19 13:55     ` James Clark
2022-04-04  4:50 ` [PATCH V5 2/8] perf: Extend branch type classification Anshuman Khandual
2022-04-04  4:50   ` Anshuman Khandual
2022-04-19 13:56   ` James Clark
2022-04-19 13:56     ` James Clark
2022-04-04  4:50 ` [PATCH V5 3/8] perf: Capture branch privilege information Anshuman Khandual
2022-04-04  4:50   ` Anshuman Khandual
2022-04-04  4:50 ` [PATCH V5 4/8] perf: Add PERF_BR_NEW_ARCH_[N] map for BRBE on arm64 platform Anshuman Khandual
2022-04-04  4:50   ` Anshuman Khandual
2022-04-19 13:57   ` James Clark
2022-04-19 13:57     ` James Clark
2022-04-04  4:50 ` [PATCH V5 5/8] perf/tools: Add system error and not in transaction branch types Anshuman Khandual
2022-04-04  4:50   ` Anshuman Khandual
2022-04-19 13:58   ` James Clark
2022-04-19 13:58     ` James Clark
2022-04-04  4:50 ` [PATCH V5 6/8] perf/tools: Extend branch type classification Anshuman Khandual
2022-04-04  4:50   ` Anshuman Khandual
2022-04-19 14:01   ` James Clark
2022-04-19 14:01     ` James Clark
2022-04-04  4:50 ` [PATCH V5 7/8] perf/tools: Add branch privilege information request flag Anshuman Khandual
2022-04-04  4:50   ` Anshuman Khandual
2022-04-04  4:50 ` [PATCH V5 8/8] perf/tools: Add PERF_BR_NEW_ARCH_[N] map for BRBE on arm64 platform Anshuman Khandual
2022-04-04  4:50   ` Anshuman Khandual
2022-04-11  5:46 ` [PATCH V5 0/8] perf: Expand perf_branch_entry Anshuman Khandual
2022-04-11  5:46   ` Anshuman Khandual
2022-04-18  6:47   ` Anshuman Khandual
2022-04-18  6:47     ` Anshuman Khandual
2022-04-28 13:45     ` Arnaldo Carvalho de Melo [this message]
2022-04-28 13:45       ` Arnaldo Carvalho de Melo
2022-05-11  3:49       ` Anshuman Khandual
2022-05-11  3:49         ` Anshuman Khandual
2022-05-11  4:28 ` Anshuman Khandual
2022-05-11  4:28   ` Anshuman Khandual

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=YmqagfywsvGXaIVl@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=anshuman.khandual@arm.com \
    --cc=james.clark@arm.com \
    --cc=jolsa@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=robin.murphy@arm.com \
    --cc=suzuki.poulose@arm.com \
    --cc=tglx@linutronix.de \
    --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 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.