[PATCH 0/3] Add CONFIGURE_RECORD_INTERRUPTS_ENABLED

[Joel Sherrill]

Is there anything the BSP has to do to support this?

What about the patch (in the docs?) to add records for arm? Is it obsolete?

I assume I just haven't noticed a documentation patch for the configure
option.

--joel

On Thu, Dec 1, 2022 at 6:11 AM Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> This enables the tracing of interrupt entry/exit events through an
> application configuration option.  The interrupt processing can be
> viewed with Trace Compass.
>
> Sebastian Huber (3):
>   bsps/irq: Rename handler in dispatch table
>   bsps/irq: Add bsp_interrupt_get_dispatch_table_slot()
>   config: Add CONFIGURE_RECORD_INTERRUPTS_ENABLED
>
>  bsps/include/bsp/irq-generic.h                | 79 ++++++++-------
>  bsps/powerpc/mpc55xxevb/include/bsp/irq.h     |  2 +-
>  bsps/riscv/riscv/include/tm27.h               |  4 +-
>  bsps/shared/irq/irq-entry-remove.c            |  6 +-
>  bsps/shared/irq/irq-generic.c                 | 41 ++++----
>  bsps/shared/irq/irq-handler-iterate.c         |  4 +-
>  bsps/shared/irq/irq-record.c                  | 97 +++++++++++++++++++
>  cpukit/doxygen/appl-config.h                  | 23 +++++
>  cpukit/include/rtems/confdefs/extensions.h    |  8 ++
>  cpukit/include/rtems/record.h                 |  2 +
>  spec/build/bsps/objirq.yml                    |  1 +
>  spec/build/bsps/powerpc/ss555/bspss555.yml    |  1 +
>  .../validation/tc-bsp-interrupt-spurious.c    |  4 +-
>  testsuites/validation/tc-intr-entry-install.c |  4 +-
>  testsuites/validation/tc-intr-entry-remove.c  |  8 +-
>  .../validation/tc-intr-handler-iterate.c      |  4 +-
>  16 files changed, 218 insertions(+), 70 deletions(-)
>  create mode 100644 bsps/shared/irq/irq-record.c
>
> --
> 2.35.3
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20221201/6b3efd01/attachment.htm>