From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] firewire: ohci: add support for tracepoints events
Date: Thu, 27 Jun 2024 22:21:35 +0900 [thread overview]
Message-ID: <20240627132135.GA965648@workstation.local> (raw)
In-Reply-To: <20240625031806.956650-1-o-takashi@sakamocchi.jp>
On Tue, Jun 25, 2024 at 12:18:04PM +0900, Takashi Sakamoto wrote:
> Hi,
>
> 1394 OHCI hardware triggers PCI interrupts to notify any events to
> software. Current driver for the hardware is programmed by the typical
> way to utilize top- and bottom- halves, thus it has a timing gap to handle
> the notification in softIRQ (tasklet). The Linux Kernel Tracepoints
> framework is enough useful to trace the interaction between 1394 OHCI
> hardware and its driver.
>
> This series of changes adds support for tracepoints events to the
> driver, and adds an event, 'irqs', so that comparison of the event and
> any event in firewire subsystem is helpful to diagnose the timing gap.
>
> Takashi Sakamoto (2):
> firewire: ohci: add support for Linux kernel tracepoints
> firewire: ohci: add tracepoints event for hardIRQ event
>
> drivers/firewire/ohci.c | 4 +++
> include/trace/events/firewire.h | 1 +
> include/trace/events/firewire_ohci.h | 47 ++++++++++++++++++++++++++++
> 3 files changed, 52 insertions(+)
> create mode 100644 include/trace/events/firewire_ohci.h
Applied to for-next branch.
Regards
Takashi Sakamoto
prev parent reply other threads:[~2024-06-27 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 3:18 [PATCH 0/2] firewire: ohci: add support for tracepoints events Takashi Sakamoto
2024-06-25 3:18 ` [PATCH 1/2] firewire: ohci: add support for Linux kernel tracepoints Takashi Sakamoto
2024-06-25 3:18 ` [PATCH 2/2] firewire: ohci: add tracepoints event for hardIRQ event Takashi Sakamoto
2024-06-27 13:21 ` Takashi Sakamoto [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240627132135.GA965648@workstation.local \
--to=o-takashi@sakamocchi.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.