Talk:Google Summer of Code 2019: Difference between revisions

From QEMU
Line 19: Line 19:
* Language: C, Python
* Language: C, Python
* Mentor: Eduardo Habkost <ehabkost@redhat.com>, ehabkost
* 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
* Suggested by: Eduardo Habkost

Revision as of 19:36, 16 January 2019

Drafts

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:

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
Retrieved from "https://wiki.qemu.org/index.php?title=Talk:Google_Summer_of_Code_2019&oldid=8095"