Date: Thu, 29 Jan 2004 17:20:47 -0500 (EST) From: Brian Tao <taob@risc.org> To: "David O'Brien" <obrien@freebsd.org> Cc: freebsd-amd64@freebsd.org Subject: Re: New AMD64 owner Message-ID: <Pine.GSO.4.21.0401291714070.26036-100000@tor-adm1.nbc.attcanada.ca> In-Reply-To: <20040129185426.GA93242@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 29 Jan 2004, David O'Brien wrote:
>
> It is a CPU mode issue. If you think back to your brand new i386
> and Windows 95, the CPU was switched back into real mode when you
> ran a MS-Windows 3.1 program. Along with MS-Windows 95 doing
> "Thunking" for system services.
Ah, gotcha... I had not thought about the parallels between this
and the 16-to-32 transition. Cool, things make a lot more sense when
I think about it that way.
> Yes -- assuming you are talking about dual-booting. My FreeBSD/i386
> build machine is actually an Athlon64 machine that is run purely and
> only in 32-bit mode. Athlon64 is the fastest 32-bit x86 machine in
> the world today.
Damn right. :)
--
Brian Tao (BT300, taob@risc.org)
"Though this be madness, yet there is method in't"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.21.0401291714070.26036-100000>