From: Stafford Horne <shorne@gmail.com>
To: Linux OpenRISC <linux-openrisc@vger.kernel.org>
Cc: Sahil Siddiq <icegambit91@gmail.com>, Miao Chen <chenmiao.ku@gmail.com>
Subject: GSoC 2025 OpenRISC Linux Feature Development
Date: Fri, 9 May 2025 21:03:01 +0100 [thread overview]
Message-ID: <aB5fdVgEiVZ4XsLw@antec> (raw)
Hi All,
Congratulations to Chen Miao for being selected as this year's google summer of
code [0] contributor under the OpenRISC project.
This project will have the contributor developing, testing and sending patches up to
the Linux kernel.
The OpenRISC Linux kernel support is under constant development but there are
certain Linux facilities that are not yet used or available on the OpenRISC
platform.
The project will be to work on:
- Add tracing facilities to OpenRISC Linux including: jump_label, ftrace,
kprobes, eBPF etc.
Options include:
- Convert OpenRISC to use common-entry framework
- Virtually mapped stacks [1]
- VDSO support
Please welcome be in welcoming Chen Miao.
-Stafford
[0] https://summerofcode.withgoogle.com
[1] https://www.youtube.com/watch?v=kmMGdSVDVuQ
next reply other threads:[~2025-05-09 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 20:03 Stafford Horne [this message]
2025-05-10 6:27 ` GSoC 2025 OpenRISC Linux Feature Development Sahil Siddiq
2025-05-10 9:28 ` Miao Chen
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=aB5fdVgEiVZ4XsLw@antec \
--to=shorne@gmail.com \
--cc=chenmiao.ku@gmail.com \
--cc=icegambit91@gmail.com \
--cc=linux-openrisc@vger.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;
as well as URLs for NNTP newsgroup(s).