optimization：Do not use raw pointers

[flying-122]

pub(crate) struct Vcpu {
pub(crate) mmu: UniqueRef,
pub(crate) va_run: u64,

• pub(crate) run: *mut RkvmRun, //here

It is better not to use raw pointers

[zhouhaoan]

It seems to be a Ref<> pointer in commit 89ef05fa(HEAD^), but modified to a raw pointer in the latest commit 5dca9316(HEAD). Both of them could be successfully compiled. Is it a mistake when commiting files?

[flying-122]

It seems to be a Ref<> pointer in commit 89ef05fa(HEAD^), but modified to a raw pointer in the latest commit 5dca9316(HEAD). Both of them could be successfully compiled. Is it a mistake when commiting files?

no. Ref<> cannot be converted to mutable

[zhouhaoan]

It seems to be a Ref<> pointer in commit 89ef05fa(HEAD^), but modified to a raw pointer in the latest commit 5dca9316(HEAD). Both of them could be successfully compiled. Is it a mistake when commiting files?

no. Ref<> cannot be converted to mutable

This is the related crates used in rust/kernel/sync/arc.rs, where the rust-kernel Ref is defined :

use core::{
    alloc::Layout,
    convert::{AsRef, TryFrom},
    marker::{PhantomData, Unsize},
    mem::{ManuallyDrop, MaybeUninit},
    ops::{Deref, DerefMut},
    pin::Pin,
    ptr::{self, NonNull},
};

Since the core::ops::DerefMut is not implemented to Ref, can we implement the DerefMut trait to rust-kernel Ref?

I think it can just write like this:

 impl<T: ?Sized> DerefMut for Ref<T> {
    type Target = T;

    fn deref_mut(&self) -> &mut Self::Target {
        
        unsafe { &mut self.ptr.as_mut().data }
    }
}