From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: James Jacobsson <slowcoder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Patch to add doxygen documentation to KVM
Date: Tue, 19 Dec 2006 16:54:57 +0200 [thread overview]
Message-ID: <4587FD41.9010405@qumranet.com> (raw)
In-Reply-To: <fe247b50612190552s311311ag386a4f19284febfd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
James Jacobsson wrote:
> Attached is a patch to add some API documentation for libkvm to the
> source-tree (applies to the trunk).
> Also attached is the Doxyfile and a separate document which I use to
> generate documentation on my machine, just for reference.
>
> This is the first suggestion of how we could have our documentation,
> so it's nowhere near complete, although it covers many of the libkvm
> functions already.
>
> I'd appreciate any feedback you could give me on the documentation,
> such as if it is verbose enough, is it accurate, etc.
>
First, great job.
Second, please tell your mailer to set the content disposition of
attachments to "inline". This allows easy review and feedback.
Some concrete feedback:
- wrap lines at 80 characters
- documenting the registers is a bit too verbose. VMM authors are
expected to know such things.
- the documentation for kvm_inject_irq() is incorrect - the input is not
a bitmask, but a vector number. The processor does not have 256
interrupt pins. You can say something along the lines of "simulate an
external vectored interrupt".
- kvm_run() also returns on a signal (EINTR), which is not an error.
Signals are the primary method of simulating external interrupts and
timers, and for implementing I/O completions.
- kvm_run() should explicitly state (it is only implied now) that it
will call functions in the callback vector.
- the patch should contain changes to user/Makefile so that 'make doc'
there will generate the documentation. Please put all files into the
patch ('diff -N')
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-12-19 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 13:52 Patch to add doxygen documentation to KVM James Jacobsson
[not found] ` <fe247b50612190552s311311ag386a4f19284febfd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2006-12-19 14:54 ` Avi Kivity [this message]
[not found] ` <4587FD41.9010405-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-12-21 10:31 ` James Jacobsson
[not found] ` <fe247b50612210231p155f4861ieb060258b1d72909-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2006-12-21 10:38 ` 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=4587FD41.9010405@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=slowcoder-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 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.