qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	qemu-devel@nongnu.org, jim@groklearning.com,
	Fam Zheng <famz@euphon.net>, Thomas Huth <thuth@redhat.com>,
	joel@jms.id.au, marcandre.lureau@redhat.com, airlied@redhat.com,
	kraxel@redhat.com
Subject: Re: [Qemu-devel] [qemu-web RFC] Add GSoC/Outreachy 2018 retrospective blog post
Date: Wed, 23 Jan 2019 16:53:38 +0000	[thread overview]
Message-ID: <20190123165338.GA8724@stefanha-x1.localdomain> (raw)
In-Reply-To: <975d05a9-57f1-4183-b84e-231265e3177e@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 3709 bytes --]

On Wed, Jan 23, 2019 at 03:50:05PM +0100, Paolo Bonzini wrote:
> On 03/01/19 16:33, Stefan Hajnoczi wrote:
> > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> > ---
> > Dear mentors,
> > Let's post an overview of what was achieved in GSoC/Outreachy 2018.  I
> > have populated a blog post with information available to me, but I'm
> > sure it can be improved to explain how the project went and the current
> > status.
> > 
> > Please let me know what should be changed, thanks!
> > ---
> >  _posts/2019-01-03-internships-wrapup.md | 61 +++++++++++++++++++++++++
> >  1 file changed, 61 insertions(+)
> >  create mode 100644 _posts/2019-01-03-internships-wrapup.md
> > 
> > diff --git a/_posts/2019-01-03-internships-wrapup.md b/_posts/2019-01-03-internships-wrapup.md
> > new file mode 100644
> > index 0000000..ec245e6
> > --- /dev/null
> > +++ b/_posts/2019-01-03-internships-wrapup.md
> > @@ -0,0 +1,61 @@
> > +---
> > +layout: post
> > +title:  "GSoC and Outreachy 2018 retrospective"
> > +date:   2019-01-03 07:50:00 +0100
> > +categories: [gsoc, outreachy, internships]
> > +---
> > +QEMU participates in open source internship programs including Google Summer of
> > +Code (GSoC) and Outreachy.  These full-time remote work opportunities allow
> > +talented new developers to get involved in our community.  This post highlights
> > +what our interns achieved in 2018.
> > +
> > +## micro:bit board emulation
> > +
> > +Julia Suvorova (Outreachy) and Steffen Görtz (GSoC) tackled adding emulation
> > +support for the [micro:bit ARM board](https://microbit.org/).  Although QEMU
> > +already has plenty of ARM emulation code, the Cortex-M0 CPU used in the
> > +micro:bit was not yet implemented and the nRF51 system-on-chip was also
> > +missing.
> > +
> > +The goal of this project was to run micro:bit programs (usually created with
> > +the [MicroPython](https://python.microbit.org/v/1.1) or
> > +[Javascript/Blocks](https://makecode.microbit.org/) IDEs) with a core set of
> > +emulated devices, including the serial port, pushbuttons, and LEDs.
> > +
> > +QEMU 3.1 already shipped the groundwork for the new `qemu-system-arm -M
> > +microbit` machine type.  Enough functionality to run basic micro:bit programs
> > +is expected in the next QEMU release.
> > +
> > +## Patchew REST API improvements
> > +
> > +Shubham Jain (GSoC) created a REST API for the Patchew continuous integration
> > +system that is at the heart of QEMU's development process.  The previous API
> > +was not RESTful and exposed database schema internals.
> 
> The improvements to the REST API have been included into Patchew and are
> deployed on http://patchew.org/.  They are not in use yet, pending more
> work on authentication; this may be the topic of a future Summer of Code
> internship.
> 
> > +## Qtest Driver Framework
> > +
> > +Emanuele Esposito (GSoC) enhanced QEMU's test infrastructure with an engine
> > +that starts tests with all variants of devices that they are capable of
> > +driving.
> > +
> > +This is a complicated task in QEMU since certain devices and busses are
> > +available in an architecture-specific way on each emulation target, making it
> > +hard to write test cases without lots of hardcoded dependencies - and to keep
> > +them up-to-date!
> > +
> > +The qgraph framework that Emanuele created eliminates the need to hardcode each
> > +variant into the test.
> 
> Emanuele also converted several existing tests.  His framework was also
> presented at KVM Forum 2019 by Laurent Vivier, Emanuele's mentor,  and
> should be merged in 4.0.

Thank you, I have included your feedback in v2.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

      reply	other threads:[~2019-01-23 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 15:33 [Qemu-devel] [qemu-web RFC] Add GSoC/Outreachy 2018 retrospective blog post Stefan Hajnoczi
2019-01-23 14:50 ` Paolo Bonzini
2019-01-23 16:53   ` Stefan Hajnoczi [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=20190123165338.GA8724@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=airlied@redhat.com \
    --cc=famz@euphon.net \
    --cc=jim@groklearning.com \
    --cc=joel@jms.id.au \
    --cc=kraxel@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    /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).