[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <4c54761865d40210be0628cb84701afc5d57b5d8.1390686193.git.baruch@tkos.co.il>
Date: Sat, 25 Jan 2014 23:50:23 +0200
From: Baruch Siach <baruch@...s.co.il>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Paul Mackerras <paulus@...ba.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>
Cc: linux-kernel@...r.kernel.org, Baruch Siach <baruch@...s.co.il>
Subject: [PATCH RESEND] perf: design.txt: remove mention of set_perf_event_pending
set_perf_event_pending() was removed in e360adbe (irq_work: Add generic hardirq
context callbacks)
Signed-off-by: Baruch Siach <baruch@...s.co.il>
---
Resending with lkml added to Cc.
---
tools/perf/design.txt | 1 -
1 file changed, 1 deletion(-)
diff --git a/tools/perf/design.txt b/tools/perf/design.txt
index 67e5d0cace85..63a0e6f04a01 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.
--
1.8.5.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists