cpu: implement IPI support #579
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
msft-jlange
force-pushed
the
ipi
branch
2 times, most recently
from
dcc98e1 to
101a911
Compare
joergroedel
reviewed
Dec 20, 2024
msft-jlange
force-pushed
the
ipi
branch
3 times, most recently
from
bea6820 to
5d94146
Compare
|
I've added the |
joergroedel
reviewed
Jan 7, 2025
KVM does not support tracking interrupt state separately for each VMPL. The use of interrupts by the SVSM should be suppressed when running with SNP any time the SVSM is running under KVM/QEMU, not just when restricted injection is enabled. Signed-off-by: Jon Lange <[email protected]>
`CpuSet` is an object that can represent a set of CPUs. Two versions are defined, both atomic and non-atomic. The atomic version permits multiple threads to simultaneously add, remove, or iterate elements of the set. Signed-off-by: Jon Lange <[email protected]>
`ScopedRef` and `ScopedMut` are designed to solve the problem of managing lifetimes of references created from pointers. Normally, when a reference is created from a pointer (such as with `ptr::as_ref()`), it is associated with the static lifetime, and as a result, the compiler is unable to determine whether the reference will live long enough for its intended use. While functions like `ptr::as_ref()` can associate the reference with a lifetime, the compiler cannot usefully use this information to enfoce lifetime checks on pointers generated in this way because although every reference can be bound to a lifetime, a reference does not by itself own a lifetime, and without an owning lifetime, the compiler has no way to know when the lifetime to which the reference is bound goes out of scope. The `ScopedRef` and `ScopedMut` objects solve this by creating a new object every time a pointer is converted to a reference, so there is an actual object with an associated lifetime that the compiler can use to ensure that the reference remains valid. Signed-off-by: Jon Lange <[email protected]>
The address of a `PerCpuShared` as observed by the local CPU is different than the address of the same `PerCpuShared` observed by other CPUs in the global address space. There are cases where a local CPU needs to know the address that will be used by other CPUs. Signed-off-by: Jon Lange <[email protected]>
This change provides routines that enable one processor to send a message to one or other processors to perform work. Signed-off-by: Jon Lange <[email protected]>
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.
This change includes logic to support sending inter-processor interrupts (IPIs) to other processors. An IPI can be sent as a multicast message, or as a unicast message to a specific processor as a mutable message which receives a response. All IPI delivery is synchronous, meaning that the sender will block until the IPI is delivered and the receiver has processed it.