From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Neo Jia <neojia-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: What should I do for kvm development first?
Date: Sun, 18 Nov 2007 12:45:31 +0200 [thread overview]
Message-ID: <474017CB.9070503@qumranet.com> (raw)
In-Reply-To: <5d649bdb0711162146x32d4b74bicbf58c0f851b9ede-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Neo Jia wrote:
> hi,
>
> I am trying to contribute some (just starting some bug fix first) for
> KVM development.
>
> But, I want know first what those experienced kvm developer do
> everyday for the development work.
>
> I synced with kvm.git and kvm-userspace.git. Do I have to rebuild and
> install the entire kernel every time?
>
> I really appreciate if you can share me your development/debugging
> methods for KVM.
>
>
I generally compile kvm.git with kvm as modules, and kvm-userspace.git
with --with-patched-kernel. If I make a change to kvm, I just recompile
and reload the modules; no full rebuild is necessary.
Occasionally I merge mainline into kvm.git, which does require a full or
partial rebuild.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
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/
prev parent reply other threads:[~2007-11-18 10:45 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
[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 [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=474017CB.9070503@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=neojia-Re5JQEeQqe8AvxtiuMwx3w@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