From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, qemu-block@nongnu.org,
"Michael S . Tsirkin" <mst@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 6/6] hw/i386/i386: Stop auto-creating lsi53c895a SCSI HBAs
Date: Tue, 24 Jan 2017 12:17:40 +0100 [thread overview]
Message-ID: <3512807d-d04e-50fa-9fcf-d1d5ba8ac350@redhat.com> (raw)
In-Reply-To: <877f5l1tak.fsf@dusky.pond.sub.org>
On 23/01/2017 20:16, Markus Armbruster wrote:
>> Could we change
>> those messages to errors
>
> Fine with me, but when it comes to arguing for backward compatibility of
> our byzantine command line, I'm kind of like a lethargic public defender
> with an overly deep relationship to Bourbon. "Your honor, sure capital
> punishment is called for? Yes? Okay then."
>
> I vaguely recall discussing the topic with Peter (cc'ed). If memory
> serves, one concern was breaking usage of -device with -drive lacking
> if=... Works fine (no warning) with machines that don't pick up drives
> with their default block interface type, i.e. most of them. But PATCH 3
> changes their default to if=none, so that usage wouldn't actually break.
I think that tips the scale in favor of having errors.
> What would break is -device with -drive if=T, where T is not none and
> not picked up by the board. Such usage is certainly questionable[*],
> but it's questionable enough for us to break it?
>
>> and then drop PC if=scsi support altogether?
>
> Different backward compatibility question: here we break usage of
> if=scsi with PC machine types. Legacy way to do things, but it's
> documented in qemu.1. Are we happy to break it?
That usage is wrong after this patch, since it mentions
qemu-system-i386. So it's documented, but almost useless and the
example is not exactly correct. Let's deprecate it in 2.9 and remove in
2.10.
Paolo
next prev parent reply other threads:[~2017-01-24 11:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 9:48 [Qemu-devel] [PATCH 0/6] More sensible default for -drive interface type Markus Armbruster
2017-01-23 9:48 ` [Qemu-devel] [PATCH 1/6] hw: Default -drive to if=ide explicitly where it works Markus Armbruster
2017-01-23 9:48 ` [Qemu-devel] [PATCH 2/6] hw/arm/cubieboard hw/arm/xlnx-ep108: Fix units_per_default_bus Markus Armbruster
2017-01-23 9:48 ` [Qemu-devel] [PATCH 3/6] hw: Default -drive to if=none instead of ide when ide cannot work Markus Armbruster
2017-01-23 12:24 ` Artyom Tarasenko
2017-01-23 9:48 ` [Qemu-devel] [PATCH 4/6] hw: Default -drive to if=none instead of scsi when scsi " Markus Armbruster
2017-01-23 9:48 ` [Qemu-devel] [PATCH 5/6] hw/arm/highbank: Default -drive to if=ide instead of if=scsi Markus Armbruster
2017-01-23 9:48 ` [Qemu-devel] [PATCH 6/6] hw/i386/i386: Stop auto-creating lsi53c895a SCSI HBAs Markus Armbruster
2017-01-23 16:48 ` Paolo Bonzini
2017-01-23 19:16 ` Markus Armbruster
2017-01-24 11:17 ` Paolo Bonzini [this message]
2017-01-24 12:56 ` Markus Armbruster
2017-01-24 13:01 ` Paolo Bonzini
2017-01-24 17:20 ` Markus Armbruster
2017-01-24 17:24 ` Peter Maydell
2017-01-24 17:40 ` Paolo Bonzini
2017-01-24 17:58 ` Peter Maydell
2017-01-24 18:43 ` Markus Armbruster
2017-01-25 16:45 ` Markus Armbruster
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=3512807d-d04e-50fa-9fcf-d1d5ba8ac350@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.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).