From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Tapas Mishra <mightydreams@gmail.com>
Cc: Xen List <xen-devel@lists.xensource.com>
Subject: Re: systematic way to study Xen from development side
Date: Tue, 12 Jul 2011 14:30:53 -0400 [thread overview]
Message-ID: <20110712183053.GA4071@dumpdata.com> (raw)
In-Reply-To: <CALKraOaAMCoZLMPL=ZAD5DUJEM3zFBUeoKOgsNSYQHxpnvmoYw@mail.gmail.com>
On Sun, Jul 10, 2011 at 12:30:29PM +0530, Tapas Mishra wrote:
> Hi,
>
> I am trying to understand xen from the perspective of a developer.I
> have written basic kernel module and char driver.
Ok.
> After this I have read and understood various device drivers given in
> Orielly Greg Kroah Hartman's ,Linux Device Drivers book.
> I was looking at following tree
>
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=tree;h=refs/heads/xen/stable-2.6.32.x;hb=refs/heads/xen/stable-2.6.32.x
>
> and was browsing through main.c,
> I do not think that merely browsing the code I would be able to understand it.
> Is there a systematic way for the same, i.e. like there was device
> drivers book and ,Linux Kernel Development book of Robert Love,
> from which I understood many many concepts.What is the standard
> approach to understand the code when it comes to development of Xen
> when
> some one wants to be well versed with Xen development?
Well, I would recommend looking at it from the bootup process
(enlighten.c).. But that might be a bit overwhelming at first.
Did you look at the 'Definite Guide to the Xen hypervisor'? It gives a
explanation of how Xen functions and what are the minium requirements
for a kernel to boot under Xen.
next prev parent reply other threads:[~2011-07-12 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 7:00 systematic way to study Xen from development side Tapas Mishra
2011-07-12 18:30 ` Konrad Rzeszutek Wilk [this message]
2011-07-13 4:08 ` Tapas Mishra
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=20110712183053.GA4071@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=mightydreams@gmail.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.