The Linux Foundation

 

Become an Individual Member

LSB:PM:LSB Compliant JVM

From The Linux Foundation

Contents

Open Issues

Milestones and tasks are not finished. More people may need to be added to the project list. The project may need a different owner.

Vision

Having at least one LSB-compliant and Sun-certified Java VM per LSB architecture is very high on the request list from ISVs. While it may be beyond the scope of this project to actually build and maintain it, we must make sure that JVM vendors have everything they need in the LSB.

Milestones

A rough proposed schedule for this project. When we anticipate that we will reach certain milestones. Also, if the project has an absolutely-must-be-completed-by date, mention it here.

Milestone Plan Date Outlook Comments
Create a "missing interface" list. 3/12/2008
Decide on truly missing interfaces. 3/21/2008 This will be conducted via the mailing list, and possibly the conference call.
Add missing interfaces to LSB 4.0.
Get code changes pushed upstream for interfaces that are not appropriate, if any.
Build OpenJDK, or a derivative, to be LSB-compliant.
Work with Linux JVM vendors to achieve LSB builds.

Resources

No resources have yet been dedicated to this project.

Hardware

No hardware has yet been dedicated to this project.

Contacts

List of people who are working on the project and their roles.

Name Role
Jeff Licquia Project Owner


Tasks

Tasks will map many-to-one to milestones. Tasks are specific actionable work items that need to be completed in order to reach a milestone

Active

Task Owner Status Outlook

Completed

Task Owner Status Outlook
Create list of missing interfaces. Jeff Licquia List from Mats is captured below; list from George Kraft is here.

Pending

Tasks that can't be scheduled yet because they are waiting on some other task or external entity

Task Owner Status Outlook
Start evaluation of missing interfaces on list/call. Jeff Licquia Not started.
Determine if the LSB can be a feasible binary target for Sun JVM certification. Jeff Licquia & Sun contact Not started.

Comments

There may be interesting information on the LsbJava page.

Jeff Licquia 12:13, 12 March 2008 (PDT)

List varies depending on version/vendor. These seem to be common:

  • libXext: XMissingExtension, XextAddDisplay, XextCreateExtension, XextFindDisplay, XextRemoveDisplay
  • libXtst (missing lib): XTestFakeButtonEvent, XTestFakeKeyEvent, XTestFakeMotionEvent, XTestGrabControl, XTestQueryExtension
  • libXt: applicationShellClassRec, colorConvertArgs
  • libX11: _XEatData, _XFlush, _XRead, _XReply, _Xdebug
  • libc: backtrace, backtrace_symbols, madvise, memalign, mincore, sendfile, syscall

Additional notes:

  1. Some versions use ptrace or mtrace, sysinfo, gnu_get_libc_{release,version}, dl_iterate_phdr from libc
  2. Some versions use pthread_getattr_np from libpthread
  3. some versions link with Xprint (libXp), not an LSB candidate
  4. some versions use __snd* interfaces from alsa (not recommended by ALSA upstream team)

Comments:

  • Xext*Display and Xext*Extension from libXext (see bug 1757). Xext is an LSB library, but these interfaces were in the past omitted on the theory they weren't needed by applications, only by extension writers, with "how to write an X extension" being out of the scope of the LSB. This seems not to be true, however, as it seems many applications use these to query details about available extensions.
  • libXtst (see bug 2020). Library containing the API to the XTest extension, which includes two sets of interfaces, 15 XTest interfaces and 14 XRecord interfaces. XTest was originally developed as a hook for testing, and including it would actually considerably help our test suite in this area, the patch is currently huge because it must pull in the interfaces since they're not in LSB. But the concept of event injection has turned out to be useful elsewhere, and is used by many projects including Accessibility. At the moment, libXtst is proposed to add, but only the XTest interfaces. JVM's use 4 of the 15 interfaces; of the 15, 11 are in the original XTest spec written by Kieron Drake (a formner colleague of Mats'); we have to check on the other four.
  • LSB recommends posix_madvise, posix_memalign instead of madvise, memalign (the former are in LSB)

-- Mats (copied from task list, above)

Archived Weekly Status Reports


[Article] [Discussion] [View source] [History]