From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:55137)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1RNQvZ-0006nr-F2
	for qemu-devel@nongnu.org; Mon, 07 Nov 2011 10:16:06 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1RNQvX-0004ww-Tc
	for qemu-devel@nongnu.org; Mon, 07 Nov 2011 10:16:01 -0500
Received: from mx1.redhat.com ([209.132.183.28]:40906)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1RNQvX-0004wr-Jl
	for qemu-devel@nongnu.org; Mon, 07 Nov 2011 10:15:59 -0500
Message-ID: <4EB7F62A.4030305@redhat.com>
Date: Mon, 07 Nov 2011 17:15:54 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <1320663634-29453-1-git-send-email-kraxel@redhat.com>	<4EB7E896.9010108@redhat.com>	<4EB7EC4A.90607@redhat.com>
	<4EB7EE62.7070805@redhat.com>	<4EB7EEDD.4090604@codemonkey.ws>
	<4EB7F027.10209@redhat.com> <4EB7F0D8.2060306@codemonkey.ws>
	<4EB7F285.9080009@redhat.com> <4EB7F4C8.4080004@redhat.com>
In-Reply-To: <4EB7F4C8.4080004@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH 1.0] ac97: don't override the pci subsystem
 id
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Takashi Iwai <tiwai@suse.de>, kvm@vger.kernel.org, qemu-devel@nongnu.org

On 11/07/2011 05:10 PM, Gerd Hoffmann wrote:
>   Hi,
>
> > This is more of an edge case however, since we know that hardware tools
> > rely on PCI IDs.
>
> The ID is invalid, you can't do anything useful with it ...
>
> > For example our hypothetical ABI signature tool will
> > certainly include lspci like functionality and detect this as a change.
>
> ... except maybe recording it somewhere to notice when changes.
>
> So I guess your point is Windows guests might think they got a new sound
> card, record that has hardware change and may require re-activation
> because of that?

Yes.  Or some hardware inventory tool we know nothing about, which was
constructed specifically in order to make our lives miserable.

-- 
error compiling committee.c: too many arguments to function