On Thu, 6 Oct 2016, James Hogan wrote: > I don't particularly object to always allocating our own vector when > EBase is present. It'd probably break KVM, but that's KVM's fault for > not emulating EBase properly yet. In most cases we'll use the default KSEG0 base address anyway, won't we? > I suppose there is also an advantage to keeping the bootloader exception > vector as alive as possible at least until Linux has set up its own one, > as it allows early bugs to be caught by the bootloader, which can dump > registers etc and even return to the bootloader prompt. Right, but I think using our own allocated memory actually helps that in that we can install our exception handlers first and only then switch EBase, which is atomic (modulo probing for WG, but perhaps we don't actually have to do that). Whereas overwriting firmware memory already pointed to by EBase while installing exception handlers is pretty much destructive right away, as there'll always be a stage at which a partially installed handler is non-functional. Maciej
