From: "Alexander van Heukelum" <heukelum@fastmail.fm>
To: "Cyrill Gorcunov" <gorcunov@gmail.com>,
"Ingo Molnar" <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
"Thomas Gleixner" <tglx@linutronix.de>
Cc: "LKML" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] x86: trampoline_64.S - use predefined constants with simplification
Date: Wed, 28 Jan 2009 22:52:57 +0100 [thread overview]
Message-ID: <1233179577.19086.1297291037@webmail.messagingengine.com> (raw)
In-Reply-To: <20090128202125.GA32555@localhost>
On Wed, 28 Jan 2009 23:21:25 +0300, "Cyrill Gorcunov"
<gorcunov@gmail.com> said:
> Impact: cleanup
>
> We may use macros from processor-flags.h instead
> of hardcoding bits. Actually it's not direct mapping
> of old instructions with new ones -- BTS does change
> CF flag while MOV does not. But i didn't find any
> dependency on CF in this code.
>
> Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org>
> ---
>
> Please review
Looks good.
Acked-by: Alexander van Heukelum <heukelum@fastmail.fm>
> arch/x86/kernel/trampoline_64.S | 19 +++++++++----------
> 1 file changed, 9 insertions(+), 10 deletions(-)
>
> Index: linux-2.6.git/arch/x86/kernel/trampoline_64.S
> ===================================================================
> --- linux-2.6.git.orig/arch/x86/kernel/trampoline_64.S
> +++ linux-2.6.git/arch/x86/kernel/trampoline_64.S
> @@ -29,6 +29,7 @@
> #include <asm/page.h>
> #include <asm/msr.h>
> #include <asm/segment.h>
> +#include <asm/processor-flags.h>
>
> .section .rodata, "a", @progbits
>
> @@ -37,7 +38,7 @@
> ENTRY(trampoline_data)
> r_base = .
> cli # We should be safe anyway
> - wbinvd
> + wbinvd
> mov %cs, %ax # Code and data in the same place
> mov %ax, %ds
> mov %ax, %es
> @@ -73,9 +74,8 @@ r_base = .
> lidtl tidt - r_base # load idt with 0, 0
> lgdtl tgdt - r_base # load gdt with whatever is appropriate
>
> - xor %ax, %ax
> - inc %ax # protected mode (PE) bit
> - lmsw %ax # into protected mode
> + mov $X86_CR0_PE, %ax # protected mode (PE) bit
> + lmsw %ax # into protected mode
>
> # flush prefetch and jump to startup_32
> ljmpl *(startup_32_vector - r_base)
> @@ -86,9 +86,8 @@ startup_32:
> movl $__KERNEL_DS, %eax # Initialize the %ds segment register
> movl %eax, %ds
>
> - xorl %eax, %eax
> - btsl $5, %eax # Enable PAE mode
> - movl %eax, %cr4
> + movl $X86_CR4_PAE, %eax
> + movl %eax, %cr4 # Enable PAE mode
>
> # Setup trampoline 4 level pagetables
> leal (trampoline_level4_pgt - r_base)(%esi), %eax
> @@ -99,9 +98,9 @@ startup_32:
> xorl %edx, %edx
> wrmsr
>
> - xorl %eax, %eax
> - btsl $31, %eax # Enable paging and in turn activate Long Mode
> - btsl $0, %eax # Enable protected mode
> + # Enable paging and in turn activate Long Mode
> + # Enable protected mode
> + movl $(X86_CR0_PG | X86_CR0_PE), %eax
> movl %eax, %cr0
>
> /*
--
Alexander van Heukelum
heukelum@fastmail.fm
--
http://www.fastmail.fm - Faster than the air-speed velocity of an
unladen european swallow
next prev parent reply other threads:[~2009-01-28 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 20:21 [PATCH -tip] x86: trampoline_64.S - use predefined constants with simplification Cyrill Gorcunov
2009-01-28 21:52 ` Alexander van Heukelum [this message]
2009-01-29 13:36 ` Ingo Molnar
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=1233179577.19086.1297291037@webmail.messagingengine.com \
--to=heukelum@fastmail.fm \
--cc=gorcunov@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.