From: Izik Eidus <izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Dan Kenigsberg <danken-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: What should I do for kvm development first?
Date: Sat, 17 Nov 2007 17:47:08 +0200 [thread overview]
Message-ID: <473F0CFC.4000908@qumranet.com> (raw)
In-Reply-To: <20071117152930.GA4968-iWbx9bcAnq+Hk9JtIoIkgNBPR1lH4CV8@public.gmane.org>
Dan Kenigsberg wrote:
> On Fri, Nov 16, 2007 at 09:46:03PM -0800, Neo Jia wrote:
>
>> I synced with kvm.git and kvm-userspace.git. Do I have to rebuild and
>> install the entire kernel every time?
>>
>>
>
> Luckily, not. By default, when you ./configure in kvm-userspace.git, make
> is told to build the kvm kernel module against the currently-running
> kernel.
>
> The source code of the kernel module comes from the kvm.git tree. What I
> suggest is to
> make -C kernel LINUX=path/to/kvm.git sync
> (when in kvm-userspace.git) in order to copy that source code to
> kvm-userspace.git.
>
>
>> I really appreciate if you can share me your development/debugging
>> methods for KVM.
>>
>
> I hope you get more clues from other more experienced folks here. Good
> luck,
>
> Dan.
>
development methods:
1)reading the kvm code / reading
2)intel/amd system programming specs
3)ask questions in the list
debugging is very very hard in this area, most of time is just printing
the values all over kvm
and biesecting.
sometimes you might want to write a test program, but...
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-11-17 15:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 5:46 What should I do for kvm development first? Neo Jia
[not found] ` <5d649bdb0711162146x32d4b74bicbf58c0f851b9ede-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-11-17 15:29 ` Dan Kenigsberg
[not found] ` <20071117152930.GA4968-iWbx9bcAnq+Hk9JtIoIkgNBPR1lH4CV8@public.gmane.org>
2007-11-17 15:47 ` Izik Eidus [this message]
[not found] ` <473F0CFC.4000908-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-18 7:02 ` Neo Jia
[not found] ` <5d649bdb0711172302y4e3e8292r7ac10c89f0479b13-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-11-18 8:09 ` Izik Eidus
2007-11-18 10:47 ` Avi Kivity
[not found] ` <4740182E.1070208-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-18 11:00 ` Neo Jia
[not found] ` <5d649bdb0711180300p1720e15co5383337a9b5181b1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-11-18 11:04 ` Avi Kivity
[not found] ` <47401C4F.20508-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-18 11:15 ` Neo Jia
[not found] ` <5d649bdb0711180315u4a22c1c2kfe8f2a450aae38e0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-11-18 11:21 ` Avi Kivity
[not found] ` <4740202D.4070502-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-18 20:02 ` Neo Jia
[not found] ` <47409A38.50700-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-11-19 5:49 ` Avi Kivity
2007-11-18 10:45 ` Avi Kivity
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=473F0CFC.4000908@qumranet.com \
--to=izike-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=danken-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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