All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@linaro.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, mingo@redhat.com,
	acme@kernel.org, alexander.shishkin@linux.intel.com,
	jolsa@redhat.com, daniel.lezcano@linaro.org, tglx@linutronix.de,
	sboyd@codeaurora.org, john.stultz@linaro.org
Subject: Re: [PATCH 0/5] arm64: perf: Proper cap_user_time* support
Date: Mon, 13 Jul 2020 14:08:00 +0800	[thread overview]
Message-ID: <20200713060800.GA15400@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <20200512124058.833263033@infradead.org>

Hi Peter,

On Tue, May 12, 2020 at 02:40:58PM +0200, Peter Zijlstra wrote:
> Prompted by Leo's patches, here a series that corrects the arm64 perf cap_user_time situation.

I checked the latest mainline kernel code base, found this patch set
are missed to merge into it.

Could you confirm if this is missed or any other reasons to hold on it?

Thanks,
Leo

WARNING: multiple messages have this Message-ID (diff)
From: Leo Yan <leo.yan@linaro.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	alexander.shishkin@linux.intel.com, Marc Zyngier <maz@kernel.org>,
	jolsa@redhat.com, daniel.lezcano@linaro.org,
	sboyd@codeaurora.org, linux-kernel@vger.kernel.org,
	acme@kernel.org, mingo@redhat.com, john.stultz@linaro.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	tglx@linutronix.de, Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/5] arm64: perf: Proper cap_user_time* support
Date: Mon, 13 Jul 2020 14:08:00 +0800	[thread overview]
Message-ID: <20200713060800.GA15400@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <20200512124058.833263033@infradead.org>

Hi Peter,

On Tue, May 12, 2020 at 02:40:58PM +0200, Peter Zijlstra wrote:
> Prompted by Leo's patches, here a series that corrects the arm64 perf cap_user_time situation.

I checked the latest mainline kernel code base, found this patch set
are missed to merge into it.

Could you confirm if this is missed or any other reasons to hold on it?

Thanks,
Leo

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

  parent reply	other threads:[~2020-07-13  6:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 12:40 [PATCH 0/5] arm64: perf: Proper cap_user_time* support Peter Zijlstra
2020-05-12 12:40 ` Peter Zijlstra
2020-05-12 12:40 ` [PATCH 1/5] sched_clock: Expose struct clock_read_data Peter Zijlstra
2020-05-12 12:40   ` Peter Zijlstra
2020-05-12 12:41 ` [PATCH 2/5] arm64: perf: Implement correct cap_user_time Peter Zijlstra
2020-05-12 12:41   ` Peter Zijlstra
2020-05-12 14:03   ` Leo Yan
2020-05-12 14:03     ` Leo Yan
2020-05-12 14:08     ` Peter Zijlstra
2020-05-12 14:08       ` Peter Zijlstra
2020-05-12 16:05   ` kbuild test robot
2020-05-12 16:05     ` kbuild test robot
2020-05-12 16:05     ` kbuild test robot
2020-05-12 12:41 ` [PATCH 3/5] arm64: perf: Only advertise cap_user_time for arch_timer Peter Zijlstra
2020-05-12 12:41   ` Peter Zijlstra
2020-05-12 12:41 ` [PATCH 4/5] perf: Add perf_event_mmap_page::cap_user_time_short ABI Peter Zijlstra
2020-05-12 12:41   ` Peter Zijlstra
2020-05-12 12:41 ` [PATCH 5/5] arm64: perf: Add cap_user_time_short Peter Zijlstra
2020-05-12 12:41   ` Peter Zijlstra
2020-05-12 14:11   ` Leo Yan
2020-05-12 14:11     ` Leo Yan
2020-05-12 16:59   ` kbuild test robot
2020-05-12 16:59     ` kbuild test robot
2020-05-12 16:59     ` kbuild test robot
2020-07-13  6:08 ` Leo Yan [this message]
2020-07-13  6:08   ` [PATCH 0/5] arm64: perf: Proper cap_user_time* support Leo Yan
2020-07-13 10:11   ` Will Deacon
2020-07-13 10:11     ` Will Deacon
2020-07-13 12:58     ` Leo Yan
2020-07-13 12:58       ` Leo Yan

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=20200713060800.GA15400@leoy-ThinkPad-X240s \
    --to=leo.yan@linaro.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=catalin.marinas@arm.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=john.stultz@linaro.org \
    --cc=jolsa@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sboyd@codeaurora.org \
    --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.