| Age | Commit message (Collapse) | Author | Lines |
|
|
|
|
|
We're trying to get closer to doing correct move semantics for channel
operations. This involves a lot of cleanup (such as removing the
unused sched parameter from rust_vec constructor) and making
circular_buffer kernel_owned.
Added tagging for memory allocations. This means we give a string tag
to everything we allocate. If we leak something and TRACK_ALLOCATIONS
is enabled, then it's much easier now to tell exactly what is leaking.
|
|
|
|
|
|
|
|
|
|
to re-xfail a few tests brson recently un-xfailed.
|
|
See https://github.com/graydon/rust/wiki/Logging-vision
The runtime logging categories are now treated in the same way as
modules in compiled code. Each domain now has a log_lvl that can be
used to restrict the logging from that domain (will be used to allow
logging to be restricted to a single domain).
Features dropped (can be brought back to life if there is interest):
- Logger indentation
- Multiple categories per log statement
- I possibly broke some of the color code -- it confuses me
|
|
domains can only talk to other domains via handles, and with the help of the rust_kernel.
|
|
and fixed race caused by calling rust_srv::malloc() from multiple threads when sending messages.
|
|
zero. This should only happen in the Rust code and not in the drop glue, or on the unwind path. This change allows the task owning the channel to block on a flush and delete its own channel. This change also cleans up some code around rust_port and rust_chan.
|
|
system use it (and proxies) instead of existing token scheme.
|
|
notify_message, make them use proxies, cache task proxies in dom.
|