From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>,
Shubham Kumar <kumar.shubham@research.iiit.ac.in>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] regarding codebase
Date: Mon, 6 Feb 2017 13:51:29 -0600 [thread overview]
Message-ID: <028cef8c-2f84-b98a-b914-ed9f5c98acfc@redhat.com> (raw)
In-Reply-To: <20170203152407.GH642@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]
On 02/03/2017 09:24 AM, Stefan Hajnoczi wrote:
> On Fri, Feb 03, 2017 at 02:28:49AM +0530, Shubham Kumar wrote:
>> I'm having difficulty in understanding the codebase of QEMU .There seem to have hundreds of code files and header files in the directory and I'm unable to figure out the functionality of each file.Is there any way to understand the function of each file ??
>
> vl.c is the main() function for the qemu-system-* family of programs
> (the "system emulators"). You could start exploring the source code
> from there. That's what I did when I first started hacking on QEMU.
>
> Be prepared to read code. QEMU isn't an educational codebase and the
> code reflects the requirements of many contributors over the years.
> Most of their requirements may not be relevant to you. You will learn
> to skip the stuff that doesn't affect you and to see the big picture.
In fact, I seriously doubt ANYONE knows the entire code base. Rather,
various people are experts in a subset of the code base; the MAINTAINERS
file is a good mapping of where to direct questions about a particular
file. It's also a good jumping off point if you see a category that
interests you for knowing what files to inspect related to that category.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-02-06 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 20:58 [Qemu-devel] regarding codebase Shubham Kumar
2017-02-03 15:24 ` Stefan Hajnoczi
2017-02-06 19:51 ` Eric Blake [this message]
2017-02-06 22:14 ` Peter Maydell
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=028cef8c-2f84-b98a-b914-ed9f5c98acfc@redhat.com \
--to=eblake@redhat.com \
--cc=kumar.shubham@research.iiit.ac.in \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).