Re: 32/64bit KSE issues?

On Saturday 31 March 2007 03:16, Andriy Gapon wrote:
on 31/03/2007 05:23 Daniel Eischen said the following:
On Fri, 30 Mar 2007, David E. Cross wrote:

I recently ran into a problem where the 32bit JVM won't run on a 64bit host.
I, and at least one other person in -java thinks it has to do with 32 bit KSE
on a 64bit kernel (I have a vague memory on this somewheres WAY back). Is
this still the issue? Could someone point me in the general direction of the
specifics of the problem (if they exist, if not, I may try to create a
simpler test case then java)?

I tried a few searches, but nothing matching what I remembered came up.

No, you can't run 32-bit libpthread on 64-bit kernel. There
are no compatiblity hooks in the kernel to handle 32-bit kse
interfaces. It is really too messy to provide it.


Daniel,

maybe you can send a followup to the following ?
http://www.freebsd.org/cgi/query-pr.cgi?pr=110655

Given that 32-bit libthr also doesn't work on 64-bit kernel, the only
option is to map thread libs to libc_r via libmap32.conf.
BTW, next time there is a poll about retiring libc_r please count me
against for precisely this reason.

I plan on making sure full 32-bit compat exists for both libthr and
libpthread and backporting it to 6.x for work. Very few things are
too hard to wrap with a 32-bit shim.

--
John Baldwin
_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: 32/64bit KSE issues?
    ... and at least one other person in -java thinks it has to do with 32 bit KSE ... you can't run 32-bit libpthread on 64-bit kernel. ... are no compatiblity hooks in the kernel to handle 32-bit kse ... Given that 32-bit libthr also doesn't work on 64-bit kernel, ...
    (freebsd-arch)
  • HEADSUP: KSE about to become a kernel option
    ... If you use a GENERIC kernel, then this change won't affect you ... properly with the KSE code in the kernel). ... Out of this I hope to determine which thread implementation ...
    (freebsd-current)
  • Re: KSE, libpthread & libthr: almost newbie question
    ... They use KSE in different ways: libpthread uses N:M model and libthr uses 1:1 model, but bot use KSE to work. ... How will be possible to sue these libraries when KSE will be optional, on kernel without KSE?! ... The FreeBSD kernel actually implements a good three different threading models: ... Notice that this isn't just about code complexity, but also about scheduler overhead. ...
    (freebsd-current)
  • Re: KSE, libpthread & libthr: almost newbie question
    ... They use KSE in different ways: libpthread uses N:M model and libthr uses 1:1 model, but bot use KSE to work. ... How will be possible to sue these libraries when KSE will be optional, on kernel without KSE?! ... The FreeBSD kernel actually implements a good three different threading models: ... Notice that this isn't just about code complexity, but also about scheduler overhead. ...
    (freebsd-current)
  • Re: effect of sched_set{param|scheduler} on MT-process
    ... > interrupted and another entity is run once its context is restored. ... Threads - that is multiple flows of control within a process can be ... The kernel is not aware of multiple threads within the process. ... N threads to 1 KSE. ...
    (comp.unix.programmer)