From: Josh Marshall <joshua.r.marshall.1991@gmail.com>
To: linux-newbie@vger.kernel.org
Subject: Feedback on my development setup
Date: Tue, 16 Apr 2024 08:38:54 -0400 [thread overview]
Message-ID: <CAFkJGRcWdHpbxjBrynncOb3apWO7d5+WP82WqcHeq=hsc65MAA@mail.gmail.com> (raw)
Hello all,
I am trying to work on and improve some aspects of the "fanotify"
parts of the VFS subsystem with Amir Goldstein being the person I
brought these to. Amir has me doing some work to see what is going on
since I have observed some unexpected behaviors. In doing so, I have
cobbled together the following iteration pattern which I would like
feedback on. It doesn't feel like it is as concise as it should be in
practice and I am hoping someone can offer pointers on how to improve
it. By the end of this, I would like to have a fully documented and
replicable script to share for certain kinds of non-hardware kernel
development like I am doing here. As a word of warning, I haven't
gotten to fully test this either. It feels like I'm trying to cut
down a hydra with everything new I need to account for.
```
Source:
https://github.com/archlinux/arch-boxes
Term 1:
guestmount -w -a ~/Downloads/Arch-Linux-x86_64-basic.qcow2 -m
/dev/sda3 ~/mnt/arch/
<copy sources, files, perform compilation steps, etc as needed to
inside the VM image as needed each development iteration>
cp ~/mnt/ arch/home/arch/linux/boot/x86/vmlinux .
umount ~/mnt/arch
Term 2:
kvm -s -cpu host -display gtk -vga qxl -accel kvm -drive
format=qcow2,file=$HOME/Downloads/Arch-Linux-x86_64-basic.qcow2 -m 1G
-smp 2 -S
Term 3:
gdb vmlinux
: target remote:1234
<set break points>
: continue
Qemu:
<time sensitive, boot into the right kernel if available>
<perform development tasks>
```
next reply other threads:[~2024-04-16 12:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 12:38 Josh Marshall [this message]
2024-04-16 14:56 ` Feedback on my development setup ngn
2024-04-16 15:03 ` Josh Marshall
2024-04-16 15:21 ` ngn
2024-04-17 16:11 ` Josh Marshall
[not found] ` <CAPzh0z8RySn429XYQHoP_c9UA+pb6SLHGhH40vQDhc3P2xiysQ@mail.gmail.com>
2024-04-17 21:18 ` Josh Marshall
2024-04-18 15:35 ` ngn
2024-04-18 19:15 ` Josh Marshall
2024-04-18 19:27 ` Josh Marshall
2024-04-18 19:52 ` Josh Marshall
2024-04-18 21:40 ` Josh Marshall
2024-04-19 16:14 ` ngn
2024-04-23 15:34 ` Josh Marshall
2024-04-23 16:08 ` Pranjal Singh
2024-04-23 16:39 ` Bilbao, Carlos
2024-04-23 17:43 ` Josh Marshall
2024-04-25 5:37 ` Josh Marshall
2024-04-25 14:36 ` Bilbao, Carlos
2024-04-25 14:54 ` Josh Marshall
2024-04-25 15:14 ` Jonathan Corbet
[not found] ` <CAFkJGReoq2s+LR1kj1hj8QvsKsEhk+CLYtCXV=DQTjTqan3DOg@mail.gmail.com>
2024-04-25 16:59 ` Carlos Bilbao
2024-04-25 17:08 ` Josh Marshall
2024-04-25 20:14 ` Theodore Ts'o
2024-04-25 20:02 ` Theodore Ts'o
2024-04-25 14:32 ` Thomas Bertschinger
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='CAFkJGRcWdHpbxjBrynncOb3apWO7d5+WP82WqcHeq=hsc65MAA@mail.gmail.com' \
--to=joshua.r.marshall.1991@gmail.com \
--cc=linux-newbie@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 read-only IMAP folder(s) and NNTP newsgroup(s).