mirror of
https://github.com/facebookexperimental/reverie.git
synced 2025-01-23 05:06:23 +00:00
Update readme with aarch64 support
Reviewed By: wkhughes Differential Revision: D40956267 fbshipit-source-id: 10655f6898e026506778c0a55b8daee619029908
This commit is contained in:
parent
ffd9f11127
commit
ffc3020fe8
1 changed files with 15 additions and 4 deletions
19
README.md
19
README.md
|
@ -1,9 +1,9 @@
|
||||||
# Reverie
|
# Reverie
|
||||||
|
|
||||||
Reverie is a user space system-call interception framework for x86-64 Linux.
|
Reverie is a user space system-call interception framework for Linux. It can
|
||||||
It can be used to intercept, modify, or elide a syscall before the kernel
|
be used to intercept, modify, or elide a syscall before the kernel executes
|
||||||
executes it. In essence, Reverie sits at the boundary between user space and
|
it. In essence, Reverie sits at the boundary between user space and kernel
|
||||||
kernel space.
|
space.
|
||||||
|
|
||||||
Some potential use cases include:
|
Some potential use cases include:
|
||||||
|
|
||||||
|
@ -95,6 +95,17 @@ running in the same address space. Thus, all shared state is communicated via
|
||||||
RPC messages. (There is, however, currently only a single ptrace-based backend
|
RPC messages. (There is, however, currently only a single ptrace-based backend
|
||||||
where all tracer code is in the same address space.)
|
where all tracer code is in the same address space.)
|
||||||
|
|
||||||
|
## Platform and Architecture Support
|
||||||
|
|
||||||
|
Reverie currently only supports the following platforms and architectures:
|
||||||
|
|
||||||
|
| Platform | Architecture | Notes |
|
||||||
|
|:--------:|:------------:|:------------------------------------------|
|
||||||
|
| Linux | x86-64 | Full support |
|
||||||
|
| Linux | aarch64 | Missing timers & cpuid/rdtsc interception |
|
||||||
|
|
||||||
|
Other platforms and architectures are currently unplanned.
|
||||||
|
|
||||||
## Future Plans
|
## Future Plans
|
||||||
|
|
||||||
* Add a more performant backend. The rough goal is to have handlers executing in
|
* Add a more performant backend. The rough goal is to have handlers executing in
|
||||||
|
|
Loading…
Reference in a new issue