hermit-os / kernel Goto Github PK

A Rust-based, lightweight unikernel.

License: Apache License 2.0

Rust 97.57% Assembly 1.30% Python 1.13%

rust-lang cloud-computing kernel virtualization high-performance-computing unikernels osdev rust operating-systems operating-system

kernel's People

Contributors

Stargazers

Watchers

Forkers

justicezyx kaperstone gurry happy-ferret kvart2006 photoszzt rowhit progval rayleyva tisma l1212s aicaramba duzhanyuan n-eiling mhdbs ssrg-vt realrichardparker isgasho tlambertz mincheolsung xiaming9880 jschwe jbreitbart alethes mustermeiszer stlankes mkroening binary-rusty-hermit cs360v8 alessio-proietti josephlr quangio fitcha2 chenhengqi simonschoening jts22 dalalsunil1986 striezel-stash duanyu-yu whb07 ant4g0nist phial3 teymour-aldridge pjungkamp turrisxyz playxe shism2 jcastme gaojiaqi7 q741242673 joboet badersz mohamedtaoufik mnj98 cyberflamego zfg88287508 michaelrichards99 cs360v-s23 ynchen2829 richiewahidin joannejchen sarvex iq-scm gmh5225 cathaysia qscuio sarahspberrypi cagatay-y placrosse lishaowen0426 shabbirhasan1 sfbdragon 1337kiwi luojia65

kernel's Issues

CI failed because it used an old version of our loader

At least PR #54 failed because the CI used an old version of our loader. @jschwe Do you have an idea, why this happens?

Move uhyve constants to separate crate

https://github.com/hermitcore/libhermit-rs/blob/fe69c31ac45342b13c65c19dc738a494353e9d90/src/syscalls/interfaces/uhyve.rs#L20

Copy/Pasting the constants is error prone. It might be more elegant to move out the src/consts.rs to a separate (no_std) crate uhyve-api and depend on it from uhyve and from libhermit.

On the other hand, I have to admit that this is just a very minor problem...

Scheduler does not wake sleeping threads when multiple cores are available

When using multiple CPU cores, the scheduler does not wake sleeping threads once their sleep duration is over. I guess this happens because of the core-local scheduling, where the main core does not check for threads to be woken on other cores. But I have not verified this.

Simple reproducer:

#[cfg(target_os = "hermit")]
extern crate hermit_sys;

use std::thread;
use std::time;

fn main() {
    let mut children = vec![];

    let threadnum = 5;
    for i in 0..threadnum {
        println!("SPAWNING THREAD {}", i);
        children.push(thread::spawn(move || {
            println!("this is thread number {}", i);
            thread::sleep(time::Duration::from_millis(2000));
            println!("---------------THREAD DONE!---------- {}", i);
        }));
    }
    println!("SPAWNED THREADS");

    for child in children {
        let _ = child.join();
    }
}

My test project includes a cargo project, makefile and the rusty-loader: rusty-test-sleep.tar.gz.
The binary is build and started with make run. This also sets the correct QEMU options to reproduce the bug.

Build failed

OS: Ubuntu 18.04.3 LTS

I install rust nightly and followed these instructions

git clone https://github.com/hermitcore/rusty-hermit.git
cd rusty-hermit
git submodule init
git submodule update
cargo build -Z build-std=std,core,alloc,panic_abort --target x86_64-unknown-hermit

and the build failed with the message:

[hikari@atlantis rusty-hermit]$ cargo build -Z build-std=std,core,alloc,panic_abort --target x86_64-unknown-hermit
warning: profiles for the non root package will be ignored, specify profiles at the workspace root:
package:   /home/hlab/hikari/rusty-hermit/demo/Cargo.toml
workspace: /home/hlab/hikari/rusty-hermit/Cargo.toml
   Compiling rustc-std-workspace-core v1.99.0 (/home/hlab/hikari/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/tools/rustc-std-workspace-core)
   Compiling unwind v0.0.0 (/home/hlab/hikari/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/libunwind)
   Compiling backtrace-sys v0.1.32
   Compiling hermit-sys v0.1.6 (/home/hlab/hikari/rusty-hermit/hermit-sys)
error: failed to run custom build command for `hermit-sys v0.1.6 (/home/hlab/hikari/rusty-hermit/hermit-sys)`

