drgn/MANIFEST.in

recursive-include docs *.py *.rst
recursive-include tests *.py
recursive-include scripts/vmtest *.py *.rst *.sh
Document with Sphinx drgn has pretty thorough in-program documentation, but it doesn't have a nice overview or introduction to the basic concepts. This commit adds that using Sphinx. In order to avoid documenting everything in two places, the libdrgn bindings have their docstrings generated from the API documentation. The alternative would be to use Sphinx's autodoc extension, but that's not as flexible and would also require building the extension to build the docs. The documentation for the helpers is generated using autodoc and a small custom extension. 2019-04-04 09:27:23 +01:00			`recursive-include docs .py .rst`
Rewrite drgn core in C The current mixed Python/C implementation works well, but it has a couple of important limitations: - It's too slow for some common use cases, like iterating over large data structures. - It can't be reused in utilities written in other languages. This replaces the internals with a new library written in C, libdrgn. It includes Python bindings with mostly the same public interface as before, with some important improvements: - Types are now represented by a single Type class rather than the messy polymorphism in the Python implementation. - Qualifiers are a bitmask instead of a set of strings. - Bit fields are not considered a separate type. - The lvalue/rvalue terminology is replaced with reference/value. - Structure, union, and array values are better supported. - Function objects are supported. - Program distinguishes between lookups of variables, constants, and functions. The C rewrite is about 6x as fast as the original Python when using the Python bindings, and about 8x when using the C API directly. Currently, the exposed API in C is fairly conservative. In the future, the memory reader, type index, and object index APIs will probably be exposed for more flexibility. 2019-03-22 23:27:46 +00:00			`recursive-include tests *.py`
Add virtual machine testing setup Now that we have tests for kernel-specific functionality, we should run them on various kernel versions. This adds a script for doing so using QEMU with a pre-built root filesystem image and kernels that I'm hosting on my Dropbox. The script can be run locally, but this also sets it up to be run on Travis. For now, we're testing the mainline, stable, and longterm releases from kernel.org (not including v3.16, which doesn't even boot for me). 2019-11-15 20:35:08 +00:00			`recursive-include scripts/vmtest .py .rst *.sh`