public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: eranian@googlemail.com
To: linux-kernel@vger.kernel.org
Subject: [patch 01/21] perfmon2 minimal:  generic hooks
Date: Mon, 09 Jun 2008 15:33:36 -0700 (PDT)	[thread overview]
Message-ID: <484dafc0.0af6660a.55fa.617b@mx.google.com> (raw)

This simple patch adds the perfmon subdirectory to the
top-level Makefile.

It also adds the perfmon2 context pointer to the task
struct. The field points to the perfmon context structure
only when a thread is monitored.

Signed-off-by: Stephane Eranian <eranian@gmail.com>

--

Index: o/Makefile
===================================================================
--- o.orig/Makefile	2008-06-05 11:00:37.000000000 +0200
+++ o/Makefile	2008-06-05 11:00:43.000000000 +0200
@@ -607,7 +607,7 @@
 
 
 ifeq ($(KBUILD_EXTMOD),)
-core-y		+= kernel/ mm/ fs/ ipc/ security/ crypto/ block/
+core-y		+= kernel/ mm/ fs/ ipc/ security/ crypto/ block/ perfmon/
 
 vmlinux-dirs	:= $(patsubst %/,%,$(filter %/, $(init-y) $(init-m) \
 		     $(core-y) $(core-m) $(drivers-y) $(drivers-m) \
Index: o/include/linux/sched.h
===================================================================
--- o.orig/include/linux/sched.h	2008-06-05 11:00:37.000000000 +0200
+++ o/include/linux/sched.h	2008-06-05 11:00:43.000000000 +0200
@@ -95,6 +95,7 @@
 struct futex_pi_state;
 struct robust_list_head;
 struct bio;
+struct pfm_context;
 
 /*
  * List of flags we want to share for kernel threads,
@@ -1303,6 +1304,9 @@
 	int latency_record_count;
 	struct latency_record latency_record[LT_SAVECOUNT];
 #endif
+#ifdef CONFIG_PERFMON
+	struct pfm_context *pfm_context;
+#endif
 };
 
 /*

-- 


             reply	other threads:[~2008-06-09 22:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-09 22:33 eranian [this message]
2008-06-10 14:24 ` [patch 01/21] perfmon2 minimal: generic hooks Arjan van de Ven

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=484dafc0.0af6660a.55fa.617b@mx.google.com \
    --to=eranian@googlemail.com \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox