From: Pavel Machek <pavel@suse.cz>
To: torvalds@transmeta.com, kernel list <linux-kernel@vger.kernel.org>
Subject: Tiny cleanup of entry.S
Date: Fri, 20 Apr 2001 20:17:13 +0200 [thread overview]
Message-ID: <20010420201713.A981@bug.ucw.cz> (raw)
Hi!
I believe that no ifdefs are worth several bytes of code expansion...
Index: arch/i386/kernel/head.S
===================================================================
RCS file: /home/cvs/Repository/linux/arch/i386/kernel/head.S,v
retrieving revision 1.1.1.1
diff -u -u -r1.1.1.1 head.S
--- arch/i386/kernel/head.S 2000/09/04 16:54:43 1.1.1.1
+++ arch/i386/kernel/head.S 2001/02/13 13:44:48
@@ -169,9 +169,7 @@
rep
movsl
1:
-#ifdef CONFIG_SMP
checkCPUtype:
-#endif
movl $-1,X86_CPUID # -1 for no CPUID initially
@@ -244,9 +242,7 @@
orl $2,%eax # set MP
2: movl %eax,%cr0
call check_x87
-#ifdef CONFIG_SMP
incb ready
-#endif
lgdt gdt_descr
lidt idt_descr
ljmp $(__KERNEL_CS),$1f
@@ -278,9 +274,7 @@
jmp L6 # main should never return here, but
# just in case, we know what happens.
-#ifdef CONFIG_SMP
ready: .byte 0
-#endif
/*
* We depend on ET to be correct. This checks for 287/387.
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
reply other threads:[~2001-04-20 18:23 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=20010420201713.A981@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).