From: Frank Cornelis <Frank.Cornelis@rug.ac.be>
To: <linux-kernel@vger.kernel.org>
Subject: fixes: current_text_addr
Date: Sat, 27 Oct 2001 17:26:46 +0200 (MEST) [thread overview]
Message-ID: <Pine.GSO.4.31.0110271724540.16025-100000@eduserv.rug.ac.be> (raw)
Hi,
Next patch fixes the current_text_addr macro to work also with optimized
code.
There is also a documentation fix included.
Frank.
--- processor.h.orig Fri Oct 26 16:37:51 2001
+++ processor.h Fri Oct 26 16:39:15 2001
@@ -22,7 +22,8 @@
* Default implementation of macro that returns current
* instruction pointer ("program counter").
*/
-#define current_text_addr() ({ void *pc; __asm__("movl $1f,%0\n1:":"=g" (pc)); pc; })
+#define current_text_addr() \
+({ void *pc; __asm__ __volatile__("movl $1f,%0\n1:":"=g" (pc)); pc; })
/*
* CPU type and hardware bug flags. Kept separately for each CPU.
--- threads.h.orig Fri Oct 26 16:46:52 2001
+++ threads.h Fri Oct 26 16:47:19 2001
@@ -5,7 +5,7 @@
/*
* The default limit for the nr of threads is now in
- * /proc/sys/kernel/max-threads.
+ * /proc/sys/kernel/threads-max.
*/
#ifdef CONFIG_SMP
reply other threads:[~2001-10-27 15:26 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=Pine.GSO.4.31.0110271724540.16025-100000@eduserv.rug.ac.be \
--to=frank.cornelis@rug.ac.be \
--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;
as well as URLs for NNTP newsgroup(s).