From: Baruch Siach <baruch@tkos.co.il>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: design.txt: remove mention of set_perf_event_pending
Date: Mon, 13 Jan 2014 12:48:39 +0200 [thread overview]
Message-ID: <20140113104839.GN4944@tarshish> (raw)
In-Reply-To: <bd81da79fb3cfca28d7e990566c8794ec14328c7.1385647452.git.baruch@tkos.co.il>
Hi perf maintainers,
Ping?
On Thu, Nov 28, 2013 at 04:04:12PM +0200, Baruch Siach wrote:
> set_perf_event_pending() was removed in e360adbe (irq_work: Add generic hardirq
> context callbacks)
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> tools/perf/design.txt | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/tools/perf/design.txt b/tools/perf/design.txt
> index 67e5d0c..63a0e6f 100644
> --- a/tools/perf/design.txt
> +++ b/tools/perf/design.txt
> @@ -454,7 +454,6 @@ So to start with, in order to add HAVE_PERF_EVENTS to your Kconfig, you
> will need at least this:
> - asm/perf_event.h - a basic stub will suffice at first
> - support for atomic64 types (and associated helper functions)
> - - set_perf_event_pending() implemented
>
> If your architecture does have hardware capabilities, you can override the
> weak stub hw_perf_event_init() to register hardware counters.
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
parent reply other threads:[~2014-01-13 10:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bd81da79fb3cfca28d7e990566c8794ec14328c7.1385647452.git.baruch@tkos.co.il>]
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=20140113104839.GN4944@tarshish \
--to=baruch@tkos.co.il \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®