From: Vivek Goyal <vgoyal@in.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Jean Delvare <khali@linux-fr.org>, Andi Kleen <ak@suse.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Patch "i386: Relocatable kernel support" causes instant reboot
Date: Thu, 21 Dec 2006 09:24:58 +0530 [thread overview]
Message-ID: <20061221035458.GE30299@in.ibm.com> (raw)
In-Reply-To: <20061221022601.GB30299@in.ibm.com>
On Thu, Dec 21, 2006 at 07:56:01AM +0530, Vivek Goyal wrote:
[..]
> > # Manual, Mixing 16-bit and 32-bit code, page 16-6)
> >
> > .byte 0x66, 0xea # prefix + jmpi-opcode
> > -code32: .long 0x1000 # will be set to 0x100000
> > - # for big kernels
> > +code32: .long startup_32 # will be set to %cs+startup_32
> > .word __BOOT_CS
> > +.code32
> > +startup_32:
> > + movl $(__BOOT_DS), %eax
> > + movl %eax, %ds
> > + movl %eax, %es
> > + movl %eax, %fs
> > + movl %eax, %gs
> > + movl %eax, %ss
> > +
> > + xorl %eax, %eax
> > +1: incl %eax # check that A20 really IS enabled
> > + movl %eax, 0x00000000 # loop forever if it isn't
> > + cmpl %eax, 0x00100000
> > + je 1b
> > +
> > + # Jump to the 32bit entry point
> > + jmpl *(code32_start - start + (DELTA_INITSEG << 4))(%esi)
>
> Hi Eric,
>
> I got a basic query. Why have we introduced this additional jump to
> startup_32 in the same file? Won't it work if we stick to old method of
> enabling protected mode and then directly taking a jmp to startup_32 in
> arch/i386/kernel/head.S. Am I missing something obivious?
>
Sorry, I meant arch/i386/boot/compressed/head.S and not arch/i386/kernel/head.S
Thanks
Vivek
next prev parent reply other threads:[~2006-12-21 14:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061220141808.e4b8c0ea.khali@linux-fr.org>
2006-12-20 14:00 ` Patch "i386: Relocatable kernel support" causes instant reboot Eric W. Biederman
[not found] ` <20061220214340.f6b037b1.khali@linux-fr.org>
2006-12-20 22:22 ` Eric W. Biederman
[not found] ` <20061221101240.f7e8f107.khali@linux-fr.org>
[not found] ` <20061221102232.5a10bece.khali@linux-fr.org>
2006-12-21 10:32 ` Eric W. Biederman
2006-12-21 1:08 ` Vivek Goyal
2006-12-21 12:32 ` Eric W. Biederman
2006-12-21 2:26 ` Vivek Goyal
2006-12-21 3:54 ` Vivek Goyal [this message]
2006-12-21 13:13 ` Jean Delvare
2006-12-21 3:13 ` Vivek Goyal
2006-12-21 13:59 ` Jean Delvare
2006-12-21 17:45 ` Alexander van Heukelum
2006-12-21 20:44 ` Vivek Goyal
2006-12-22 8:08 ` Jean Delvare
2006-12-22 10:40 ` Vivek Goyal
2006-12-22 22:22 ` Jean Delvare
2006-12-22 22:37 ` Eric W. Biederman
2006-12-26 12:43 ` Segher Boessenkool
2006-12-26 14:03 ` Jean Delvare
2006-12-27 4:00 ` Vivek Goyal
2006-12-27 4:25 ` Segher Boessenkool
2007-01-01 21:39 ` Jean Delvare
2007-01-02 6:11 ` Vivek Goyal
2007-01-02 9:29 ` Jean Delvare
2007-01-02 13:44 ` Segher Boessenkool
[not found] ` <20061221145401.07bfe408.khali@linux-fr.org>
2006-12-21 3:40 ` Vivek Goyal
2006-12-21 14:22 ` Jean Delvare
2006-12-21 4:41 ` Vivek Goyal
2006-12-21 8:55 ` Jean Delvare
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=20061221035458.GE30299@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=ak@suse.de \
--cc=ebiederm@xmission.com \
--cc=khali@linux-fr.org \
--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