On Wed, Jan 08, 2003 at 04:03:52PM -0800, David S. Miller wrote:
> From: Linus Torvalds <torvalds@transmeta.com>
> Date: Wed, 8 Jan 2003 16:02:24 -0800 (PST)
>
> Or you can use an /etc/systype file that contains information.
>
> That sounds fine to me.
>
> A funny way to initialize this could be by reading System.map
> and seeing how many significant hexidecimal digits are used
> to list the kernel symbol addresses :-)
Don't try it, the perversity of MIPS will break you :)
Just to clarify something that I saw getting lost in this discussion:
Oprofile doesn't need to become built as a 64-bit binary, just
configured to accept 64-bit kernels. So this doesn't rule out using a
32-bit oprofile (i.e. not needing a 64-bit libc) on a 64-bit kernel.
It just means that we need to specify it somehow.
John, speaking of MIPS perversity: MIPS64 kernels can come in ELF32
files. So you may just want to make this a configure-time option.
-- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jan 15 2003 - 22:00:26 EST