Handle non-dtrace-triggered kernel breakpoint traps in mips.If DTRACE is enabled at compile time, all kernel breakpoint traps arefirst given to dtrace to see if they are triggered by a FBT probe.
Handle non-dtrace-triggered kernel breakpoint traps in mips.If DTRACE is enabled at compile time, all kernel breakpoint traps arefirst given to dtrace to see if they are triggered by a FBT probe.Previously if dtrace didn't recognize the trap, it was silentlyignored breaking the handling of other kernel breakpoint traps such asthe debug.kdb.enter sysctl. This only returns early from the traphandler if dtrace recognizes the trap and handles it.Submitted by: Nicolò Mazzucato <[email protected]>Reviewed by: markjObtained from: CheriBSDDifferential Revision: https://reviews.freebsd.org/D24478
show more ...
Enable dtrace support for mips64 and the ERL kernel configTurn on the required options in the ERL config file, and ensurethat the fbt module is listed as a dependency for mips inthe modules/dtrac
Enable dtrace support for mips64 and the ERL kernel configTurn on the required options in the ERL config file, and ensurethat the fbt module is listed as a dependency for mips inthe modules/dtrace/dtraceall/dtraceall.c file.PR: 220346Reviewed by: gnn, markjMFC after: 2 weeksDifferential Revision: https://reviews.freebsd.org/D12227
Corrected misspelled versions of rendezvous.The MFC will include a compat definition of smp_no_rendevous_barrier()that calls smp_no_rendezvous_barrier().Reviewed by: gnn, kibMFC after: 1 weekD
Corrected misspelled versions of rendezvous.The MFC will include a compat definition of smp_no_rendevous_barrier()that calls smp_no_rendezvous_barrier().Reviewed by: gnn, kibMFC after: 1 weekDifferential Revision: https://reviews.freebsd.org/D10313
Implement FBT provider (MD part) for DTrace on MIPS.Tested on MIPS64.Sponsored by: DARPA, AFRLSponsored by: HEIF5
Make the second argument of dtrace_invop() a trapframe pointer.Currently this argument is a pointer into the stack which is used by FBTto fetch the first five probe arguments. On all non-x86 archi
Make the second argument of dtrace_invop() a trapframe pointer.Currently this argument is a pointer into the stack which is used by FBTto fetch the first five probe arguments. On all non-x86 architectures it'ssimply the trapframe address, so this change has no functional impact. Onamd64 it's a pointer into the trapframe such that stack[1 .. 5] gives thefirst five argument registers, which are deliberately grouped together inthe amd64 trapframe definition.A trapframe argument simplifies the invop handlers on !x86 and makes thex86 FBT invop handler easier to understand. Moreover, it allows for invophandlers that may want to modify the register set of the interrupted thread.
Remove unused variables dtrace_in_probe and dtrace_in_probe_addr.
As <machine/vmparam.h> is included from <vm/vm_param.h>, there is noneed to include it explicitly when <vm/vm_param.h> is already included.Suggested by: alcReviewed by: alcDifferential Revision:
As <machine/vmparam.h> is included from <vm/vm_param.h>, there is noneed to include it explicitly when <vm/vm_param.h> is already included.Suggested by: alcReviewed by: alcDifferential Revision: https://reviews.freebsd.org/D5379
Fix DTrace's panic() action.It would previously call into some unfinished Solaris compatibility code andreturn without actually calling panic(9). The compatibility code isunneeded, however, so ju
Fix DTrace's panic() action.It would previously call into some unfinished Solaris compatibility code andreturn without actually calling panic(9). The compatibility code isunneeded, however, so just remove it and have dtrace_panic() call vpanic(9)directly.Differential Revision: https://reviews.freebsd.org/D2349Reviewed by: avgMFC after: 2 weeksSponsored by: EMC / Isilon Storage Division
Restore the trap type argument to the DTrace trap hook, removed in r268600.It's redundant at the moment since it can be obtained from the trapframeon the architectures where DTrace is supported, bu
Restore the trap type argument to the DTrace trap hook, removed in r268600.It's redundant at the moment since it can be obtained from the trapframeon the architectures where DTrace is supported, but this won't be the casewith ARM.
Invoke the DTrace trap handler before calling trap() on amd64. This matchesthe upstream implementation and helps ensure that a trap induced by tracingfbt::trap:entry is handled without recursively
Invoke the DTrace trap handler before calling trap() on amd64. This matchesthe upstream implementation and helps ensure that a trap induced by tracingfbt::trap:entry is handled without recursively generating another trap.This makes it possible to run most (but not all) of the DTrace tests undercommon/safety/ without triggering a kernel panic.Submitted by: Anton Rang <[email protected]> (original version)Phabric: D95
- For o32 ABI get arguments from the stack- Clear CPU_DTRACE_FAULT flag in userland backtrace routine. It just means we hit wrong memory region and should stop.
Use macroses to load/store pointers and increase indexes instead of hardcoded MIPS64 instructions
Add device part of DTrace/MIPS code