From: Arnd Bergmann <arnd@arndb.de>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Philippe Elie <phil.el@wanadoo.fr>
Subject: Re: [PATCH] s390 (6/6): oprofile for s390.
Date: Thu, 29 Apr 2004 14:39:56 +0200 [thread overview]
Message-ID: <200404291439.58788.arnd@arndb.de> (raw)
Martin Schwidefsky wrote:
> > > +#if defined(CONFIG_OPROFILE) || defined(CONFIG_OPROFILE_MODULE)
> >
> > this must depend on CONFIG_PROFILING ?
>
> Currently oprofile is the only profiling method implemented for s390.
> So this doesn't really change much. But in principle you are right,
> as soon as a second profiling method gets added this would have to
> be changed to CONFIG_PROFILING.
No, it should already be changed now, because the code is also needed
for readprofile. CONFIG_PROFILING should enable the generic profiling
code here, even if CONFIG_OPROFILE is not set.
Note that the identical code on i386 is always compiled in, regardless
of CONFIG_PROFILING and CONFIG_OPROFILE.
Arnd <><
===
Enable basic profiling code on s390 depending on CONFIG_PROFILING,
not CONFIG_OPROFILE.
===== arch/s390/kernel/time.c 1.25 vs edited =====
--- 1.25/arch/s390/kernel/time.c Wed Apr 28 19:51:41 2004
+++ edited/arch/s390/kernel/time.c Thu Apr 29 11:13:36 2004
@@ -179,7 +179,7 @@
#endif /* CONFIG_ARCH_S390X */
-#if defined(CONFIG_OPROFILE) || defined(CONFIG_OPROFILE_MODULE)
+#ifdef CONFIG_PROFILING
extern char _stext, _etext;
/*
@@ -223,7 +223,7 @@
}
#else
#define s390_do_profile(regs) do { ; } while(0)
-#endif /* CONFIG_OPROFILE */
+#endif /* CONFIG_PROFILING */
/*
===== arch/s390/oprofile/Kconfig 1.1 vs edited =====
--- 1.1/arch/s390/oprofile/Kconfig Wed Apr 28 19:51:41 2004
+++ edited/arch/s390/oprofile/Kconfig Thu Apr 29 11:16:21 2004
@@ -5,8 +5,8 @@
config PROFILING
bool "Profiling support (EXPERIMENTAL)"
help
- Say Y here to enable the extended profiling support mechanisms used
- by profilers such as OProfile.
+ Say Y here to enable profiling support mechanisms used by
+ profilers such as readprofile or OProfile.
config OPROFILE
next reply other threads:[~2004-04-29 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 12:39 Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-29 8:18 Martin Schwidefsky
2004-04-28 16:51 Martin Schwidefsky
2004-04-29 6:04 ` Philippe Elie
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=200404291439.58788.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phil.el@wanadoo.fr \
--cc=schwidefsky@de.ibm.com \
/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
Powered by JetHome