feat: axerrno compatibility

[AsakuraMizu]

This feature has been discussed in arceos-org/allocator#6.

[Copilot]

Pull Request Overview

This PR adds optional axerrno compatibility to the page_table_multiarch crate by implementing a From<PagingError> trait for converting paging errors into axerrno error types. The PR also decouples version management by assigning specific versions to each crate instead of using a workspace-level version.

• Added optional axerrno feature with error type conversion from PagingError to AxError
• Bumped page_table_multiarch version to 0.5.7 (separated from workspace version)
• Set page_table_entry version to 0.5.6 (independent versioning)

Reviewed Changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
page_table_multiarch/src/lib.rs	Implements From<PagingError> conversion trait to map paging errors to axerrno error types when the axerrno feature is enabled
page_table_multiarch/Cargo.toml	Adds optional axerrno dependency (v0.1), creates axerrno feature flag, and sets independent version 0.5.7
page_table_entry/Cargo.toml	Sets independent version 0.5.6, no longer using workspace version
Cargo.toml	Removes workspace-level version field as packages now manage their own versions
Cargo.lock	Updates lock file with axerrno dependencies (0.1.2 and its transitive dependency 0.2.0) and related crates

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[equation314]

It's better to keep the versions of page_table_entry and page_table_multiarch consistent for easier management.

[AsakuraMizu]

It's better to keep the versions of page_table_entry and page_table_multiarch consistent for easier management.

Hmm, what I'm considering is avoiding releasing an unchanged version to another crate when only one crate is being updated. Another point is that if there are semver-breaking changes to page_table_multiarch in the future (which will happen soon), I don't want to break the compatibility of page_table_entry as well.

[AsakuraMizu]

The CI is failing because quote crate is using cfg(doc) to simplify documentation: https://github.com/dtolnay/quote/blob/b550c7ee34b90c54a05e2272fcec1d5346a38ca9/src/lib.rs#L627-L635. This usage is actually correct, but we are using --cfg doc to trick the compiler in documentation and testing. I will create a separate PR to remove --cfg doc first.

[Azure-stars]

It's better to keep the versions of page_table_entry and page_table_multiarch consistent for easier management.

Hmm, what I'm considering is avoiding releasing an unchanged version to another crate when only one crate is being updated. Another point is that if there are semver-breaking changes to page_table_multiarch in the future (which will happen soon), I don't want to break the compatibility of page_table_entry as well.

LGTM. I think there are no strong unified release requirements for our packages in the same workspace. So to seperate them is OK for me.

[AsakuraMizu]

Let's postpone the changes for version bumping. Keep this PR focusing on adding axerrno compatibility only.