From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Takashi Iwai <tiwai@suse.de>, Gerd Hoffmann <kraxel@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 1.0] ac97: don't override the pci subsystem id
Date: Mon, 07 Nov 2011 17:00:21 +0200 [thread overview]
Message-ID: <4EB7F285.9080009@redhat.com> (raw)
In-Reply-To: <4EB7F0D8.2060306@codemonkey.ws>
On 11/07/2011 04:53 PM, Anthony Liguori wrote:
>> I think so, but that's unrelated. The worry is that some DRM code
>> checksums your hardware and complains if it changed too much. Nothing
>> to do with the test suite.
>>
>> The sense of Gerd's comment is reversed. We should preserve the ABI
>> unless there is a strong reason not to.
>
>
> Yes, I understand where you're coming from and I agree except when it
> comes to bug fixes.
>
> My view toward bug fixes is the opposite--unless we know that the bug
> fix breaks something, we should fix the bug. If it's a bug, we have to
> assume it's breaking something.
You're right in that not every bug fix deserves an entry in our quirk
table. We don't want -M pc-0.15 to reintroduce a data corrupting bug
just because it is guest visible!
This is more of an edge case however, since we know that hardware tools
rely on PCI IDs. For example our hypothetical ABI signature tool will
certainly include lspci like functionality and detect this as a change.
I now agree with both sides of the argument and can continue the
discussion unaided for at least 30-40 emails.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-11-07 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 11:00 [PATCH 1.0] ac97: don't override the pci subsystem id Gerd Hoffmann
2011-11-07 14:17 ` Avi Kivity
2011-11-07 14:33 ` Gerd Hoffmann
2011-11-07 14:39 ` [Qemu-devel] " Anthony Liguori
2011-11-07 14:42 ` Avi Kivity
2011-11-07 14:44 ` [Qemu-devel] " Anthony Liguori
2011-11-07 14:50 ` Avi Kivity
2011-11-07 14:53 ` Anthony Liguori
2011-11-07 15:00 ` Avi Kivity [this message]
2011-11-07 15:10 ` Gerd Hoffmann
2011-11-07 15:15 ` Avi Kivity
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=4EB7F285.9080009@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=tiwai@suse.de \
/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