From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/5] ARM/ARM64 architected timer updates
Date: Tue, 27 Aug 2013 12:22:47 +0100 [thread overview]
Message-ID: <20130827112247.GH19897@arm.com> (raw)
In-Reply-To: <1377274749-6196-1-git-send-email-Sudeep.KarkadaNagesha@arm.com>
On Fri, Aug 23, 2013 at 05:19:04PM +0100, Sudeep KarkadaNagesha wrote:
> From: Sudeep KarkadaNagesha <sudeep.karkadanagesha@arm.com>
>
> This patch series adds support to configure the rate and enable the
> event stream for architected timer. The event streams can be used to
> impose a timeout on a wfe, to safeguard against any programming error
> in case an expected event is not generated or even to implement
> wfe-based timeouts for userspace locking implementations. This feature
> can be disabled(enabled by default).
I had two minor comments. Once they are addressed:
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: Re: [PATCH v4 0/5] ARM/ARM64 architected timer updates
Date: Tue, 27 Aug 2013 12:22:47 +0100 [thread overview]
Message-ID: <20130827112247.GH19897@arm.com> (raw)
In-Reply-To: <1377274749-6196-1-git-send-email-Sudeep.KarkadaNagesha@arm.com>
On Fri, Aug 23, 2013 at 05:19:04PM +0100, Sudeep KarkadaNagesha wrote:
> From: Sudeep KarkadaNagesha <sudeep.karkadanagesha@arm.com>
>
> This patch series adds support to configure the rate and enable the
> event stream for architected timer. The event streams can be used to
> impose a timeout on a wfe, to safeguard against any programming error
> in case an expected event is not generated or even to implement
> wfe-based timeouts for userspace locking implementations. This feature
> can be disabled(enabled by default).
I had two minor comments. Once they are addressed:
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2013-08-27 11:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 16:19 [PATCH v4 0/5] ARM/ARM64 architected timer updates Sudeep KarkadaNagesha
2013-08-23 16:19 ` Sudeep KarkadaNagesha
2013-08-23 16:19 ` [PATCH v4 1/5] ARM/ARM64: arch_timer: add macros for bits in control register Sudeep KarkadaNagesha
2013-08-23 16:19 ` Sudeep KarkadaNagesha
2013-08-27 11:21 ` Catalin Marinas
2013-08-27 11:21 ` Catalin Marinas
2013-08-27 11:37 ` Sudeep KarkadaNagesha
2013-08-27 11:37 ` Sudeep KarkadaNagesha
2013-08-27 14:52 ` Catalin Marinas
2013-08-27 14:52 ` Catalin Marinas
2013-08-27 15:19 ` Sudeep KarkadaNagesha
2013-08-27 15:19 ` Sudeep KarkadaNagesha
2013-08-27 16:53 ` Catalin Marinas
2013-08-27 16:53 ` Catalin Marinas
2013-08-27 17:16 ` Sudeep KarkadaNagesha
2013-08-27 17:16 ` Sudeep KarkadaNagesha
2013-08-23 16:19 ` [PATCH v4 2/5] ARM: arch_timer: add support to configure and enable event stream Sudeep KarkadaNagesha
2013-08-23 16:19 ` Sudeep KarkadaNagesha
2013-08-23 16:19 ` [PATCH v4 3/5] ARM64: " Sudeep KarkadaNagesha
2013-08-23 16:19 ` Sudeep KarkadaNagesha
2013-08-27 11:19 ` Catalin Marinas
2013-08-27 11:19 ` Catalin Marinas
2013-08-27 11:31 ` Sudeep KarkadaNagesha
2013-08-27 11:31 ` Sudeep KarkadaNagesha
2013-08-23 16:19 ` [PATCH v4 4/5] drivers: clocksource: add support for ARM architected timer " Sudeep KarkadaNagesha
2013-08-23 16:19 ` Sudeep KarkadaNagesha
2013-08-23 16:19 ` [PATCH v4 5/5] drivers: clocksource: add CPU PM notifier for ARM architected timer Sudeep KarkadaNagesha
2013-08-23 16:19 ` Sudeep KarkadaNagesha
2013-08-27 11:22 ` Catalin Marinas [this message]
2013-08-27 11:22 ` [PATCH v4 0/5] ARM/ARM64 architected timer updates Catalin Marinas
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=20130827112247.GH19897@arm.com \
--to=catalin.marinas@arm.com \
--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.