Daniel Xu
Daniel Xu
Before, we were pinning dependencies down to the patch version. This prevents us from picking up bug fixes. It also (I think) caused failures like this: $ cargo install vmtest...
Should be a better fit of vmtest use case (tests). Claims to boot faster and consume less resources. See https://www.qemu.org/docs/master/system/i386/microvm.html I believe virtme-ng also supports this
`run_in_vm()` is getting kinda hairy. It would be nice to pull it into a cleaner abstraction. Maybe with some kinda [OpenOptions](https://doc.rust-lang.org/std/fs/struct.OpenOptions.html) like builder to specify options. A proper object would...
vmtest is more or less a wrapper around qemu stuff. So it's almost completely I/O bound, making it a good candidate for async. Async is particularly appealing cuz we have...
Maybe something like: ``` def foo(arg1) { print(arg1) } ``` Questions: * explicit return type annotation? * do we need a new type for `None` if function doesn't return anything?
List of features in progress and upcoming: - [x] Support `BTRFS_EXTENT_ITEM_KEY` item types * #2 - [x] Support arbitrary type interpretation * #4 - [ ] Support arbitrary type interpretation...
This is needed for the write API and arbitrary interpretation
Add a write API such that if `btrd` is given an unmounted FS image, btrd can write arbitrary bytes to anywhere in the image. Code example: ``` (btrd) filesystem /home/dev/dxu/unmounted_image...
### Is your feature request related to a problem? Please describe. Consider: ``` $ sudo ./build/src/bpftrace -e 'kprobe:zswap_swapon { @x++ }' ``` It generates the following code: ``` $ sudo...
Take, for example, this: $ sudo ./build/src/bpftrace -e 'BEGIN { print(*curtask); exit() }' error: :0:0: in function BEGIN i64 (ptr): A call to built-in function 'memset' is not supported. The...