From: Avi Kivity <avi@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: Memory API feature page
Date: Wed, 10 Aug 2011 18:08:04 +0300 [thread overview]
Message-ID: <4E429ED4.4040707@redhat.com> (raw)
While the memory API is not a feature, it deserves a feature page, so I
can put the TODO list there:
http://wiki.qemu.org/Features/Memory_API
Please consider helping out. Device conversions are easy, if boring,
and there's no end to them. There is a lot of more interesting work on
the core itself, but I'd like to defer it until conversion is complete.
--
error compiling committee.c: too many arguments to function
reply other threads:[~2011-08-10 15:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E429ED4.4040707@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).