qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	QEMU Developers <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Michael Walle <michael@walle.cc>
Subject: Re: Deprecation of the LM32 target
Date: Tue, 29 Dec 2020 11:38:13 +0100	[thread overview]
Message-ID: <559bbdfa-3876-ab22-445f-4bb59d9b4979@redhat.com> (raw)
In-Reply-To: <d8bbe81c-3446-8d83-3f34-f29156cf4f01@physik.fu-berlin.de>

On 26/12/2020 10.06, John Paul Adrian Glaubitz wrote:
> Hello!
> 
> On 12/26/20 9:39 AM, Thomas Huth wrote:
>> the problem is not that the target CPU is old, but rather that according to the (former?) maintainer, there are no users left:
>>
>>   https://www.mail-archive.com/qemu-devel@nongnu.org/msg605024.html
>>
>> So it got marked as deprecated in this commit here:
>>
>>   https://git.qemu.org/?p=qemu.git;a=commitdiff;h=d84980051229fa43c96b3
>>
>> Without maintainer and without users, there is no point in keeping this target, is there?
> 
> I'm not sure how you determine whether there are people using the code or not. There
> is no really user tracking in QEMU, is there?
> 
> And the maintainer's claim that RISC-V takes over makes no sense either. The point of
> emulators is to be able to run old and existing software. If a target had only a
> justification to exist while it's commercially viable, you would have to remove 90%
> of the targets in QEMU.
> 
> I mean, the whole point of an emulator is being able to run existing code on modern hardware,
> usually because the old hardware is no longer available. And as long as the target is
> functional, I don't see a point in taking away the functionality.

You also have to consider that it takes some effort to keep code up to date, 
e.g. if there is a bigger restructuring of the code base going on, you also 
have to work on neglected targets, too. If there is no active maintainer 
left anymore, it's quite a burden for all the other developers.
So if there is no known user left (are *you* using lm32?), and there is no 
active maintainer anymore, it's IMHO adequate to mark a target as 
deprecated. If someone still wants to run old lm32 code, they still can use 
older versions of QEMU to do this.

  Thomas




  parent reply	other threads:[~2020-12-29 10:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24  9:53 Deprecation of the LM32 target John Paul Adrian Glaubitz
2020-12-26  8:39 ` Thomas Huth
2020-12-26  9:06   ` John Paul Adrian Glaubitz
2020-12-26 11:50     ` Michael Walle
2020-12-29 10:38     ` Thomas Huth [this message]
2020-12-30 16:34       ` 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=559bbdfa-3876-ab22-445f-4bb59d9b4979@redhat.com \
    --to=thuth@redhat.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=michael@walle.cc \
    --cc=peter.maydell@linaro.org \
    --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).