Re: [Qemu-devel] What's the next QEMU version after 2.9 ? (or: when is a good point in time to get rid of old interfaces)

From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	Jason Wang <jasowang@redhat.com>
Cc: Yongbok Kim <yongbok.kim@imgtec.com>,
	Aurelien Jarno <aurelien@aurel32.net>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] What's the next QEMU version after 2.9 ? (or: when is a good point in time to get rid of old interfaces)
Date: Fri, 10 Mar 2017 12:53:03 +0100	[thread overview]
Message-ID: <24f60ae4-9a6b-eaa6-7300-1e908eff8a24@redhat.com> (raw)
In-Reply-To: <CAFEAcA9x1c74MBetKxxwQSNWhC=C8JV80QCBiEuY3pLteY=UVA@mail.gmail.com>

On 10.03.2017 12:22, Peter Maydell wrote:
> On 10 March 2017 at 12:07, Jason Wang <jasowang@redhat.com> wrote:
>> On 2017年03月09日 18:20, Yongbok Kim wrote:
>>> Indeed but we still use the platform to verify architectural
>>> compatibilities even for newer MIPS architectures.
> 
>> I see, but I believe it may need some modifications in the code to support
>> newer architectures? If yes, plan to send them upstream? Since it has been
>> deprecated, if no new codes it makes sense to deprecate it in qemu too. You
>> can still use exist qemu versions to do the verification.
> 
> Taking a step back, the reason for deprecating and deleting
> code is to avoid having unmaintained and unused code in QEMU.
> If Yongbok is maintaining the mipssim board and devices
> and is willing to keep them up to spec with current QOM
> and other best practices, and there are test images to
> check they still work, I think that's fine.

But the Mipssim machine is currently marked as "Orphan" in our
MAINTAINERS file ... Yongbok, if you're still using it, would you maybe
be interested in doing at least "Odd fixes" here?
BTW, I think "F: hw/net/mipsnet.c" should be added to the "Mipssim"
section, too.

 Thomas