From: Stefan Metzmacher <[email protected]>
To: io-uring <[email protected]>
Subject: fast io_uring development using livepatching to test/debug simple changes
Date: Fri, 14 Oct 2022 14:14:48 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
I'm used to do kernel hacking using kernel modules, which allows me to test things very fast.
When I do io_uring coding, I just want to build my own kernel just once
and debug/test fixes without the need to rebuild/reboot.
For that I have some patches, see
https://git.samba.org/?p=metze/linux/wip.git;a=shortlog;h=refs/heads/io_uring_livepatch.v6.1
I include them in the kernel I build and then I'm able to do quick adjustments until
the feature I'm working on does what I want...
metze
reply other threads:[~2022-10-14 12:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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 \
[email protected] \
[email protected] \
[email protected] \
/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