mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@arm.com>
To: "Bouron, Justinien" <jbouron@amazon.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	David Hildenbrand <david@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Ryan Roberts <ryan.roberts@arm.com>,
	Ada Couprie Diaz <ada.coupriediaz@arm.com>,
	Kevin Brodsky <kevin.brodsky@arm.com>,
	Lorenzo Stoakes <ljs@kernel.org>,
	Quentin Perret <qperret@google.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Kudrjavets, Gunnar" <gunnarku@amazon.com>
Subject: Re: [PATCH] arm64: Add user and kernel page-fault tracepoints
Date: Wed, 9 Sep 2026 18:50:58 +0100	[thread overview]
Message-ID: <20260909175058.GE200420@e132581.arm.com> (raw)
In-Reply-To: <FFEB5A47-7651-4607-A127-8CC07D241F4C@amazon.com>

Hi Justinien,

On Wed, Sep 09, 2026 at 01:13:42PM +0000, Bouron, Justinien wrote:
> Leo,
> 
> Thank you for the feedback. I've posted a second revision at
> https://lore.kernel.org/lkml/20260902115216.49158-1-jbouron@amazon.com/, though
> it doesn't seem to be getting much traction.

This should be in the arm64 maintainers' scope (v1 caught my attention
due to it mentioned perf related things).

I think the main question is these tracepoints overlap with perf sw
events. Could you elaborate on why ftrace tracepoints are necessary?
('perf record' and 'perf script' can provide similar info and we can
avoid extra latency).

If the maintainers think this patch is reasonable, I'd be happy to help
test it.

Thanks,
Leo

      reply	other threads:[~2026-09-09 17:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20  4:55 Justinien Bouron
2026-05-20  7:36 ` Leo Yan
2026-05-20 16:45   ` Justinien Bouron
2026-09-09 13:13   ` Bouron, Justinien
2026-09-09 17:50     ` Leo Yan [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=20260909175058.GE200420@e132581.arm.com \
    --to=leo.yan@arm.com \
    --cc=ada.coupriediaz@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=david@kernel.org \
    --cc=gunnarku@amazon.com \
    --cc=jbouron@amazon.com \
    --cc=kevin.brodsky@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ljs@kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=qperret@google.com \
    --cc=ryan.roberts@arm.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
all inboxes | Powered by JetHome®