Add CPU features filter for executables #100
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
hoh
added a commit
to aleph-im/aleph-vm
that referenced
this pull request
May 29, 2024
Trusted computing requires CPU features such as `sev`, `sev_es` and `sev_snp`. This adds the field `properties.cpu.features` `/about/usage/system` as a list of CPU features. Currently, only SEV related features are present, but more can be added, for example `avx2`, `fma` and `f16c`. Adding them will require ensuring that they are actually active and not just present on the CPU via `/proc/cpuinfo`. This work is based on a proposal to add the relevant field on aleph-message: aleph-im/aleph-message#100
hoh
force-pushed
the
hoh-add-cpu-features
branch
from
db4654c
to
e97fdc1
Compare
This allows the user to specify CPU features the CPU that must be available in order to run the VM. This should help with automatic and manual scheduling to the right machines.
hoh
force-pushed
the
hoh-add-cpu-features
branch
from
e97fdc1
to
618778e
Compare
olethanh
approved these changes
Jun 18, 2024
hoh
added a commit
to aleph-im/aleph-vm
that referenced
this pull request
Jun 19, 2024
Trusted computing requires CPU features such as `sev`, `sev_es` and `sev_snp`. This adds the field `properties.cpu.features` `/about/usage/system` as a list of CPU features. Currently, only SEV related features are present, but more can be added, for example `avx2`, `fma` and `f16c`. Adding them will require ensuring that they are actually active and not just present on the CPU via `/proc/cpuinfo`. This work is based on a proposal to add the relevant field on aleph-message: aleph-im/aleph-message#100
hoh
added a commit
to aleph-im/aleph-vm
that referenced
this pull request
Jun 20, 2024
Trusted computing requires CPU features such as `sev`, `sev_es` and `sev_snp`. This adds the field `properties.cpu.features` `/about/usage/system` as a list of CPU features. Currently, only SEV related features are present, but more can be added, for example `avx2`, `fma` and `f16c`. Adding them will require ensuring that they are actually active and not just present on the CPU via `/proc/cpuinfo`. This work is based on a proposal to add the relevant field on aleph-message: aleph-im/aleph-message#100
hoh
added a commit
that referenced
this pull request
Jun 21, 2024
This allows the user to specify CPU features the CPU that must be available in order to run the VM. This should help with automatic and manual scheduling to the right machines.
hoh
added a commit
to aleph-im/aleph-vm
that referenced
this pull request
Jun 26, 2024
Trusted computing requires CPU features such as `sev`, `sev_es` and `sev_snp`. This adds the field `properties.cpu.features` `/about/usage/system` as a list of CPU features. Currently, only SEV related features are present, but more can be added, for example `avx2`, `fma` and `f16c`. Adding them will require ensuring that they are actually active and not just present on the CPU via `/proc/cpuinfo`. This work is based on a proposal to add the relevant field on aleph-message: aleph-im/aleph-message#100
hoh
added a commit
to aleph-im/aleph-vm
that referenced
this pull request
Jun 27, 2024
Trusted computing requires CPU features such as `sev`, `sev_es` and `sev_snp`. This adds the field `properties.cpu.features` `/about/usage/system` as a list of CPU features. Currently, only SEV related features are present, but more can be added, for example `avx2`, `fma` and `f16c`. Adding them will require ensuring that they are actually active and not just present on the CPU via `/proc/cpuinfo`. This work is based on a proposal to add the relevant field on aleph-message: aleph-im/aleph-message#100
hoh
added a commit
to aleph-im/aleph-vm
that referenced
this pull request
Jun 27, 2024
Trusted computing requires CPU features such as `sev`, `sev_es` and `sev_snp`. This adds the field `properties.cpu.features` `/about/usage/system` as a list of CPU features. Currently, only SEV related features are present, but more can be added, for example `avx2`, `fma` and `f16c`. Adding them will require ensuring that they are actually active and not just present on the CPU via `/proc/cpuinfo`. This work is based on a proposal to add the relevant field on aleph-message: aleph-im/aleph-message#100
hoh
added a commit
to aleph-im/aleph-vm
that referenced
this pull request
Jun 27, 2024
Trusted computing requires CPU features such as `sev`, `sev_es` and `sev_snp`. This adds the field `properties.cpu.features` `/about/usage/system` as a list of CPU features. Currently, only SEV related features are present, but more can be added, for example `avx2`, `fma` and `f16c`. Adding them will require ensuring that they are actually active and not just present on the CPU via `/proc/cpuinfo`. This work is based on a proposal to add the relevant field on aleph-message: aleph-im/aleph-message#100
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.
Fix: CPU features required for execution could not be specified.
This allows the user to specify CPU features the CPU that must be available in order to run the VM.
This should help with automatic and manual scheduling to the right machines.
@aliel , this should help for running CPU intensive software that takes advantage of avx2, fma, f16c 😉