From: Avi Kivity <avi@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
Takashi Iwai <tiwai@suse.de>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1.0] ac97: don't override the pci subsystem id
Date: Mon, 07 Nov 2011 17:15:54 +0200 [thread overview]
Message-ID: <4EB7F62A.4030305@redhat.com> (raw)
In-Reply-To: <4EB7F4C8.4080004@redhat.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Takashi Iwai <tiwai@suse.de>, kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1.0] ac97: don't override the pci subsystem id
Date: Mon, 07 Nov 2011 17:15:54 +0200 [thread overview]
Message-ID: <4EB7F62A.4030305@redhat.com> (raw)
In-Reply-To: <4EB7F4C8.4080004@redhat.com>
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
next prev parent reply other threads:[~2011-11-07 15:16 UTC|newest]
Thread overview: 21+ 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 11:00 ` [Qemu-devel] " Gerd Hoffmann
2011-11-07 14:17 ` Avi Kivity
2011-11-07 14:17 ` [Qemu-devel] " Avi Kivity
2011-11-07 14:33 ` Gerd Hoffmann
2011-11-07 14:33 ` [Qemu-devel] " Gerd Hoffmann
2011-11-07 14:39 ` Anthony Liguori
2011-11-07 14:39 ` Anthony Liguori
2011-11-07 14:42 ` Avi Kivity
2011-11-07 14:42 ` [Qemu-devel] " Avi Kivity
2011-11-07 14:44 ` Anthony Liguori
2011-11-07 14:44 ` Anthony Liguori
2011-11-07 14:50 ` Avi Kivity
2011-11-07 14:50 ` Avi Kivity
2011-11-07 14:53 ` Anthony Liguori
2011-11-07 15:00 ` Avi Kivity
2011-11-07 15:00 ` [Qemu-devel] " Avi Kivity
2011-11-07 15:10 ` Gerd Hoffmann
2011-11-07 15:10 ` Gerd Hoffmann
2011-11-07 15:15 ` Avi Kivity [this message]
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=4EB7F62A.4030305@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.