[Verifier][Chore] Extract Meter trait from Verifier #16903
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Ignored Deployments
|
amnn
force-pushed
the
amnn/verify-fix-mod
branch
from
05e43ea
to
a562268
Compare
This was referenced Mar 28, 2024
tnowacki
approved these changes
Apr 3, 2024
| units_per_item: u128, | ||
| items: usize, | ||
| ) -> PartialVMResult<()> { | ||
| if items == 0 { |
There was a problem hiding this comment.
I find these sort of micro-optimizations peculiar but fine by me
There was a problem hiding this comment.
This is just a straight copy of the existing Meter trait, I wouldn't be opposed to revisiting it, but didn't want to do that in this PR to not muddy the history too much.
## Description Pulling the `Meter` trait definition out of each version of the verifier into a common place. This is so that this trait can be used as part of the execution layer interface. The overall motivation is so that we can supply a `Meter` implementation that captures more data when run from the CLI, to improve the quality of output from `sui client verify-bytecode-meter`. ## Test Plan ``` sui$ cargo build --bin sui sui$ cargo simtest sui$ env SUI_SKIP_SIMTESTS=1 cargo nextest run ```
amnn
added a commit
that referenced
this pull request
Apr 4, 2024
## Description Supersede `Verifier::meter_compiled_modules_with_overrides` by: - Allowing `meter_compiled_modules` and `meter_compiled_bytes` to accept a custom meter. - Extracting the generation of `VerifierConfig` out to the `sui-protocol-config` crate. - Splitting up `VerifierConfig` into itself and `MeterConfig`. - Adding a `Verifier::meter` function for creating the meter that is used during signing. - Removed the meter as a field of each `Verifier`. This means that we can now pass a different meter type when we don't want to enforce metering, and no longer need to modify the config in-place to achieve the same result. To make this work, I needed to enable the use of a `&mut dyn Meter` trait object to instantiate what was previously a `&mut impl Meter` parameter everywhere. To do this, I created a forwarding trait implementation of `Meter` for `&mut dyn Meter` and added an extra relaxation of `+ ?Sized` to all the `&mut impl Meter` parameters to allow the trait object to instantiate them. This is in preparation for passing a custom meter into this new parameter when instantiated by the CLI to capture all information about scopes during metering. Today we don't do that which means: - We only report back information about the last module and function we verified. - We can incorrectly report that everything is fine, (package would pass verification) even if there was some previous module or function that exceeded the stated limits. ## Test Plan ``` sui$ cargo build --bin sui sui$ cargo simtest sui$ env SUI_SKIP_SIMTESTS=1 cargo nextest run external-crates$ ./tests.sh deepbook$ cargo run --bin sui -p sui -- client verify-bytecode-meter ``` ## Stack - #16899 - #16900 - #16903
amnn
added a commit
that referenced
this pull request
Apr 4, 2024
## Description The motivation for this change is to properly track the modules being visited in the `Meter`, so that in our command line tool, we can provide an output that correctly tracks how many meter ticks were used to verify each function and module. Prior to this change, the metered verifier pretended like there was only "one module" that all the functions being verified were in. This change introduces the level of packages that ticks from modules are transferred to. We also add an explicit protocol config parameter to set a max tick limit per package (whose value is the same as the function and module level limits currently). This was not strictly necessary but was done to avoid confusion (caused by treating the module level limit as the package level limit). This should be a behaviour preserving change, but in some cases we may do more work verifying transactions because of how the ticks for each module are now gathered in isolation before being transferred to the package scope. In any case, a behaviour change would be okay, because metering (and related errors) is only used during signing, and not execution. ## Test Plan ``` sui$ cargo simtest deepbook$ cargo run --bin sui -p sui -- client verify-bytecode-meter ``` ## Stack - #16903 - #16941
amnn
added a commit
that referenced
this pull request
Apr 8, 2024
…6963) ## Description Use a custom meter to track every function and module that is verified, and display all of them. ## Test Plan ``` deepbook$ cargo run --bin sui -p sui \ -- client verify-bytecode-meter \ --module build/DeepBook/bytecode_modules/math.mv ╭──────────────────────────────────────╮ │ Package will pass metering check! │ ├──────────────────────────────────────┤ │ Limits │ ├─────────────────────────┬────────────┤ │ packages │ 16,000,000 │ │ modules │ 16,000,000 │ │ functions │ 16,000,000 │ ├─────────────────────────┴────────────┤ │ Ticks Used │ ├─────────────────────────┬────────────┤ │ <unknown> │ 41,915 │ │ math │ 41,915 │ │ unsafe_mul │ 1,225 │ │ unsafe_mul_round │ 5,675 │ │ mul │ 2,410 │ │ mul_round │ 2,905 │ │ unsafe_div │ 1,225 │ │ unsafe_div_round │ 6,085 │ │ div_round │ 2,905 │ │ count_leading_zeros │ 19,485 │ ├─────────────────────────┴────────────┤ │ Package will pass metering check! │ ╰──────────────────────────────────────╯ ``` ## Stack - #16903 - #16941 - #16945 --- If your changes are not user-facing and do not break anything, you can skip the following section. Otherwise, please briefly describe what has changed under the Release Notes section. ### Type of Change (Check all that apply) - [ ] protocol change - [x] user-visible impact - [ ] breaking change for a client SDKs - [ ] breaking change for FNs (FN binary must upgrade) - [ ] breaking change for validators or node operators (must upgrade binaries) - [ ] breaking change for on-chain data layout - [ ] necessitate either a data wipe or data migration ### Release notes `sui client verify-bytecode-meter` prints a breakdown of verifier cost by module and function in a package.
amnn
added a commit
that referenced
this pull request
Apr 8, 2024
When passing modules to `sui client verify-bytecode-meter`, support passing multiple `--modules` to be treated as a single package. ## Test Plan ``` deepbook$ cargo run --bin sui -p sui \ -- client verify-bytecode-meter \ --module build/DeepBook/bytecode_modules/math.mv \ --module build/DeepBook/bytecode_modules/clob.mv Running bytecode verifier for 2 modules ╭──────────────────────────────────────────────────╮ │ Package will pass metering check! │ ├──────────────────────────────────────────────────┤ │ Limits │ ├─────────────────────────────────────┬────────────┤ │ packages │ 16,000,000 │ │ modules │ 16,000,000 │ │ functions │ 16,000,000 │ ├─────────────────────────────────────┴────────────┤ │ Ticks Used │ ├─────────────────────────────────────┬────────────┤ │ <unknown> │ 1,859,140 │ │ math │ 41,915 │ │ unsafe_mul │ 1,225 │ │ unsafe_mul_round │ 5,675 │ │ mul │ 2,410 │ │ mul_round │ 2,905 │ │ unsafe_div │ 1,225 │ │ unsafe_div_round │ 6,085 │ │ div_round │ 2,905 │ │ count_leading_zeros │ 19,485 │ │ clob │ 1,817,225 │ │ destroy_empty_level │ 1,205 │ │ create_account │ 360 │ │ create_pool │ 480 │ │ deposit_base │ 5,490 │ │ deposit_quote │ 5,490 │ │ withdraw_base │ 6,500 │ │ withdraw_quote │ 6,500 │ │ swap_exact_base_for_quote │ 20,805 │ │ swap_exact_quote_for_base │ 18,590 │ │ match_bid_with_quote_quantity │ 383,275 │ │ match_bid │ 310,200 │ │ match_ask │ 316,500 │ │ place_market_order │ 37,615 │ │ inject_limit_order │ 70,195 │ │ place_limit_order │ 184,740 │ │ order_is_bid │ 540 │ │ emit_order_canceled │ 4,905 │ │ emit_order_filled │ 8,335 │ │ cancel_order │ 57,890 │ │ remove_order │ 20,095 │ │ cancel_all_orders │ 64,425 │ │ batch_cancel_order │ 102,405 │ │ list_open_orders │ 57,300 │ │ account_balance │ 6,620 │ │ get_market_price │ 3,265 │ │ get_level2_book_status_bid_side │ 39,785 │ │ get_level2_book_status_ask_side │ 39,785 │ │ get_level2_book_status │ 23,545 │ │ get_order_status │ 20,385 │ ├─────────────────────────────────────┴────────────┤ │ Package will pass metering check! │ ╰──────────────────────────────────────────────────╯ ``` ## Stack - #16903 - #16941 - #16945 - #16963 --- If your changes are not user-facing and do not break anything, you can skip the following section. Otherwise, please briefly describe what has changed under the Release Notes section. ### Type of Change (Check all that apply) - [ ] protocol change - [x] user-visible impact - [ ] breaking change for a client SDKs - [ ] breaking change for FNs (FN binary must upgrade) - [ ] breaking change for validators or node operators (must upgrade binaries) - [ ] breaking change for on-chain data layout - [ ] necessitate either a data wipe or data migration ### Release notes `sui client verify-bytecode-meter` supports passing multiple `--module` flags to verify multiple compiled modules together as if they were one package.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Pulling the
Metertrait definition out of each version of the verifier into a common place. This is so that this trait can be used as part of the execution layer interface.The overall motivation is so that we can supply a
Meterimplementation that captures more data when run from the CLI, to improve the quality of output fromsui client verify-bytecode-meter.Test Plan
Stack