Implement should_panic for ktest and clear the codebase

This commit is contained in:
Zhang Junyang
2023-11-05 00:14:28 +08:00
committed by Tate, Hongliang Tian
parent bb0560530f
commit 45a6b2f46c
14 changed files with 242 additions and 170 deletions

View File

@ -1,23 +1,17 @@
#![no_std]
#![no_main]
// The `no_mangle`` attribute for the `jinux_main` entrypoint requires the removal of safety check.
// The `export_name` attribute for the `jinux_main` entrypoint requires the removal of safety check.
// Please be aware that the kernel is not allowed to introduce any other unsafe operations.
// #![forbid(unsafe_code)]
extern crate jinux_frame;
use core::panic::PanicInfo;
use jinux_frame::println;
#[no_mangle]
pub fn jinux_main() -> ! {
#[export_name = "jinux_main"]
pub fn main() -> ! {
jinux_frame::init();
println!("[kernel] finish init jinux_frame");
component::init_all(component::parse_metadata!()).unwrap();
jinux_std::init();
jinux_std::run_first_process();
}
#[panic_handler]
fn panic(info: &PanicInfo) -> ! {
jinux_frame::panic_handler(info);
}