Difference between revisions of "Hotswap"

From JVMLangSummit
Jump to navigationJump to search
(New page: == Hotswap == Thomas Wuerthinger - Sun ; Project: ; Blog: ; Slides: Image:file.pdf === Abstract === = Background = = Current Status = = Future = = Key Issues for Discussion ...)
 
 
(10 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
== Hotswap ==
 
== Hotswap ==
Thomas Wuerthinger - Sun
+
Thomas Wuerthinger (wuerthinger@ssw.jku.at) - Sun
  
; Project:
+
; Slides: [[Image:Wuerthinger_Hotswap.pdf]]
; Blog:
 
; Slides: [[Image:file.pdf]]
 
  
=== Abstract ===
+
== Abstract ==
 +
The current hotswapping mechanism in the HotSpot VM only allows changing the bodies of methods at runtime. We are working on an approach that allows arbitrary changes. This talk is about our experiences implementing a prototype in HotSpot that supports adding and deleting of methods and fields as well as performing changes to the class hierarchy. What are the conditions for dynamic code evolution to have a clear semantics and what kind of changes should be forbidden? What are meaningful applications of dynamic code evolution for Java and their requirements? The talk will conclude with ideas for future work to make dynamic code evolution stable and performant.
  
= Background =
+
== Background ==
 +
This project is part of a long-term collaboration between the HotSpot compiler group at Sun Microsystems and the Institute of System Software at the Johannes Kepler University Linz.
  
 +
For a list of publications that were results of this collaboration (topics include SSA form, linear scan register allocation, ABCE, object inlining, escape analysis, compiler graph visualization tools) see:
  
= Current Status =
+
[http://wikis.sun.com/display/HotSpotInternals/Publications+JKU JKU HotSpot Publications]
  
 +
== Current Status ==
 +
[http://wikis.sun.com/display/mlvm/HotSwap Patch + Technical Documentation]
  
= Future =
+
== Future ==
  
  
= Key Issues for Discussion =
+
== Key Issues for Discussion ==
 
''(please expand cooperatively)''
 
''(please expand cooperatively)''

Latest revision as of 13:07, 17 September 2009

Hotswap

Thomas Wuerthinger (wuerthinger@ssw.jku.at) - Sun

Slides
File:Wuerthinger Hotswap.pdf

Abstract

The current hotswapping mechanism in the HotSpot VM only allows changing the bodies of methods at runtime. We are working on an approach that allows arbitrary changes. This talk is about our experiences implementing a prototype in HotSpot that supports adding and deleting of methods and fields as well as performing changes to the class hierarchy. What are the conditions for dynamic code evolution to have a clear semantics and what kind of changes should be forbidden? What are meaningful applications of dynamic code evolution for Java and their requirements? The talk will conclude with ideas for future work to make dynamic code evolution stable and performant.

Background

This project is part of a long-term collaboration between the HotSpot compiler group at Sun Microsystems and the Institute of System Software at the Johannes Kepler University Linz.

For a list of publications that were results of this collaboration (topics include SSA form, linear scan register allocation, ABCE, object inlining, escape analysis, compiler graph visualization tools) see:

JKU HotSpot Publications

Current Status

Patch + Technical Documentation

Future

Key Issues for Discussion

(please expand cooperatively)