Date: Tue, 15 May 2012 11:38:43 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-hackers@freebsd.org Cc: Eric McCorkle <eric@shadowsun.net> Subject: Re: GSoC Project: EFI on amd64/i386 Message-ID: <201205151138.43864.jhb@freebsd.org> In-Reply-To: <alpine.BSF.2.00.1205150955440.17247@gw.reifenberger.com> References: <4FA95960.7090908@shadowsun.net> <4FB17B85.9080701@shadowsun.net> <alpine.BSF.2.00.1205150955440.17247@gw.reifenberger.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, May 15, 2012 4:00:44 am Michael Reifenberger wrote: > On Mon, 14 May 2012, Eric McCorkle wrote: > ... > > If I understand things correctly, boot2 handles the switch to > > protected mode (as well as enabling A20), both loader(8) and the > > kernel begin their execution in a protected mode environment. Can I > > get an absolute confirmation on this? Obviously if this is not the > > case, then there will need to be another (protected mode) entry point > > into the kernel. > > > > No. > *boot* and *loader should be the same on X32 and AMD64. > The kernel seems to switch to long mode in /sys/amd64/amd64/mpboot.S No. That is only for AP startup. The loader switches to long mode for an amd64 kernel before it starts the kernel. For i386, boot2 and the loader both start the kernel while running in flat 32-bit protected mode (so no paging). -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201205151138.43864.jhb>