-
Notifications
You must be signed in to change notification settings - Fork 47
Merge new features to main for hvisor-v0.2 release #193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…for now, logic needs rewrite
|
|
||
| pub fn cpuid_to_mpidr_affinity(cpuid: u64) -> (u64, u64, u64, u64) { | ||
| let mpidr = BOARD_MPIDR_MAPPINGS[cpuid as usize]; | ||
| let aff3 = (mpidr >> 32) & 0xff; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This may be aff3 = (mpidr >> 24) ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is reasonable. All right.
src/device/irqchip/gicv3/mod.rs
Outdated
| .position(|&x| x == mpidr) | ||
| .expect("MPIDR from BOARD_MPIDR_MAPPINGS must be present in sorted list"); | ||
|
|
||
| GIC.get().unwrap().gicr_base + order * PER_GICR_SIZE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a question here. The correct way to find the gicr base of one cpu is to check if GICR_TYPER.Affinity_value is equal to the mpidr of this cpu. I searched in the internet and found that the order of the cpu's mpidr may not be the order of the cpu's gicr_base.
src/arch/loongarch64/hypercall.rs
Outdated
| use crate::hypercall::HyperCallResult; | ||
| impl<'a> HyperCall<'a> { | ||
| pub fn hv_ivc_info(&mut self, ivc_info_ipa: u64) -> HyperCallResult { | ||
| warn!("hv_ivc_info is not implemented for Risc-V"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Risc-V should be LoongArch64 ?
caodg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should indicate the current status, the main and new features, in README, and list major changes in CHANGELOG.md
Optimized the structure of GIC parameters.
…mprove logging clarity
This commit deletes the following files from the vendor/fdt/src directory
Refactor: Enhance GICR handling and remove unused FDT code
Update CHANGELOG for version 0.2 with new platform and feature…

No description provided.