All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Cc: Chen Gang <chengang@emindsoft.com.cn>,
	Chen Gang <gang.chen.5i5j@gmail.com>,
	Anthony Green <green@moxielogic.com>,
	Guan Xuetao <gxt@mprc.pku.edu.cn>,
	Chen Gang <xili_gchen_5257@hotmail.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] Deprecate tilegx ?
Date: Wed, 28 Feb 2018 11:38:40 +0100	[thread overview]
Message-ID: <d7fad9ae-95f0-077e-313f-161c6a243a07@redhat.com> (raw)
In-Reply-To: <8c93c12e-f794-d0ea-c393-55131ba4ad25@redhat.com>

On 28.02.2018 08:17, Paolo Bonzini wrote:
> On 28/02/2018 07:11, Thomas Huth wrote:
>> On 27.02.2018 12:51, Peter Maydell wrote:
>>> I propose that we deprecate and plan to remove the unicore32 code:
>> [...]
>>> Essentially, it seems to be a largely-inactive university R&D project,
>>> it's costing us in maintenance effort every time we have to touch it,
>>> and I don't think it has any real users.
>>>
>>> Does anybody disagree?
>>>
>>> If we go ahead with deprecating then we should:
>>>  * add a note to Changelog that we're deprecating the target
>>>  * ditto qemu-doc.texi's deprecation section
>>>  * patch hw/unicore32/puv3.c to warn on startup that it's deprecated
>>>  * remove it entirely for the 2.14 release
>>>
>>> We could also remove linux-user/unicore32 immediately, since
>>> the linux-user target has been disabled for some time.
>>
>> Sounds reasonable to me, but let's wait a week or two for feedback from
>> Guan Xuetao.
> 
> Sounds good---thought I would consider dropping unicore32 now with no
> formal deprecation period...
> 
>>> 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?
> 
> Tilegx has been last modified in 2015, so it's a little more alive than
> unicore32.
> 
> Another one is moxie.  Anthony?

For moxie, we've got at least a maintainer in MAINTAINERS, and there is
still a proper project page online
(http://moxielogic.org/blog/pages/architecture.html). And since we've
now also got a mini Moxie TCG test in tests/boot-serial-test.c, the CPU
code is at least still basically working fine. So IMHO there's no urgent
need to mark the moxie CPU as deprecated yet.

 Thomas

  reply	other threads:[~2018-02-28 10:39 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 [this message]
2018-02-28 12:41   ` Bastian Koppelmann
2018-03-09 15:13     ` Alex Bennée
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=d7fad9ae-95f0-077e-313f-161c6a243a07@redhat.com \
    --to=thuth@redhat.com \
    --cc=chengang@emindsoft.com.cn \
    --cc=gang.chen.5i5j@gmail.com \
    --cc=green@moxielogic.com \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.