From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] net: Inform the user about deprecated -net options
Date: Tue, 15 Dec 2015 19:08:17 +0100 [thread overview]
Message-ID: <56705711.1000702@redhat.com> (raw)
In-Reply-To: <567052E7.3000903@redhat.com>
On 15/12/2015 18:50, Thomas Huth wrote:
> On 15/12/15 18:31, Paolo Bonzini wrote:
>>
>> On 15/12/2015 18:15, Thomas Huth wrote:
>>> On 15/12/15 17:21, Paolo Bonzini wrote:
> [...]
>>>> For example you could print all DEVICE_CATEGORY_NETWORK devices that
>>>> support device_add.
>>>
>>> I think that would not work since spapr-vlan is not hot-pluggable.
>>
>> cannot_instantiate_with_device_add_yet which actually refers to -device,
>> not really device_add, so it would work.
>
> I just tried:
>
> (qemu) device_add spapr-vlan
> Bus 'spapr-vio' does not support hotplugging
>
> ... did I miss something?
When I said "support device_add" I really meant "does not have
cannot_instantiate_with_device_add_yet", but spapr-vlan should pass that
test.
>>>> The thing is, people are still running QEMU from the command line.
>>>>
>>>> "-net nic -net bridge,br=virbr0" is still much less of a mouthful than
>>>> "-netdev bridge,br=virbr0,id=br -device rtl8139,netdev=br" if all I want
>>>> is something I can ssh into.
>>>>
>>>> It's easy to deprecate things. It's hard to convince users that it's
>>>> worth, and you haven't convinced this user. :)
>>>
>>> Ok, if you want to maintain that legacy stuff forever - fine.
>>
>> I don't want to, but I think we have to. It would be a good idea to get
>> rid of it, but unfortunately it's not a feasible idea IMHO.
>
> If the code gets unmaintainable because there is too much legacy cruft
> in it, that's IMHO even worse. At one point in time, you just have to
> get rid of such stuff ... but well, maybe the time for the "-net" option
> just has not come yet.
Yes, indeed. I don't think it's unmaintainable. It used to be much
worse, and it could be improved.
Paolo
next prev parent reply other threads:[~2015-12-15 18:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 11:46 [Qemu-devel] [PATCH] net: Inform the user about deprecated -net options Thomas Huth
2015-12-15 12:51 ` Paolo Bonzini
2015-12-15 16:01 ` Thomas Huth
2015-12-15 16:21 ` Paolo Bonzini
2015-12-15 16:46 ` Eric Blake
2015-12-15 17:15 ` Thomas Huth
2015-12-15 17:31 ` Paolo Bonzini
2015-12-15 17:50 ` Thomas Huth
2015-12-15 18:08 ` Paolo Bonzini [this message]
2015-12-16 7:20 ` Thomas Huth
2015-12-16 8:50 ` Paolo Bonzini
2015-12-15 16:17 ` Peter Maydell
2015-12-15 16:33 ` Thomas Huth
2015-12-15 16:46 ` 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=56705711.1000702@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).