Skip to content

Commit 173b662

Browse files
authored
Merge branch 'main' into 0200-domain-schedules
2 parents 2b9dfd2 + 746b98b commit 173b662

1 file changed

Lines changed: 3 additions & 10 deletions

File tree

src/active/0170-multikernel-ipi-api.md renamed to src/implemented/0170-multikernel-ipi-api.md

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -152,17 +152,11 @@ delivery of all signals with reasonable scalability overhead.
152152
well as adding support for interrupting multiple targets as supported by GICv2
153153
and GICv3).
154154

155-
## Unresolved questions
156-
157-
The current proposed implementation is here, but it’s awaiting a minor update to
158-
the revoke paths as part of some ongoing verification work:
159-
<https://github.com/seL4/seL4/commit/7fda970d382c034c4e9b6d49b10bfbe33d4f815f>
160-
161155
## Disposition
162156

163157
The TSC approved the RFC with the following conditions:
164158

165-
- The RFC should be updated to remove the API for broadcast and multicast for
159+
- [x] The RFC should be updated to remove the API for broadcast and multicast for
166160
now. Until we have figured out a good general model for multicast, we want to
167161
keep the API small so that conservative extensions are possible. The rationale
168162
is that for the current use case of a low number (2-16) of cores, it is cheap
@@ -171,15 +165,14 @@ The TSC approved the RFC with the following conditions:
171165
specific multicast model too early. This means, the `SGISignalCap` (on Arm)
172166
should authorise sending to a single core (and store a single SGI number).
173167

174-
- The API for Arm should be updated to include higher affinity bits for GICv3 to
168+
- [x] The API for Arm should be updated to include higher affinity bits for GICv3 to
175169
support sending to more cores. For platforms that do not support these bits
176170
(e.g. GICv2), the corresponding `IRQControl` invocation should fail if those
177171
bits are attempted to be set.
178172

179173
- The TSC confirmed that we want the API for invoking `SGISignalCaps` to be like
180174
notifications, that is, the invocation should not take any parameters beside
181-
the `SGISignal` cap itself. The current (not yet updated) pull request for this
182-
RFC is [seL4/seL4#1222].
175+
the `SGISignal` cap itself.
183176

184177
[seL4/seL4#1222]: https://github.com/seL4/seL4/pull/1222
185178
[seL4/l4v#733]: https://github.com/seL4/l4v/pull/733

0 commit comments

Comments
 (0)