From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] firewire: ohci: add tracepoints event for data of Self-ID DMA
Date: Thu, 4 Jul 2024 09:07:01 +0900 [thread overview]
Message-ID: <20240704000701.GA1447446@workstation.local> (raw)
In-Reply-To: <20240702222034.1378764-6-o-takashi@sakamocchi.jp>
Hi,
On Wed, Jul 03, 2024 at 07:20:34AM +0900, Takashi Sakamoto wrote:
> In 1394 OHCI, the SelfIDComplete event occurs when the hardware has
> finished transmitting all of the self ID packets received during the bus
> initialization process to the host memory by DMA.
>
> This commit adds a tracepoints event for this event to trace the timing
> and packet data of Self-ID DMA. It is the part of following tracepoints
> events helpful to debug some events at bus reset; e.g. the issue addressed
> at a commit d0b06dc48fb1 ("firewire: core: use long bus reset on gap count
> error")[1]:
>
> * firewire_ohci:irqs
> * firewire_ohci:self_id_complete
> * firewire:bus_reset_handle
> * firewire:self_id_sequence
>
> They would be also helpful in the problem about invocation timing of
> hardIRQ/softIRQ contexts. We can often see this kind of problem with -rt
> kernel[2].
Oops, I misunderstood. The handling of Self-ID DMA buffer is in hardIRQ
and process (workqueue) contexts, thus the above issue is not the
invocation timing of hardIRQ/softIRQ contexts. Let me correct it at the
applied commit comment.
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d0b06dc48fb1
> [2] https://lore.kernel.org/linux-rt-users/YAwPoaUZ1gTD5y+k@hmbx/
>
> Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
> ---
> drivers/firewire/ohci.c | 11 +++++-
> include/trace/events/firewire_ohci.h | 54 ++++++++++++++++++++++++++++
> 2 files changed, 64 insertions(+), 1 deletion(-)
Regards
Takashi Sakamoto
next prev parent reply other threads:[~2024-07-04 0:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 22:20 [PATCH 0/5] firewire: ohci: add tracepoints event for data of Self-ID DMA Takashi Sakamoto
2024-07-02 22:20 ` [PATCH 1/5] firewire: ohci: use common macro to interpret be32 data in le32 buffer Takashi Sakamoto
2024-07-02 22:20 ` [PATCH 2/5] firewire: ohci: use static function to handle endian issue on PowerPC platform Takashi Sakamoto
2024-07-02 22:20 ` [PATCH 3/5] firewire: ohci: add static inline functions to deserialize for Self-ID DMA operation Takashi Sakamoto
2024-07-02 22:20 ` [PATCH 4/5] firewire: ohci: use inline functions to operate data of self-ID DMA Takashi Sakamoto
2024-07-02 22:20 ` [PATCH 5/5] firewire: ohci: add tracepoints event for data of Self-ID DMA Takashi Sakamoto
2024-07-04 0:07 ` Takashi Sakamoto [this message]
2024-07-03 23:30 ` [PATCH 0/5] " Takashi Sakamoto
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=20240704000701.GA1447446@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.