From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: "Song Bao Hua (Barry Song)" <song.bao.hua@hisilicon.com>
Cc: "will@kernel.org" <will@kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
Linuxarm <linuxarm@huawei.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] iommu/arm-smmu-v3: add tracepoints for cmdq_issue_cmdlist
Date: Fri, 28 Aug 2020 10:33:25 +0200 [thread overview]
Message-ID: <20200828083325.GC3825485@myrica> (raw)
In-Reply-To: <f8f00caacc774c79b7c0c7a39abf795f@hisilicon.com>
On Fri, Aug 28, 2020 at 07:55:18AM +0000, Song Bao Hua (Barry Song) wrote:
>
>
> > -----Original Message-----
> > From: Jean-Philippe Brucker [mailto:jean-philippe@linaro.org]
> > Sent: Friday, August 28, 2020 7:41 PM
> > To: Song Bao Hua (Barry Song) <song.bao.hua@hisilicon.com>
> > Cc: iommu@lists.linux-foundation.org; linux-arm-kernel@lists.infradead.org;
> > robin.murphy@arm.com; will@kernel.org; Linuxarm <linuxarm@huawei.com>
> > Subject: Re: [PATCH] iommu/arm-smmu-v3: add tracepoints for
> > cmdq_issue_cmdlist
> >
> > Hi,
> >
> > On Thu, Aug 27, 2020 at 09:33:51PM +1200, Barry Song wrote:
> > > cmdq_issue_cmdlist() is the hotspot that uses a lot of time. This
> > > patch adds tracepoints for it to help debug.
> > >
> > > Signed-off-by: Barry Song <song.bao.hua@hisilicon.com>
> > > ---
> > > * can furthermore develop an eBPF program to benchmark using this
> > > trace
> >
> > Have you tried using kprobe and kretprobe instead of tracepoints?
> > Any noticeable performance drop?
>
> Yes. Pls read this email.
> kprobe overhead and OPTPROBES implementation on ARM64
> https://www.spinics.net/lists/arm-kernel/msg828788.html
Thanks for the pointer. I'm asking because I've been working on BPF
trampolines (fentry/fexit) for arm64, which reduce the overhead of BPF
tracing, and am looking for confirmation that it's needed before spending
more time on it. Perhaps OPTPROBE would be a better first step, though, it
seems more generic.
Thanks,
Jean
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-28 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 9:33 [PATCH] iommu/arm-smmu-v3: add tracepoints for cmdq_issue_cmdlist Barry Song
2020-08-28 7:41 ` Jean-Philippe Brucker
2020-08-28 7:55 ` Song Bao Hua (Barry Song)
2020-08-28 8:33 ` Jean-Philippe Brucker [this message]
2020-08-28 10:29 ` Will Deacon
2020-08-28 11:02 ` Song Bao Hua (Barry Song)
2020-08-28 11:18 ` Robin Murphy
2020-08-28 11:58 ` Song Bao Hua (Barry Song)
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=20200828083325.GC3825485@myrica \
--to=jean-philippe@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=robin.murphy@arm.com \
--cc=song.bao.hua@hisilicon.com \
--cc=will@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox