From: Sahil Siddiq <icegambit91@gmail.com>
To: Linux OpenRISC <linux-openrisc@vger.kernel.org>,
Stafford Horne <shorne@gmail.com>
Subject: KProbes for OpenRISC-linux
Date: Tue, 9 Sep 2025 09:56:06 +0530 [thread overview]
Message-ID: <56e910a3-46c7-4df1-b1cf-ebdfaf8e49dc@gmail.com> (raw)
In-Reply-To: <51b89c55-ee58-461d-a2a0-5c8dd8ba77e7@gmail.com>
Hi,
On 5/10/25 1:48 PM, Sahil Siddiq wrote:
> Sure. Based on what I have understood from the synopsis of the GSoC proposal [1],
> the focus will initially be on jump_labels. So, I'll start going through kprobes
> in the meantime.
I am writing this email to let you know that I am still interested in implementing
KProbes for OpenRISC-Linux. My changes make use of Miao's text patching implementation.
I should be able to send a patch soon.
Thanks,
Sahil
next prev parent reply other threads:[~2025-09-09 4:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-03 16:14 Queries regarding ftrace's implementation for OpenRISC-linux Sahil Siddiq
2025-05-06 15:03 ` Stafford Horne
2025-05-08 18:40 ` Sahil Siddiq
2025-05-09 18:59 ` Stafford Horne
2025-05-10 8:18 ` Sahil Siddiq
2025-09-09 4:26 ` Sahil Siddiq [this message]
2025-09-11 9:52 ` KProbes " Stafford Horne
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=56e910a3-46c7-4df1-b1cf-ebdfaf8e49dc@gmail.com \
--to=icegambit91@gmail.com \
--cc=linux-openrisc@vger.kernel.org \
--cc=shorne@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).