Gerwin Klein

@kent-mcleod there are a few Arm platforms that don't use `gic_v2.h` or `gic_v3.h`, which means they are currently not defining the right interface functions. If the RFC is accepted, these...

> > It's a bit early to review the PR (should have left it on draft). We should sort out the API in the RFC discussion first. > > The...

> Ok, I'll just use a 32bit capSGITarget and 4 bit capSGIIRQ fields for now. 👍 > In the call there was a request to expose GICv3 SGI targeting functionality...

Given #1238 I think we can close this issue. Please re-open if still relevant.

Do we know how much slower the slow path becomes with this patch? The additional checks are probably not much, but it would be nice to quantify. If there is...

Do you have a test case that shows the error and that we can use to make sure the fix works and the error doesn't reappear down the line?

> This seem to be a general issue then that other code might also run into. Thus, I wonder if we should provide a version of `seL4_ReplyRecv()` that returns all...

Looks like a good list. Additional ideas (not necessarily all for right now): - Ideally, we'd also have an actual test suite that tests each feature with positive and negative...

> The real solution is probably to have _less_ dependencies, but I'm not sure how feasible that is. Yup, definitely the fewer the better.

`continue` is definitely supported, so it would be good to figure out what is going on. This change seems to be doing a whole lot of other stuff too, though....