On Wed, Jul 27, 2022 at 03:29:03PM +0100, Marc Zyngier wrote: > Having multiple versions of on_accessible_stack() (one per unwinder) > makes it very hard to reason about what is used where due to the > complexity of the various includes, the forward declarations, and > the reliance on everything being 'inline'. > > Instead, move the code back where it should be. Each unwinder > implements: > > - on_accessible_stack() as well as the helpers it depends on, > > - unwind()/unwind_next(), as they pass on_accessible_stack as > a parameter to unwind_next_common() (which is the only common > code here) Reviewed-by: Mark Brown <broonie@xxxxxxxxxx> It feels like more of the accessibility stuff *should* be sharable, but yeah.
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
