You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove i686-guest, nanvix-unstable and guest-counter features (#1525)
* Remove i686-guest, nanvix-unstable and guest-counter features
Removes the experimental 32-bit i686 guest support along with the
nanvix-unstable and guest-counter cargo features that depended on or
accompanied it. This deletes the i686 arch modules, the PEB file-mapping
plumbing (labels, preallocated FileMappingInfo array), the GuestCounter
API, and the associated cfg gating, tests, Justfile recipes, CI matrix
entries and docs.
As part of the cleanup, the ReadableSharedMemory trait machinery in
mem::layout is now gated on a precise 'readable_shared_mem' cfg alias
(gdb debug path or shared-snapshot mem_profile path) instead of a blanket
Signed-off-by: Simon Davies <simongdavies@users.noreply.github.com>
#[allow(unused)], so it is compiled out entirely when unused.
* Gate crashdump helpers on the crashdump cfg-alias
Four crashdump-only items in mem::mgr (the BasicMapping/MappingKind
import, mapping_kind_to_flags, try_coalesce_region and
get_guest_memory_regions) were gated on the raw `crashdump` feature
rather than the `crashdump` cfg-alias from build.rs
(all(feature = "crashdump", target_arch = "x86_64")). They reference
CrashDumpRegion/MemoryRegionFlags/MemoryRegionType, which are imported
under #[cfg(crashdump)], so enabling the feature on a non-x86_64 target
would compile the code without the types and fail to build. Switch them
to #[cfg(crashdump)] for consistency with the rest of the crashdump
codepath.
Addresses Copilot review feedback on #1525.
Signed-off-by: Simon Davies <simongdavies@users.noreply.github.com>
* Remove unused multi-root snapshot plumbing
Drop unused multi-root page-table snapshot machinery introduced by the
old aliasing work:
- Remove PtRootFinder/set_pt_root_finder and root_pt_gpas plumbing
from MultiUseSandbox and SandboxMemoryManager snapshot flow.
- Simplify Snapshot::new to walk and rebuild from a single root (CR3)
using virt_to_phys + map only.
- Remove unused multi-space API/types from hyperlight_common::vmem:
SpaceId, SpaceReferenceMapping, SpaceAwareMapping,
walk_va_spaces, and space_aware_map, plus arch stubs.
This keeps only the single-root walker path now used by the host and
eliminates dead code and extra complexity.
Signed-off-by: Simon Davies <simongdavies@users.noreply.github.com>
* Update CHANGLOG
Signed-off-by: Simon Davies <simongdavies@users.noreply.github.com>
* Further review changes
Signed-off-by: Simon Davies <simongdavies@users.noreply.github.com>
* Address review feedback
Signed-off-by: Simon Davies <simongdavies@users.noreply.github.com>
---------
Signed-off-by: Simon Davies <simongdavies@users.noreply.github.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,12 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
4
4
5
5
## [Prerelease] - Unreleased
6
6
7
+
### Changed
8
+
***Breaking:**`MultiUseSandbox::map_file_cow` and `UninitializedSandbox::map_file_cow` no longer take a label argument. The APIs now accept only `(file_path, guest_base)`.
9
+
10
+
### Removed
11
+
* Removed the experimental `i686-guest`, `nanvix-unstable`, and `guest-counter` feature flags, along with 32-bit (i686) guest support and its page-table/snapshot code paths. Hyperlight guests are now 64-bit only (x86_64 and aarch64).
0 commit comments