Talk:Google Summer of Code 2019: Difference between revisions

From QEMU
(drafts moved to their own pages)
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Drafts =


I'm saving some drafts here before including it on the wiki page. -[[User:Ehabkost|Ehabkost]] ([[User talk:Ehabkost|talk]]) 19:36, 16 January 2019 (UTC)
=== API documentation generation ===
'''Summary:''' Generation of API documentation from doc comments
QEMU currently has many functions documented using the GTK-Doc
syntax, but there is no mechanism to actually generate API
documentation from these doc comments.  We need tools to
generate API documentation from C and Python source code.
'''Links:'''
* [https://lists.gnu.org/archive/html/qemu-devel/2011-12/msg01803.html series from 2011 for gtk-doc build integration]
* [https://www.mail-archive.com/qemu-devel@nongnu.org/msg411643.html discussion about Sphinx vs gtk-doc]
* [https://www.gtk.org/gtk-doc/ GTK-Doc Project]
'''Details:'''
* Skill level: beginner
* Language: C, Python
* Mentor: Eduardo Habkost <ehabkost@redhat.com>, ehabkost
* Suggested by: Eduardo Habkost
=== Guest ABI automated testing ===
'''Summary:''' Automated test of Guest ABI and compatibility
QEMU tries to provide a stable '''guest ABI''' on versioned
machine-types.  Despite investing lots of effort keeping
compatibility, we have no automated testing to detect common
bugs that break guest ABI.  It should be possible to write
automated test cases that will compare a virtual machine to a
previously stored dump of guest ABI information, including:
* CPUID data
* Physical memory and I/O port maps
* Device addresses (PCI, USB, etc.)
'''Links:'''
* TODO
* Wiki links to relevant material
* External links to mailing lists or web sites
'''Details:'''
* Skill level: intermediate
* Language: C
* Mentor: Eduardo Habkost
* Suggested by: Eduardo Habkost

Latest revision as of 18:51, 21 January 2019