Caused by:
  process didn't exit successfully: `/home/hlab/hikari/rusty-hermit/target/debug/build/hermit-sys-e186b5ca70364884/build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'Unable to build kernel: Os { code: 2, kind: NotFound, message: "No such file or directory" }', hermit-sys/build.rs:31:23
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

warning: build failed, waiting for other jobs to finish...
error: build failed

Did I miss anything?

`RxQueues`: Panicking does not work properly in debug

Panicking in RxQueues::get_next does not work properly in debug and instead causes a page fault:

[0][ERROR] Page Fault (#PF) Exception: ExceptionStackFrame {
    instruction_pointer: 0x500,
    code_segment: 0x8,
    cpu_flags: 0x1206,
    stack_pointer: 0x3a953790,
    stack_segment: 0x10,
}
[0][ERROR] virtual_address = 0x500, page fault error = The fault was caused by a page-level protection violation.
The access causing the fault was a read.
The access causing the fault originated when the processor was executing in supervisor mode.
The fault was not caused by reserved bit violation.
The fault was caused by an instruction fetch.
[0][ERROR] fs = 0x1, gs = 0x1

request : RISCV64 support

any planning for supporting RISCV64 arch ? RISCV64 multicore and manycore may become potential for multi-kernel feature

support of bootimage

Build a bootable image with bootimage. Bootimage use a boot loader, which is better maintained in comparison to our own.

Delete Stale branches

There are two branches which are outdated: devel and loader. I think they can be removed.

Add syscalls to Rust libstd

Hi, there is no "issues section" on the hermitcore:rust repo, so I post here.
I am now trying to add some system calls on RustyHermit.
I created my_syscalls.rs on rust/src/libstd/sys/hermit/ and tried to import it from the libhermit-rs/tests/src/tests/mod.rs.

As I observed, I can't directly use it because the libstd/sys is private.
So do I need to create interfaces for my system calls and overwrite them on rust/src/libstd/sys/hermit/my_syscalls.rs?

Rusty-hermit may experience Page Fault when panicking

For detailed instructions on how to reproduce and a log output please view hermit-os/uhyve#7 (comment)

When a panic occurs in rusty-hermit, e.g. due to an expect/unwrap it may happen that a Page Fault occurs. This hints that the panic handling of the kernel has some kind of bug.

hermit-os/uhyve#6 also contains related information

Missing FSGS leeds to endless spinloop without any error message

https://github.com/hermitcore/libhermit-rs/blob/d6539f202a1938c143fa7b975071f6dbaed0092a/src/arch/x86_64/kernel/processor.rs#L785-L792

Missing fsgs support leads to an endless spin-loop without any error message. I'm not quite sure why no error message is printed, maybe the serial interface is not initialized at that point? (it's still very early).
If possible it would be great to enable the serial interface before this point, so that an error message can get sent out.
Additionally I would propose to change the loop so that it loops only for a couple of seconds and terminates the kernel afterwards e.g. by panicking.

SMP issue

I don't think we have an issue for this yet, so I'm opening one now to track this issue.
Currently there are issues running rusty-demo with multiple cores, where sometimes it takes a long time to complete the demo.

Jobs failed due to SMP timeout (May 20 - June 06):

Possibly related Job logs:

thread 'main' panicked at 'Trying to get the scheduler for core 1, but it isn't available', src/scheduler/mod.rs:530:9 for hermit-os/hermit-rs@64ec710

add microvm support

Citation:

microvm is a machine type inspired by Firecracker and constructed after its machine model.
It's a minimalist machine type without PCI nor ACPI support, designed for short-lived guests. microvm also establishes a baseline for benchmarking and optimizing both QEMU and guest operating systems, since it is optimized for both boot time and footprint.

Conseqeuntly, it is a interesting platform for RustyHermit and should be supported

Retry naked functions

Naked functions have come a long way since #95.

There is rust-lang/rfcs#2972 and rust-lang/rust#79653 which help against misusing the feature. We have adapted it in eduOS successfully, making it possible to use const and sym operands in asm! blocks instead of having to resort to global symbols. We could also eliminate most, if not all, hard coded constants from assembly, making the code much easier to understand.

What do you think, @stlankes?

`ExceptionStackFrame` in interrupts contains gibberish

