JDK-8166730 : JEP 294: Linux/s390x Port
  • Type: JEP
  • Component: hotspot
  • Sub-Component: compiler
  • Priority: P3
  • Status: Closed
  • Resolution: Delivered
  • Fix Versions: 9
  • Submitted: 2016-09-26
  • Updated: 2019-08-13
  • Resolved: 2017-05-03
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Description
Summary
-------

Port JDK 9 to Linux/s390x.


Motivation
----------

[s390x][1] (also known under the names "System z" or "z/Architecture")
is a mainframe architecture developed and supported by IBM. Several
Linux distributions including [Ubuntu][2], RHEL/[Fedora][3] and
[SuSE][4] run on s390x.

Current cloud deployments with packages like TomEE, Cassandra, Spark,
Hadoop and Neo4j, to name just a few, rely heavily on Java. Because
most of these packages are open source they run best on OpenJDK, which
is currently not available for Linux/s390x.

The reason for this JEP is to resolve this deficiency.

Description
-----------

SAP has a complete (i.e., template interpreter, C1, and C2 JIT) and
certified (Java SE 1.4-8) s390x port which has been used in production for
years. In the [s390x Port Project][6] we have already
contributed this port, which runs on IBM System z models z10 or newer
(64-bit only).

The focus of this JEP is not the porting effort itself, which has been
mostly completed, but rather the integration of the port into the
JDK 9 master repository.

Currently we have a [patch queue][7] with less than 10 changesets and
with very few shared changes which shouldn't affect current platforms
at all. Besides two minimal build changes in the top-level and `jdk`
repositories, all the other changes are in the `hotspot` repository only.

We have already started opening [JBS issues][8] for the shared changes and
some of them are already under review.

Alternatives
------------

Currently, the [Zero port][5] can be used to run the JDK on
Linux/s390x but it is quite slow (because it only uses the old,
deprecated C++ interpreter) and is not very well tested. It is no
real alternative for running workloads like application servers or
database applications written in Java.

[IBM's Developer Kit for Linux][10] is also available for Linux/s390x
but it is currently not open source and Java applications usually
require some configuration/tuning in order to run with it. Also, it can
not be used for testing new features of upcoming Java versions because
it is only released after the JDK itself is GA.

Testing
-------

This port has been used in production for years within our
commercial SAP JVM offering. We are already building and testing
the OpenJDK version of the port daily (by running `jtreg` and JCK tests, SPEC
benchmarks, and several SAP applications), and are committed to do so in
the future. Of course we will also maintain the port in the future and
update it conforming to all upcoming requirements.

Risks and Assumptions
---------------------

Unlike our previous [PowerPC/AIX Port][9], this port requires only
minimal changes to the existing code base, because:

 - s390x is a CISC architecture with a strong memory model
 - no OS-relevant changes are required because we only target Linux

We don't foresee any impact on the existing platforms at all.


[1]: https://en.wikipedia.org/wiki/IBM_System_z
[2]: https://wiki.ubuntu.com/S390X
[3]: https://fedoraproject.org/wiki/Architectures/s390x
[4]: https://www.suse.com/products/systemz
[5]: http://openjdk.java.net/projects/zero/
[6]: http://openjdk.java.net/projects/s390x-port/
[7]: http://cr.openjdk.java.net/~goetz/wr16/s390x_patch_queue/hotspot/
[8]: https://bugs.openjdk.java.net/browse/JDK-8166561?jql=CPU%20%3D%20%22s390x%22
[9]: http://openjdk.java.net/projects/ppc-aix-port/
[10]: http://www.ibm.com/developerworks/java/jdk/linux/download.html

Comments
[~simonis] Volker, please close this JEP - press "Delivered" button.
02-05-2017

[~simonis] Volker, changes were integrated into jdk9/jdk9 master repository. Please, mark JEP as Integrated.
22-11-2016

Moved dates since I don't know when jdk9/hs will be stable to push into jdk9/dev.
07-11-2016

Oops, sorry for the workflow churn -- I accidentally hit the "Target" button too soon, and that was the only way to unwind it.
15-10-2016

[~simonis] I set due and integration date which are required for targeted JEP. Please, adjust them if you think they are not reasonable.
11-10-2016

According to the JEP process "a credible engineering plan should be documented in subtasks of the JEP issue" before a JEP can be "proposed to target". But this JEP is small with respect to its extent. All the required changes are already linked in the "relates to" section (some of them are already pushed, others are already reviewed and the remaining ones are currently under review). So I don't think it's worth while to create additional "artificial" subtasks before I'll propose this JEP to target.
07-10-2016