qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
Cc: Thomas Huth <thuth@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Guan Xuetao <gxt@mprc.pku.edu.cn>,
	Chen Gang <chengang@emindsoft.com.cn>,
	Chen Gang <gang.chen.5i5j@gmail.com>,
	Chen Gang <xili_gchen_5257@hotmail.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] Deprecate tilegx ?
Date: Fri, 09 Mar 2018 15:13:16 +0000	[thread overview]
Message-ID: <87y3j1jn8z.fsf@linaro.org> (raw)
In-Reply-To: <c7b075f5-8084-99c0-02e0-3da555bea4df@mail.uni-paderborn.de>


Bastian Koppelmann <kbastian@mail.uni-paderborn.de> writes:

> On 02/28/2018 07:11 AM, Thomas Huth wrote:
>> On 27.02.2018 12:51, Peter Maydell wrote:
>>> I propose that we deprecate and plan to remove the unicore32 code:
>> [...]
> [...]
>>
>> Sounds reasonable to me, but let's wait a week or two for feedback from
>> Guan Xuetao.
>
> Agreed.
>
>>
>>> Possibly there are other target architectures we could reasonably
>>> deprecate-and-remove (though none of the other ones Linux is dropping
>>> in this round are ones we support)...
>>
>> I'd vote for marking tilegx as deprecated, too, since we even do not
>> have an active maintainer for that CPU core (at least I did not spot one
>> in our MAINTAINERS file). Opinions?
>
> I always saw it as a big plus that QEMU supports nearly any
> architecture, no matter how obscure it is. So I'm a bit more hesitant on
> dropping architectures quickly.

All things being equal I agree, however there is a maintenance burden
for the QEMU upstream, especially if the only active use if on
out-of-tree branches or behind the closed doors of research groups.

Looking at https://wiki.qemu.org/Documentation/Platforms/TileGX it
doesn't give much of an idea of where I would get toolchains to build
guest binaries or what guest user-space I could run.

--
Alex Bennée

  reply	other threads:[~2018-03-09 15:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 11:51 [Qemu-devel] Proposal: deprecate and remove QEMU's unicore32 target code Peter Maydell
2018-02-27 11:56 ` Daniel P. Berrangé
2018-02-28  6:11 ` [Qemu-devel] Deprecate tilegx ? (was: Proposal: deprecate and remove QEMU's unicore32 target code) Thomas Huth
2018-02-28  7:17   ` [Qemu-devel] Deprecate tilegx ? Paolo Bonzini
2018-02-28 10:38     ` Thomas Huth
2018-02-28 12:41   ` Bastian Koppelmann
2018-03-09 15:13     ` Alex Bennée [this message]
2018-03-13 17:18       ` Bastian Koppelmann
2018-03-13 17:39         ` Peter Maydell
2018-03-14  9:09           ` Xuetao Guan
2018-03-14 10:11             ` Laurent Vivier
2018-03-14 12:01               ` Xuetao Guan
2018-03-17  8:06       ` Waldemar Brodkorb
2018-03-13 16:37     ` Chen Gang
2018-03-09 14:08 ` [Qemu-devel] Proposal: deprecate and remove QEMU's unicore32 target code Xuetao Guan

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=87y3j1jn8z.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=chengang@emindsoft.com.cn \
    --cc=gang.chen.5i5j@gmail.com \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=kbastian@mail.uni-paderborn.de \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=thuth@redhat.com \
    --cc=xili_gchen_5257@hotmail.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).