[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] What's the next QEMU version after 2.9 ? (or: when is a

From: Yongbok Kim
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: Thu, 9 Mar 2017 10:20:09 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1

On 09/03/2017 09:53, Jason Wang wrote:
> On 2017年03月09日 16:50, Thomas Huth wrote:
>> On 09.03.2017 03:21, Jason Wang wrote:
>>> On 2017年03月08日 19:22, Thomas Huth wrote:
>>>> On 08.03.2017 11:03, Peter Maydell wrote:
>>>>> On 8 March 2017 at 09:26, Thomas Huth <address@hidden> wrote:
>>>>>> But anyway, the more important thing that keeps me concerned is:
>>>>>> Someone
>>>>>>    once told me that we should get rid of old parameters and interfaces
>>>>>> (like HMP commands) primarily only when we're changing to a new major
>>>>>> version number. As you all know, QEMU has a lot of legacy options,
>>>>>> which
>>>>>> are likely rather confusing than helpful for the new users nowadays,
>>>>>> e.g. things like the "-net channel" option (which is fortunately even
>>>>>> hardly documented), but maybe also even the whole vlan/hub concept in
>>>>>> the net code, or legacy parameters like "-usbdevice". If we switch to
>>>>>> version 3.0, could we agree to remove at least some of them?
>>>>> I think if we are going to deprecate and remove options we need
>>>>> a clear transition plan for doing so, which means at least one
>>>>> release where options are "still works, but warn that they
>>>>> are going away with pointer to documentation or similar info
>>>>> about their replacement syntax", before actually dropping them.
>>>> Yes, that's certainly a good idea. But as Daniel suggested in his mail,
>>>> I think we should also have the rule that the option should be marked as
>>>> deprecated in multiple releases first - so that the users have a chance
>>>> to speak up before something gets really removed (otherwise the option
>>>> could be removed right on the first day after the initial release with
>>>> the deprecation message, so there is no time for the user to notice this
>>>> and complain). Not sure whether we need three releases, as Daniel
>>>> suggested, though, but if that's common sense, that's fine for me, too.
>>>> Anyway, I've now started a Wiki page where we could track the removal of
>>>> deprecated interfaces:
>>>>    http://wiki.qemu-project.org/Features/LegacyRemoval
>>>> Feedback / updates / addition of other legacy interfaces is welcome!
>>>>    Thomas
>>> I think we may want to add mipsnet to the list too. It's kernel driver
>>> was removed about 3 years ago.
>> But that's still the default network of the "mipssim" machine ...
>> is that machine considered as deprecated, too?
>>   Thomas
> I think so, according to [1], it was deprecated.
> [1] https://www.linux-mips.org/wiki/MIPSsim
> Thanks

Indeed but we still use the platform to verify architectural
compatibilities even for newer MIPS architectures.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]