From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Eduardo Habkost" <ehabkost@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Paul Mackerras" <paulus@samba.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Alexander Graf" <agraf@suse.com>
Subject: Re: [Qemu-devel] machines and versions - why so many?
Date: Tue, 24 Jun 2014 19:10:41 +1000 [thread overview]
Message-ID: <53A94091.2000406@ozlabs.ru> (raw)
In-Reply-To: <87bnti202c.fsf@blackfin.pond.sub.org>
On 06/24/2014 06:17 PM, Markus Armbruster wrote:
> Alexey Kardashevskiy <aik@ozlabs.ru> writes:
>
>> On 06/24/2014 03:15 PM, Paolo Bonzini wrote:
>>> Il 23/06/2014 23:35, Alexey Kardashevskiy ha scritto:
>>>> nec-usb-xhci is off for PC_COMPAT_1_3 because of what? PIIX emulation was
>>>> broken in 1.3? Or nec-usb-xhci?
>>>
>>> nec-usb-xhci is not "off".
>>
>> Yes, my bad, I understood (but explained this wrong) that XHCI is enabled
>> but without MSI.
>>
>>
>>>
>>> .driver = "nec-usb-xhci",\
>>> .property = "msi",\
>>> .value = "off",\
>>>
>>> What's off is MSI (and MSI-X), because it wasn't implemented.
>>>
>>>> If it is the latter, why is the tweak limited by PC?
>>>
>>> Because at the time nobody cared about migration compatibility (even now
>>> only pSeries is starting to care).
>>
>>
>> "only pSeries"? There are plenty of x86 machines already and if it is not
>> for migration support, then what are they all for? :)
>
> At the time, nobody *else* cared. Only PC did.
Ah. Misinterpret. My bad. Ok.
>
> Back then gerd created a way to do the compatibility stuff without
> getting into the other target's hair: compat_props. They've served us
> well enough, but now that more targets get interested in migration,
> their shortcomings start to hurt. Having to duplicate device
> compatibility gunk in multiple places, all far away from the device, is
> decidedly suboptimal. Better ideas welcome.
I would suggest moving PC_COMPAT_X_Y things to platform-independent place
but "[RFC v2 00/39] Convert PC machine-types to QOM classes" is already
huge and complicated, and also "pseries" does not really need stuff below
1.6, may be it is not worth it...
--
Alexey
next prev parent reply other threads:[~2014-06-24 9:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 14:15 [Qemu-devel] machines and versions - why so many? Alexey Kardashevskiy
2014-06-23 14:59 ` Paolo Bonzini
2014-06-23 21:35 ` Alexey Kardashevskiy
2014-06-23 21:41 ` Andreas Färber
2014-06-23 22:33 ` Alexey Kardashevskiy
2014-06-24 5:21 ` Paolo Bonzini
2014-06-24 11:15 ` Andreas Färber
2014-06-24 13:05 ` Alexey Kardashevskiy
2014-06-24 12:38 ` Marcel Apfelbaum
2014-06-23 21:41 ` Peter Maydell
2014-06-24 5:15 ` Paolo Bonzini
2014-06-24 5:37 ` Alexey Kardashevskiy
2014-06-24 8:17 ` Markus Armbruster
2014-06-24 9:10 ` Alexey Kardashevskiy [this message]
2014-06-24 11:22 ` Andreas Färber
2014-06-24 12:56 ` Alexey Kardashevskiy
2014-06-23 15:16 ` Markus Armbruster
2014-06-24 1:06 ` Alexey Kardashevskiy
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=53A94091.2000406@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=afaerber@suse.de \
--cc=agraf@suse.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=paulus@samba.org \
--cc=pbonzini@redhat.com \
--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 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.