Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix: clippy #733

Merged
merged 2 commits into from
Jul 26, 2024
Merged

fix: clippy #733

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4070ec7
fix(uhyve-interface): clippy::doc_lazy_continuation
mkroening Jul 26, 2024
dbb287f
fix(dead_code): remove unused shared_queue module
mkroening Jul 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions src/lib.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,8 +23,6 @@ mod hypercall;
pub mod mem;
pub mod paging;
pub mod params;
#[cfg(target_os = "linux")]
pub mod shared_queue;
mod vcpu;
pub mod virtio;
pub mod virtqueue;
Expand Down
27 changes: 0 additions & 27 deletions src/shared_queue.rs
View file
Open in desktop

This file was deleted.

4 changes: 2 additions & 2 deletions uhyve-interface/src/lib.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,8 @@
//! The Uhyve hypercall interface works as follows:
//!
//! - On `x86_64` you use an out port instruction. The address of the `out`-port corresponds to the
//! hypercall you want to use. You can obtain it from the [`IoPorts`] enum. The data send to
//! that port is the physical memory address (of the VM) of the parameters of that hypercall.
//! hypercall you want to use. You can obtain it from the [`IoPorts`] enum. The data send to
//! that port is the physical memory address (of the VM) of the parameters of that hypercall.
//! - On `aarch64` you write to the respective [`HypercallAddress`]. The 64-bit value written to that location is the guest's physical memory address of the hypercall's parameter.

#![cfg_attr(not(feature = "std"), no_std)]
Expand Down