From: tip-bot for Ingo Molnar <mingo@elte.hu>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, paulmck@linux.vnet.ibm.com,
hpa@zytor.com, mingo@redhat.com, rostedt@goodmis.org,
tglx@linutronix.de, mingo@elte.hu
Subject: [tip:perf/core] core_kernel_data(): Fix architectures that do not define _sdata
Date: Thu, 19 May 2011 23:37:09 GMT [thread overview]
Message-ID: <tip-i878c8a0e0g0ep4v7i6vxnhz@git.kernel.org> (raw)
Commit-ID: c5fc472171ec4f96d06d1ac039d88f9b89bb95db
Gitweb: http://git.kernel.org/tip/c5fc472171ec4f96d06d1ac039d88f9b89bb95db
Author: Ingo Molnar <mingo@elte.hu>
AuthorDate: Fri, 20 May 2011 01:22:14 +0200
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Fri, 20 May 2011 01:27:16 +0200
core_kernel_data(): Fix architectures that do not define _sdata
Some architectures such as Alpha do not define _sdata but _data:
kernel/built-in.o: In function `core_kernel_data':
kernel/extable.c:77: undefined reference to `_sdata'
So expand the scope of the data range to the text addresses too,
this might be more correct anyway because this way we can
cover readonly variables as well.
Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Link: http://lkml.kernel.org/n/tip-i878c8a0e0g0ep4v7i6vxnhz@git.kernel.org
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/extable.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/extable.c b/kernel/extable.c
index c2d625f..d44aac0 100644
--- a/kernel/extable.c
+++ b/kernel/extable.c
@@ -74,7 +74,7 @@ int core_kernel_text(unsigned long addr)
int core_kernel_data(unsigned long addr)
{
- if (addr >= (unsigned long)_sdata &&
+ if (addr >= (unsigned long)_stext &&
addr < (unsigned long)_edata)
return 1;
return 0;
reply other threads:[~2011-05-19 23:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=tip-i878c8a0e0g0ep4v7i6vxnhz@git.kernel.org \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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