FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=main 2024-11-22T14:03:40Z 2024-11-22T14:03:40Z Mark Johnston markj@FreeBSD.org 2024-11-22T13:51:37Z urn:sha1:cc3da1955c16df5eb0019e0fef810696b035b7cf - Use a fresh context when entering dtrace_invop() via a breakpoint exception. - Mark the #BP trapframe as initialized. MFC after: 2 weeks 2024-09-19T09:22:13Z Mark Johnston markj@FreeBSD.org 2024-09-19T09:22:13Z urn:sha1:06e7bc83f6a49b99f87ad1a6034e2fad54ebe7f3 It is not needed after commit 7e80fd5ef397. No functional change intended. Reviewed by: avg MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D46675 2023-08-16T17:54:11Z Warner Losh imp@FreeBSD.org 2023-08-16T17:54:11Z urn:sha1:95ee2897e98f5d444f26ed2334cc7c439f9c16c6 Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/ 2022-08-09T22:34:01Z Mark Johnston markj@FreeBSD.org 2022-08-09T20:08:13Z urn:sha1:3ba8e9dc4a0e0e9c35cfadfe25379871ce581697 Here, the provider is responsible for updating the trapframe to redirect control flow and for computing the return address. Once software-saved registers are restored, the emulation shifts the remaining context down on the stack to make space for the return address, then copies the address provided by the invop handler. dtrace_invop() is modified to allocate temporary storage space on the stack for use by the provider to return the return address. This is to support a new provider for amd64 which can instrument arbitrary instructions, not just function entry and exit instructions as FBT does. In collaboration with: christos Sponsored by: Google, Inc. (GSoC 2022) Sponsored by: The FreeBSD Foundation MFC after: 2 weeks 2021-04-02T12:41:51Z Konstantin Belousov kib@FreeBSD.org 2021-03-31T21:04:55Z urn:sha1:aa3ea612be3659881392251e91912682b038ce78 Reviewed by: jhb Sponsored by: The FreeBSD Foundation Differential revision: https://reviews.freebsd.org/D29529 2019-09-23T15:08:17Z Mark Johnston markj@FreeBSD.org 2019-09-23T15:08:17Z urn:sha1:9093dd9a66113e7ab2abf2557319a4acc40651f0 There is no reason for these routines to be written in assembly. In the ports of DTrace to other platforms, they are already written in C. No functional change intended. MFC after: 1 week Sponsored by: Netflix 2018-12-13T20:09:38Z Mateusz Guzik mjg@FreeBSD.org 2018-12-13T20:09:38Z urn:sha1:8ca79fbd4af2570968a92f08fb714d8c1bcb378d dtrace has its own routines which were not updated after SMAP support got implemented. Use ifunc just like for other routines. This in particular fixes ustack(). Reviewed by: markj Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D18542 2018-03-20T17:58:51Z Ed Maste emaste@FreeBSD.org 2018-03-20T17:58:51Z urn:sha1:fc2a8776a2f9945f22301cd92ec6d3ac1f817028 assym is only to be included by other .s files, and should never actually be assembled by itself. Reviewed by: imp, bdrewery (earlier) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D14180 2016-04-17T23:08:47Z Mark Johnston markj@FreeBSD.org 2016-04-17T23:08:47Z urn:sha1:6c2806594b351ec39cca31bf386bdee79571fa36 Currently this argument is a pointer into the stack which is used by FBT to fetch the first five probe arguments. On all non-x86 architectures it's simply the trapframe address, so this change has no functional impact. On amd64 it's a pointer into the trapframe such that stack[1 .. 5] gives the first five argument registers, which are deliberately grouped together in the amd64 trapframe definition. A trapframe argument simplifies the invop handlers on !x86 and makes the x86 FBT invop handler easier to understand. Moreover, it allows for invop handlers that may want to modify the register set of the interrupted thread. 2015-05-25T01:22:56Z Mark Johnston markj@FreeBSD.org 2015-05-25T01:22:56Z urn:sha1:11027ebcbba5f1bd1bc5587e1bb6bbafc4d5921b MFC after: 3 days