From: Anthony Liguori <anthony@codemonkey.ws>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-trivial@nongnu.org, Rusty Russell <rusty@rustcorp.com.au>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] Remove PCI class code from virtio balloon device
Date: Wed, 21 Mar 2012 10:14:35 -0500 [thread overview]
Message-ID: <4F69F05B.5010500@codemonkey.ws> (raw)
In-Reply-To: <20120321151043.GA22707@redhat.com>
On 03/21/2012 10:10 AM, Michael S. Tsirkin wrote:
> On Wed, Mar 21, 2012 at 09:42:41AM -0500, Anthony Liguori wrote:
>> On 03/21/2012 08:08 AM, Michael S. Tsirkin wrote:
>>> On Wed, Mar 21, 2012 at 11:26:15AM +0000, Stefan Hajnoczi wrote:
>>>> On Tue, Mar 20, 2012 at 09:19:47PM +1100, David Gibson wrote:
>>>> Looking at hw/pc_piix.c there are QEMUMachine types for each QEMU
>>>> release. Legacy machine types (e.g. pc_machine_v0_14) have a
>>>> .compat_props array that can override qdev properties.
>>>>
>>>> Perhaps Michael Tsirkin or someone else can comment on how to wire up
>>>> hw/virtio-pci.c so that the class code can be overridden.
>>>>
>>>> Stefan
>>>
>>> afaik we already let users over-write it for some other pci devices,
>>> look there for examples.
>>
>> From hw/pc_piix.c:
>>
>> .name = "pc-0.10",
>> .desc = "Standard PC, qemu 0.10",
>> .init = pc_init_pci_no_kvmclock,
>> .max_cpus = 255,
>> .compat_props = (GlobalProperty[]) {
>> {
>> .driver = "virtio-blk-pci",
>> .property = "class",
>> .value = stringify(PCI_CLASS_STORAGE_OTHER),
>> },{
>>
>> And from the earlier part of the thread, yes, it's imperative that
>> we do not change anything in the PCI configuration space for older
>> pc versions regardless of whether it may or may not work.
>>
>> Certain guests (like Windows) use a complex fingerprinting algorithm
>> to determine when hardware changes. It can be hard to detect in
>> simple testing because it's based on a threshold.
>>
>> Regards,
>>
>> Anthony Liguori
>
> Which reminds me - qemu sticks the release version in
> guest visible places like CPU version.
> This is wrong and causes windows guests to print messages
> about driver updates when you switch.
> We should find all these places and stop doing this.
We could probably get away with doing a query/replace of QEMU_VERSION with
qemu_get_version(), make version a static variable that defaults to
QEMU_VERSION, and then provide a way for machines to override it.
Then pc-0.10 could report a version of 0.10.
Regards,
Anthony Liguori
>>>
>>>
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-trivial@nongnu.org, Stefan Hajnoczi <stefanha@gmail.com>,
Rusty Russell <rusty@rustcorp.com.au>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Remove PCI class code from virtio balloon device
Date: Wed, 21 Mar 2012 10:14:35 -0500 [thread overview]
Message-ID: <4F69F05B.5010500@codemonkey.ws> (raw)
In-Reply-To: <20120321151043.GA22707@redhat.com>
On 03/21/2012 10:10 AM, Michael S. Tsirkin wrote:
> On Wed, Mar 21, 2012 at 09:42:41AM -0500, Anthony Liguori wrote:
>> On 03/21/2012 08:08 AM, Michael S. Tsirkin wrote:
>>> On Wed, Mar 21, 2012 at 11:26:15AM +0000, Stefan Hajnoczi wrote:
>>>> On Tue, Mar 20, 2012 at 09:19:47PM +1100, David Gibson wrote:
>>>> Looking at hw/pc_piix.c there are QEMUMachine types for each QEMU
>>>> release. Legacy machine types (e.g. pc_machine_v0_14) have a
>>>> .compat_props array that can override qdev properties.
>>>>
>>>> Perhaps Michael Tsirkin or someone else can comment on how to wire up
>>>> hw/virtio-pci.c so that the class code can be overridden.
>>>>
>>>> Stefan
>>>
>>> afaik we already let users over-write it for some other pci devices,
>>> look there for examples.
>>
>> From hw/pc_piix.c:
>>
>> .name = "pc-0.10",
>> .desc = "Standard PC, qemu 0.10",
>> .init = pc_init_pci_no_kvmclock,
>> .max_cpus = 255,
>> .compat_props = (GlobalProperty[]) {
>> {
>> .driver = "virtio-blk-pci",
>> .property = "class",
>> .value = stringify(PCI_CLASS_STORAGE_OTHER),
>> },{
>>
>> And from the earlier part of the thread, yes, it's imperative that
>> we do not change anything in the PCI configuration space for older
>> pc versions regardless of whether it may or may not work.
>>
>> Certain guests (like Windows) use a complex fingerprinting algorithm
>> to determine when hardware changes. It can be hard to detect in
>> simple testing because it's based on a threshold.
>>
>> Regards,
>>
>> Anthony Liguori
>
> Which reminds me - qemu sticks the release version in
> guest visible places like CPU version.
> This is wrong and causes windows guests to print messages
> about driver updates when you switch.
> We should find all these places and stop doing this.
We could probably get away with doing a query/replace of QEMU_VERSION with
qemu_get_version(), make version a static variable that defaults to
QEMU_VERSION, and then provide a way for machines to override it.
Then pc-0.10 could report a version of 0.10.
Regards,
Anthony Liguori
>>>
>>>
next prev parent reply other threads:[~2012-03-21 15:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 4:59 [Qemu-trivial] [PATCH] Remove PCI class code from virtio balloon device David Gibson
2012-03-19 4:59 ` [Qemu-devel] " David Gibson
2012-03-19 11:33 ` [Qemu-trivial] " Stefan Hajnoczi
2012-03-19 11:33 ` Stefan Hajnoczi
2012-03-20 0:42 ` [Qemu-trivial] " David Gibson
2012-03-20 0:42 ` David Gibson
2012-03-20 9:54 ` [Qemu-trivial] " Stefan Hajnoczi
2012-03-20 9:54 ` Stefan Hajnoczi
2012-03-20 10:19 ` [Qemu-trivial] " David Gibson
2012-03-20 10:19 ` David Gibson
2012-03-21 11:26 ` [Qemu-trivial] " Stefan Hajnoczi
2012-03-21 11:26 ` Stefan Hajnoczi
2012-03-21 11:28 ` [Qemu-trivial] " Stefan Hajnoczi
2012-03-21 11:28 ` Stefan Hajnoczi
2012-03-21 13:24 ` [Qemu-trivial] " David Gibson
2012-03-21 13:24 ` David Gibson
2012-03-21 13:08 ` [Qemu-trivial] " Michael S. Tsirkin
2012-03-21 13:08 ` Michael S. Tsirkin
2012-03-21 14:42 ` [Qemu-trivial] " Anthony Liguori
2012-03-21 14:42 ` Anthony Liguori
2012-03-21 15:10 ` [Qemu-trivial] " Michael S. Tsirkin
2012-03-21 15:10 ` Michael S. Tsirkin
2012-03-21 15:14 ` Anthony Liguori [this message]
2012-03-21 15:14 ` Anthony Liguori
2012-03-21 16:11 ` [Qemu-trivial] " Michael S. Tsirkin
2012-03-21 16:11 ` Michael S. Tsirkin
2012-03-21 16:26 ` [Qemu-trivial] " Anthony Liguori
2012-03-21 16:26 ` Anthony Liguori
2012-03-21 16:33 ` [Qemu-trivial] " Anthony Liguori
2012-03-21 16:33 ` Anthony Liguori
2012-03-21 18:28 ` [Qemu-trivial] " Michael S. Tsirkin
2012-03-21 18:28 ` Michael S. Tsirkin
2012-03-21 18:11 ` [Qemu-trivial] " Michael S. Tsirkin
2012-03-21 18:11 ` Michael S. Tsirkin
2012-03-20 10:53 ` Michael S. Tsirkin
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=4F69F05B.5010500@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=rusty@rustcorp.com.au \
/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.