From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "Paul Mackerras" <paulus@samba.org>,
"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 07:15:07 +0200 [thread overview]
Message-ID: <53A9095B.3070803@redhat.com> (raw)
In-Reply-To: <53A89D98.3030708@ozlabs.ru>
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".
.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).
> Looks like I must copy PC_COMPAT_X_X as PSERIES_COMPAT_X_X starting 1.6 (or
> 1.7 - whichever starts supporting migration well enough on pseries) because
> pretty much of what they do is tweaking PCI devices and we can have all of
> these devices on pseries.
It's not necessary to do this retroactively, unless you're planning to
test forward migration from 1.6 to 2.1. Just start with 2.2 (and add
pseries-2.1 now as an alias).
Note that firmware interfaces and CPU features should also be versioned
if they're guest visible. That's the point of functions like pc_compat_1_6.
> And then keep an eye on what is happening in PC
> world to copy same tweaks to pseries as they come. Is that correct?
Yes. We should come up sooner or later with a way to share the tweaks
though.
> Others (ARM, s390) do not do that because they do not support PCI? Or
> migration? Or some other reason?
This is not limited to PCI. Others do not support migration across
different QEMU versions.
Paolo
next prev parent reply other threads:[~2014-06-24 5:15 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 [this message]
2014-06-24 5:37 ` Alexey Kardashevskiy
2014-06-24 8:17 ` Markus Armbruster
2014-06-24 9:10 ` Alexey Kardashevskiy
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=53A9095B.3070803@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.com \
--cc=aik@ozlabs.ru \
--cc=paulus@samba.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).