Difference between revisions of "Technologies"
(Fixed text) |
|||
Line 1: | Line 1: | ||
− | This page contains a list of tools that were developed | + | This page contains a list of technologies and tools that were developed while we did CRIU and that make sense outside of it. These tools are still maintained within the CRIU itself, but eventually they can be split out into a standalone project and CRIU will be fixed to use those as libraries/sub-tools. |
− | These tools are | ||
− | == [https://github.com/xemul/compel | + | == Parasite code injection == |
− | + | This thing was split into a separate project called [https://github.com/xemul/compel compel]. | |
+ | Compel is an utility to execute code in foreign process address space. It is based on the same technology we use in CRIU to obtain some process-private data on dump. | ||
+ | We don't currently maintain compel and it's quite out-dated, but still functional. | ||
== [https://github.com/xemul/criu/blob/master/pycriu/images/pb2dict.py pb2dict.py] == | == [https://github.com/xemul/criu/blob/master/pycriu/images/pb2dict.py pb2dict.py] == |
Revision as of 09:32, 10 February 2015
This page contains a list of technologies and tools that were developed while we did CRIU and that make sense outside of it. These tools are still maintained within the CRIU itself, but eventually they can be split out into a standalone project and CRIU will be fixed to use those as libraries/sub-tools.
Parasite code injection
This thing was split into a separate project called compel. Compel is an utility to execute code in foreign process address space. It is based on the same technology we use in CRIU to obtain some process-private data on dump. We don't currently maintain compel and it's quite out-dated, but still functional.
pb2dict.py
A Python module to convert google protocol buffers to json and back.
Unlike other projects to convert pb to python dict or json, our pb2dict does treat optional fields with empty repeated inside properly. It includes special support for custom field options to mark those needed to be treated in a special way. For example, you could include our opts.proto in your proto-file and use criu.* options to mark your fields, i.e.:
required uint64 blk_sigset = 5[(criu).hex = true];
See more examples in our protobuf/*.proto files.
It is also worth noting, that we have a unique number for all kinds of custom protobuf options(see Images#Notes_about_protobuf), so you don't have to worry that it might collide with others.