From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Michael Walle" <michael@walle.cc>,
"Daniel P. Berrange" <berrange@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] Deprecate lm32 port
Date: Thu, 27 Aug 2020 16:50:25 +0200 [thread overview]
Message-ID: <0fd6bf04-f021-6716-c010-93def04c6f5d@redhat.com> (raw)
In-Reply-To: <CAFEAcA_3fiQ86aby8PALZNUukPE1RhgV+1+hjoEF+aCfCp3mbw@mail.gmail.com>
On 27/08/2020 16.19, Peter Maydell wrote:
> On Thu, 27 Aug 2020 at 14:52, Thomas Huth <thuth@redhat.com> wrote:
>> What's next? moxie? ... apart from the tree-wide clean-ups and trivial
>> fixes, moxie did not have any major updates since 2013 when it has been
>> added, as far as I can see ... is anybody still using it?
>
> I was never very clear on how much use moxie had to start with...
>
> An extremely rough-and-ready guide to how well-loved a target
> is might be "did it get converted to TranslatorOps?". Unconverted:
> * avr
> * cris
> * lm32 (deprecation in progress)
> * microblaze (rth just posted patches for this)
> * moxie
> * nios2
> * tilegx (deprecation in progress)
> * unicore32 (deprecation in progress)
Another criteria might be: Do we have a tcg, qtest or acceptance test to
check that the target is still working?
- avr has an acceptance test
- cris has tcg tests
- lm32 has tcg tests
- microblaze has acceptance tests (and one trivial qtest)
- moxie ... has only one very trivial qtest (boot-serial-test)
- nios2 has an acceptance test
- tilegx does not have any tests at all
- unicore32 does not have any tests at all
(not counting the trivial machine-none-test)
So from that point of view, unicore32, tilegx and moxie are the
candidates for deprecation.
> I think dropping the moxie maintainer an email to ask about
> the architecture's status wouldn't be a bad idea if you
> wanted to start that ball rolling.
Ok, good idea, I'll try to write a mail later today.
Thomas
next prev parent reply other threads:[~2020-08-27 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 11:32 [PATCH] Deprecate lm32 port Peter Maydell
2020-08-27 11:36 ` Daniel P. Berrangé
2020-08-27 12:02 ` Michael Walle
2020-08-31 20:08 ` Philippe Mathieu-Daudé
2020-08-27 13:52 ` Thomas Huth
2020-08-27 14:19 ` Peter Maydell
2020-08-27 14:50 ` Thomas Huth [this message]
2020-08-31 20:11 ` Philippe Mathieu-Daudé
2020-09-23 7:55 ` Thomas Huth
2020-09-23 9:47 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2020-10-12 15:33 [PATCH 00/10] target/arm: Various v8.1M minor features Peter Maydell
2020-10-12 15:33 ` [PATCH] Deprecate lm32 port Peter Maydell
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=0fd6bf04-f021-6716-c010-93def04c6f5d@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=michael@walle.cc \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).