From: Adrian Bunk <bunk@fs.tum.de>
To: linux-kernel@vger.kernel.org
Subject: [2/4] [2.6 patch] better i386 CPU selection
Date: Sun, 14 Sep 2003 00:27:52 +0200 [thread overview]
Message-ID: <20030913222751.GP27368@fs.tum.de> (raw)
In-Reply-To: <20030913222443.GN27368@fs.tum.de>
- move "struct movsl_mask movsl_mask" to usercopy.c
(CONFIG_X86_INTEL_USERCOPY is used on non-Intel CPUs)
diffstat output:
kernel/cpu/intel.c | 7 -------
lib/usercopy.c | 7 +++++++
2 files changed, 7 insertions(+), 7 deletions(-)
--- linux-2.6.0-test5/arch/i386/kernel/cpu/intel.c.old 2003-09-13 18:06:45.000000000 +0200
+++ linux-2.6.0-test5/arch/i386/kernel/cpu/intel.c 2003-09-13 18:08:00.000000000 +0200
@@ -13,13 +13,6 @@
extern int trap_init_f00f_bug(void);
-#ifdef CONFIG_X86_INTEL_USERCOPY
-/*
- * Alignment at which movsl is preferred for bulk memory copies.
- */
-struct movsl_mask movsl_mask;
-#endif
-
/*
* Early probe support logic for ppro memory erratum #50
*
--- linux-2.6.0-test5/arch/i386/lib/usercopy.c.old 2003-09-13 18:06:56.000000000 +0200
+++ linux-2.6.0-test5/arch/i386/lib/usercopy.c 2003-09-13 18:07:51.000000000 +0200
@@ -12,6 +12,13 @@
#include <asm/uaccess.h>
#include <asm/mmx.h>
+#ifdef CONFIG_X86_INTEL_USERCOPY
+/*
+ * Alignment at which movsl is preferred for bulk memory copies.
+ */
+struct movsl_mask movsl_mask;
+#endif
+
static inline int __movsl_is_ok(unsigned long a1, unsigned long a2, unsigned long n)
{
#ifdef CONFIG_X86_INTEL_USERCOPY
next prev parent reply other threads:[~2003-09-13 22:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 22:24 [0/4] [2.6 patch] better i386 CPU selection Adrian Bunk
2003-09-13 22:26 ` [1/4] " Adrian Bunk
2003-09-15 6:46 ` Michael Neuffer
2003-09-15 6:52 ` Adrian Bunk
2003-09-15 7:02 ` Michael Neuffer
2003-09-13 22:27 ` Adrian Bunk [this message]
2003-09-13 22:28 ` [3/4] " Adrian Bunk
2003-09-13 22:29 ` [4/4] " Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2003-09-25 18:02 [0/4] " Adrian Bunk
2003-09-25 18:05 ` [2/4] " Adrian Bunk
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=20030913222751.GP27368@fs.tum.de \
--to=bunk@fs.tum.de \
--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