qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>,
	Stefano Garzarella <sgarzare@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	Fam Zheng <famz@euphon.net>,
	airlied@redhat.com, jim@groklearning.com, qemu-devel@nongnu.org,
	joel@jms.id.au, Paolo Bonzini <pbonzini@redhat.com>,
	marcandre.lureau@redhat.com, kraxel@redhat.com
Subject: Re: [Qemu-devel] [qemu-web PATCH v2] Add GSoC/Outreachy 2018 retrospective blog post
Date: Thu, 24 Jan 2019 10:30:01 +0100	[thread overview]
Message-ID: <eb8e14a4-20bf-31b1-9739-f2e763469c0e@redhat.com> (raw)
In-Reply-To: <20190123202717.GA11941@stefanha-x1.localdomain>

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

On 2019-01-23 21:27, Stefan Hajnoczi wrote:
> On Wed, Jan 23, 2019 at 06:55:07PM +0100, Stefano Garzarella wrote:
>> On Wed, Jan 23, 2019 at 04:53:10PM +0000, Stefan Hajnoczi wrote:
>>> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
>>> ---
>>> v2:
>>>  * Added mentor names
>>>  * Added additional details from Marc-André and Paolo
>>> ---
>>>  _posts/2019-01-23-internships-wrapup.md | 79 +++++++++++++++++++++++++
>>>  1 file changed, 79 insertions(+)
>>>  create mode 100644 _posts/2019-01-23-internships-wrapup.md
>>>
>>> diff --git a/_posts/2019-01-23-internships-wrapup.md b/_posts/2019-01-23-internships-wrapup.md
>>> new file mode 100644
>>> index 0000000..fefcc2a
>>> --- /dev/null
>>> +++ b/_posts/2019-01-23-internships-wrapup.md
>>> @@ -0,0 +1,79 @@
>>> +---
>>> +layout: post
>>> +title:  "GSoC and Outreachy 2018 retrospective"
>>> +date:   2019-01-23 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.
>>> +
>>> +This project was mentored by Jim Mussared, Joel Stanley, and Stefan Hajnoczi.
>>> +
>>> +## 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 <a href="https://patchew.org/">patchew.org</a>.  They are not in
>>> +use yet, pending more work on authentication; this may be the topic of a future
>>> +Summer of Code internship.
>>> +
>>> +This project was mentored by Paolo Bonzini and Fam Zheng.
>>> +
>>> +## 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 <a
>>> +href="https://www.youtube.com/watch?v=N8Go4NEw0Ss">presented at KVM Forum 2019
>>
>> s/2019/2018
> 
> Thanks!
> 
> Thomas: Please s/KVM Forum 2019/KVM Forum 2018/ when merging.

Fixed and pushed:
https://www.qemu.org/2019/01/23/internships-wrapup/

 Thanks!
  Thomas




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2019-01-24  9:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23 16:53 [Qemu-devel] [qemu-web PATCH v2] Add GSoC/Outreachy 2018 retrospective blog post Stefan Hajnoczi
2019-01-23 17:55 ` Stefano Garzarella
2019-01-23 20:27   ` Stefan Hajnoczi
2019-01-24  9:30     ` Thomas Huth [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=eb8e14a4-20bf-31b1-9739-f2e763469c0e@redhat.com \
    --to=thuth@redhat.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=sgarzare@redhat.com \
    --cc=stefanha@gmail.com \
    --cc=stefanha@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).