On Sat, Jul 22, 2017 at 10:51:42PM -0700, Don Lewis wrote: > > The stack is aligned to a 4096 (0x1000) boundary. The first access to a > > local variable below 0xfffffe085cfa5000 is what triggered the trap. The > > other end of the stack must be at 0xfffffe085cfa9000 less a bit. I don't > > know why the first stack pointer value in the trace is > > 0xfffffe085cfa8a10. That would seem to indicate that amd64_syscall is > > using ~1500 bytes of stack space. > > Actually there could be quite a bit of CPU context that gets saved. That > could be sizeable on amd64.
Yes, the usermode trap frame is located on the kernel stack. Also, pcb and usermode FPU save area (FPU == all non-general purpose x86 registers, including XMM/AVX/AVX512 as implemented by CPU) are on the stack. _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
