Date: Mon, 22 Mar 2010 13:01:18 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: obrien@freebsd.org Cc: yanefbsd@gmail.com, freebsd-current@freebsd.org, nwhitehorn@freebsd.org, swhetzel@gmail.com Subject: Re: HEADS UP: COMPAT_IA32 renamed COMPAT_FREEBSD32 Message-ID: <20100322.130118.80747594461967718.imp@bsdimp.com> In-Reply-To: <20100322185331.GA88847@dragon.NUXI.org> References: <20100312171758.GB31089@dragon.NUXI.org> <20100312.125032.270969355930630649.imp@bsdimp.com> <20100322185331.GA88847@dragon.NUXI.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20100322185331.GA88847@dragon.NUXI.org>
"David O'Brien" <obrien@freebsd.org> writes:
: On Fri, Mar 12, 2010 at 12:50:32PM -0700, M. Warner Losh wrote:
: > : On Thu, Mar 11, 2010 at 07:24:23PM -0700, M. Warner Losh wrote:
: > So the issue isn't as cut and dried as you might think. There's
: > multiple different conventions used here in addition to your simple
: > example.
:
: I guess we'd have to take a poll to find out. Seems pretty cut and dried
: to me. COMPAT_FREEBSDn has an established context that does not match
: this new usage. That is - same bit'ness, compatibility with an older
: FreeBSD API for the same architecture. All the other COMPAT_* are for
: foreign ABI compatibility. COMPAT_LINUX32 possibly should have been
: "COMPAT_LINUX_X86_64". (or is it MI and is usable as-is for PowerPC
: and MIPS? I haven't looked that deeply at the code.)
no, COMPAT_LINUX32 is the right name. While we don't have PowerPC or
MIPS linux emulation bits in the kernel, the code if for dealing with
running 32-bit binaries on 64-bit machines. There may be a little
leakage of x86 specific goo here, but not a lot.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100322.130118.80747594461967718.imp>