From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: "Paul Burton" <pburton@wavecomp.com>,
"Chris Wulff" <crwulff@gmail.com>,
"Sagar Karandikar" <sagark@eecs.berkeley.edu>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Andrew Jeffery" <andrew@aj.id.au>,
"Anthony Green" <green@moxielogic.com>,
"Palmer Dabbelt" <palmer@sifive.com>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Max Filippov" <jcmvbkbc@gmail.com>,
"Alistair Francis" <Alistair.Francis@wdc.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
"Guan Xuetao" <gxt@mprc.pku.edu.cn>,
"Marek Vasut" <marex@denx.de>, "Rob Herring" <robh@kernel.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Jia Liu" <proljc@gmail.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Helge Deller" <deller@gmx.de>,
"David Hildenbrand" <david@redhat.com>,
"Magnus Damm" <magnus.damm@gmail.com>,
"Halil Pasic" <pasic@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Hervé Poussineau" <hpoussin@reactos.org>,
"Antony Pavlov" <antonynpavlov@gmail.com>,
"Anthony Perard" <anthony.perard@citrix.com>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Artyom Tarasenko" <atar4qemu@gmail.com>,
"Joel Stanley" <joel@jms.id.au>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Jean-Christophe Dubois" <jcd@tribudubois.net>,
"Alistair Francis" <alistair@alistair23.me>,
"Fabien Chouteau" <chouteau@adacore.com>,
"Beniamino Galvani" <b.galvani@gmail.com>,
"Paul Durrant" <paul.durrant@citrix.com>,
"Peter Chubb" <peter.chubb@nicta.com.au>,
"Cédric Le Goater" <clg@kaod.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Stafford Horne" <shorne@gmail.com>,
"Andrey Smirnov" <andrew.smirnov@gmail.com>,
"Richard Henderson" <rth@twiddle.net>,
"Igor Mitsyanko" <i.mitsyanko@gmail.com>,
"Bastian Koppelmann" <kbastian@mail.uni-paderborn.de>,
"Cornelia Huck" <cohuck@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Andrew Baumann" <Andrew.Baumann@microsoft.com>,
"Subbaraya Sundeep" <sundeep.lkml@gmail.com>,
"Aleksandar Rikalo" <arikalo@wavecomp.com>,
"Michael Walle" <michael@walle.cc>,
"Thomas Huth" <huth@tuxfamily.org>,
"Aleksandar Markovic" <amarkovic@wavecomp.com>,
"Jan Kiszka" <jan.kiszka@web.de>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] Maintainers, please tell us how to boot your machines!
Date: Thu, 16 May 2019 22:07:12 +0200 [thread overview]
Message-ID: <3c7c7980-bb0a-c6f5-1f7d-56054190bb25@redhat.com> (raw)
In-Reply-To: <87d0mwatbu.fsf@dusky.pond.sub.org>
Hi Markus,
On 3/12/19 6:36 PM, Markus Armbruster wrote:
> Dear board code maintainers,
>
> This is a (rather late) follow-up to the last QEMU summit. Minutes[*]:
>
> * Deprecating unmaintained features (devices, targets, backends) in QEMU
>
> QEMU has a mechanism to deprecate features but there remains a lot of
> old unmaintained code. Refactoring is hindered by untested legacy
> code, so there is a desire to deprecate unmaintained features more
> often.
>
> [...]
>
> We should require at least a minimal test for each board; if nobody
> cares enough to come up with one, that board should be deprecated.
>
> [...]
>
> Also see the qemu-devel discussion about deprecating code:
> https://lists.nongnu.org/archive/html/qemu-devel/2018-10/msg05828.html.
>
> That's a link to "Minutes of KVM Forum BoF on deprecating stuff".
> Quote:
>
> * One obvious class of candidates for removal is machines we don't know
> how to boot, or can't boot, say because we lack required firmware
> and/or OS.
>
> Of course, "can boot" should be an automated test. As a first step
> towards that, we should at least document how to boot each machine.
> We're going to ask machine maintainers to do that.
>
> Let's get going on this.
>
> I gathered the machine types, mapped them to source files, which I fed
> to get_maintainer.pl. Results are appended. If you're cc'ed,
> MAINTAINERS fingers you for at least one machine type's source file.
> Please tell us for all of them how to to a "meaningful" boot test.
>
> For now, what's "meaningful" is entirely up to you. Booting Linux
> certainly is.
>
> Make sure to include a complete QEMU command line. If your QEMU command
> line requires resources beyond the QEMU source tree and what we build
> from it, please detail them, and provide download URLs as far as
> possible.
>
> Goals for this exercise:
>
> * Gather information we need to cover more machines in our automated
> testing.
>
> Related work:
> [PATCH v4 00/19] Acceptance Tests: target architecture support
> Message-Id: <20190312121150.8638-1-crosa@redhat.com>
> https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg03881.html
>
> * Maybe identify a few machines we don't know how to boot anymore.
>
> Thanks in advance for your help!
How do you want to proceed with all the information provided in this
thread? I think a big table in the wiki collecting the answers is ideal.
What do you think?
Regards,
Phil.
next prev parent reply other threads:[~2019-05-16 20:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87d0mwatbu.fsf@dusky.pond.sub.org>
[not found] ` <CAAdtpL6VCiXLbTWyJo4cbCNLjOCPr6KrH8KTqEq1V=CTMYKubQ@mail.gmail.com>
2019-04-12 11:11 ` [Qemu-devel] Maintainers, please tell us how to boot your machines! Thomas Huth
2019-04-12 11:11 ` Thomas Huth
2019-04-12 11:28 ` Philippe Mathieu-Daudé
2019-04-12 11:28 ` Philippe Mathieu-Daudé
2019-04-12 12:12 ` Thomas Huth
2019-04-12 12:12 ` Thomas Huth
2019-04-12 14:42 ` Thomas Huth
2019-04-12 14:42 ` Thomas Huth
2019-04-18 8:16 ` sundeep subbaraya
2019-04-18 8:16 ` sundeep subbaraya
2019-04-16 2:24 ` Andrey Smirnov
2019-04-16 2:24 ` Andrey Smirnov
2019-04-16 9:13 ` KONRAD Frederic
2019-04-16 9:13 ` KONRAD Frederic
2019-05-16 20:07 ` Philippe Mathieu-Daudé [this message]
2019-05-17 17:42 ` Markus Armbruster
2019-12-22 12:03 ` Philippe Mathieu-Daudé
2020-01-13 12:52 ` Markus Armbruster
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=3c7c7980-bb0a-c6f5-1f7d-56054190bb25@redhat.com \
--to=philmd@redhat.com \
--cc=Alistair.Francis@wdc.com \
--cc=Andrew.Baumann@microsoft.com \
--cc=alistair@alistair23.me \
--cc=amarkovic@wavecomp.com \
--cc=andrew.smirnov@gmail.com \
--cc=andrew@aj.id.au \
--cc=anthony.perard@citrix.com \
--cc=antonynpavlov@gmail.com \
--cc=arikalo@wavecomp.com \
--cc=armbru@redhat.com \
--cc=atar4qemu@gmail.com \
--cc=aurelien@aurel32.net \
--cc=b.galvani@gmail.com \
--cc=borntraeger@de.ibm.com \
--cc=chouteau@adacore.com \
--cc=clg@kaod.org \
--cc=cohuck@redhat.com \
--cc=crwulff@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=david@redhat.com \
--cc=deller@gmx.de \
--cc=edgar.iglesias@gmail.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=green@moxielogic.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=hpoussin@reactos.org \
--cc=huth@tuxfamily.org \
--cc=i.mitsyanko@gmail.com \
--cc=jan.kiszka@web.de \
--cc=jcd@tribudubois.net \
--cc=jcmvbkbc@gmail.com \
--cc=joel@jms.id.au \
--cc=kbastian@mail.uni-paderborn.de \
--cc=magnus.damm@gmail.com \
--cc=marex@denx.de \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=michael@walle.cc \
--cc=mst@redhat.com \
--cc=palmer@sifive.com \
--cc=pasic@linux.ibm.com \
--cc=paul.durrant@citrix.com \
--cc=pbonzini@redhat.com \
--cc=pburton@wavecomp.com \
--cc=peter.chubb@nicta.com.au \
--cc=peter.maydell@linaro.org \
--cc=proljc@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=robh@kernel.org \
--cc=rth@twiddle.net \
--cc=sagark@eecs.berkeley.edu \
--cc=shorne@gmail.com \
--cc=sstabellini@kernel.org \
--cc=sundeep.lkml@gmail.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).