From: stephen@brennan.io (Stephen Brennan)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Does anyone have experience about linux kernel dev and test in QEMU?
Date: Fri, 26 May 2017 14:05:23 -0400 [thread overview]
Message-ID: <20170526180523.GA5661@pride> (raw)
In-Reply-To: <SN1PR04MB2016EEEB0905B8839983B489ECF90@SN1PR04MB2016.namprd04.prod.outlook.com>
Hi Douglas,
I'm not terribly experienced, but here are my two cents.
On Tue, May 23, 2017 at 12:29:09AM +0000, Douglas Su wrote:
> After some searching works, however, I barely find any
> reading material or tutorial about the details of using QEMU in kernel
> development,
I might suggest two tools I've found useful for this purpose. First,
eudyptula-boot [1], a shell script that helps you run QEMU using the same
file system as your host (thanks to 9P). Second, vido [2], a similar tool
implemented in Python. I prefer vido because it's easier for me to extend
in Python.
In both cases, you don't have to mess around with building a VM image, and
for the most part filesystem access is seamless. These solutions don't
bother with a dedicated init process, so some things are odd (for instance,
orphaned processes that die remain zombies forever). Their minimum
configuration is pretty small so rebuilding is quick and your development
cycle is pretty great.
> especially the driver development.
You'll probably need to get into some low-level specifics for getting your
devices passed through to QEMU. I have no experience here. I've not really
thought of QEMU as being an excellent solution for driver development.
Best,
Stephen
[1]: https://github.com/vincentbernat/eudyptula-boot
[2]: https://github.com/g2p/vido
prev parent reply other threads:[~2017-05-26 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 0:29 Does anyone have experience about linux kernel dev and test in QEMU? Douglas Su
2017-05-23 2:50 ` Tobin C. Harding
2017-05-23 8:23 ` Roman Storozhenko
2017-05-26 18:05 ` Stephen Brennan [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=20170526180523.GA5661@pride \
--to=stephen@brennan.io \
--cc=kernelnewbies@lists.kernelnewbies.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).