Since LLVM 12 (rust-lang/rust#84230) ExceptionStackFrame has to be taken by value. See rust-lang/rust#40180 (comment).

Current output of ud2:

[0][ERROR] Invalid Opcode (#UD) Exception: ExceptionStackFrame {
    instruction_pointer: 0xc35b30c483480b0f,
    code_segment: 0xee9d058af2894850,
    cpu_flags: 0x3d8d48f76348ffff,
    stack_pointer: 0x7e8ffffffcc,
    stack_segment: 0xccccccccccc35900,
}

Expected:

[0][ERROR] Invalid Opcode (#UD) Exception: ExceptionStackFrame {
    instruction_pointer: 0x501738,
    code_segment: 0x8,
    cpu_flags: 0x11206,
    stack_pointer: 0x373be30,
    stack_segment: 0x10,
}

README doesn't document how to build your own libhermit-rs

The section titled Building RusytHermit only shows how to build AGAINST the published version of Rusty-Hermit - not how to build libhermit yourself.

Unwinding support

According to the discussion in hermit-os/uhyve#30 (comment) this might still be impossible or very difficult at least.

It would make it much easier to host multiple "applications" in the same unikernel without a panic crashing all of it.

Slow thread creation

Benchmarks show that the time for a thread creation is too high. As workaround we use currently in our demo a thread pool.

Intra-Unikernel Isolation with Intel Memory Protection Keys

We should backport our prototype for intra-kernel isolation.

virtio assumes contiguous memory, but their is no guarantee

https://github.com/hermitcore/libhermit-rs/blob/b52be1ea6f4a815dc7d32bc054c8cfe70dba0a58/src/arch/x86_64/kernel/virtio.rs#L103-L116

@tlambertz the code assumes contiguous memory. But there is no guarantee. I think that you have to use https://github.com/hermitcore/libhermit-rs/blob/master/src/mm/mod.rs#L239.

error: output of --print=file-names has changed in the compiler, cannot parse

I tried to rebuild rust by running
$./x.py install

However, I got an error,

error: output of --print=file-names has changed in the compiler, cannot parse
command was: /home/mincheol/rust/build/bootstrap/debug/rustc - --crate-name ___ --print=file-names -Zexternal-macro-backtrace '-Clink-args=-Wl,-rpath,$ORIGIN/../lib' -Wrust_2018_idioms -Wunused_lifetimes -Dwarnings -Zsave-analysis -Cprefer-dynamic --target x86_64-unknown-linux-gnu --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=cfg

--- stdout
Here????

___
lib___.rlib
lib___.so
lib___.so
lib___.a
lib___.so
/home/mincheol/rust/build/x86_64-unknown-linux-gnu/stage1
debug_assertions
proc_macro
target_arch="x86_64"
target_endian="little"
target_env="gnu"
target_family="unix"
target_feature="fxsr"
target_feature="mmx"
target_feature="sse"
target_feature="sse2"
target_has_atomic="16"
target_has_atomic="32"
target_has_atomic="64"
target_has_atomic="8"
target_has_atomic="cas"
target_has_atomic="ptr"
target_os="linux"
target_pointer_width="64"
target_thread_local
target_vendor="unknown"
unix

command did not execute successfully: "/home/mincheol/rust/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "build" "-Zconfig-profile" "--target" "x86_64-unknown-linux-gnu" "-Zbinary-dep-depinfo" "-j" "32" "--release" "--features" "panic-unwind backtrace compiler-builtins-c" "--manifest-path" "/home/mincheol/rust/src/libtest/Cargo.toml" "--message-format" "json-render-diagnostics"
expected success, got: exit code: 101
failed to run: /home/mincheol/rust/build/bootstrap/debug/bootstrap install
Build completed unsuccessfully in 0:06:00

Intructions for local build

Hi!

I am trying to locally build RustyHermit.
Are there instructions for that?
I tried "make" but failed to build.

mincheol@mir3:~/libhermit-rs$ make
Build libhermit
Finished dev [optimized + debuginfo] target(s) in 0.02s
make arch=x86_64 release=0 -C tests
make[1]: Entering directory '/home/mincheol/libhermit-rs/tests'
Compiling nodrop v0.1.13
Compiling lazy_static v1.4.0
Compiling cfg-if v0.1.9
Compiling scopeguard v1.0.0
Compiling fnv v1.0.6
Compiling either v1.5.2
Compiling itoa v0.4.4
Compiling libc v0.2.62
Compiling byteorder v1.3.2
Compiling memoffset v0.5.1
error[E0463]: can't find crate for core
|
= note: the x86_64-unknown-hermit target may not be installed

error[E0463]: can't find crate for core
|
= note: the x86_64-unknown-hermit target may not be installed