Skip to content

fix: avoid spatial initialization during memory queries #50

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

Merged
maverick-woo merged 1 commit into from
Nov 1, 2026
Merged

fix: avoid spatial initialization during memory queries #50

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
19 changes: 14 additions & 5 deletions crates/hook/src/hook.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,4 @@
#![allow(non_snake_case)]
use crate::npu_limiter;
use limiter::externed_api::{RT_ERROR_MEMORY_ALLOCATION, RT_ERROR_NONE};
use limiter::worker::AllocationKind;

Expand Down Expand Up @@ -245,10 +244,20 @@ pub unsafe extern "C" fn rtMemGetInfoEx(
free: *mut usize,
total: *mut usize,
) -> u64 {
let client = npu_limiter();
if client.is_hbm_limited() {
unsafe { client.get_hbm_info(free, total) };
return 0;
if limiter::config::vnpu_configuration_requested() {
limiter::config::validate_requested_limits()
.unwrap_or_else(|error| crate::spatial::fatal(&error));
let _ = crate::spatial::enabled(); // Preserve the spatial fork guard.
let mut logical = -1;
if unsafe { limiter::externed_api::rtGetDevice(&mut logical) } == 0 && logical >= 0 {
// GE queries memory before its compute device object exists. Resolve
// only the quota here; device/context selection still applies budgets.
let client = crate::npu_limiter_for_device(logical);
if client.is_hbm_limited() {
unsafe { client.get_hbm_info(free, total) };
return 0;
}
}
}
passthrough!(
"rtMemGetInfoEx",
Expand Down
Loading