From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alex Bligh <alex@alex.org.uk>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 2/3] pc: Create 2.2 machine type
Date: Wed, 30 Jul 2014 10:44:45 +0200 [thread overview]
Message-ID: <53D8B07D.4080705@siemens.com> (raw)
In-Reply-To: <53D8AFBE.2060901@alex.org.uk>
On 2014-07-30 10:41, Alex Bligh wrote:
> On 30/07/2014 08:02, Jan Kiszka wrote:
>> Yet identical to 2.1.
>
> If it's *really* identical to 2.1, are we going to add the
> 2.2 machine type to 2.1 as well, so that things that
> have difficulty using different source and destination
> machine types can migrate from 2.2 to 2.1?
>
> Or am I missing the point and is the issue that 2.2
> is actually different to 2.1, not in the machine
> type definition, but in what is sent within the
> migrated data? If so, a commit message to this
> effect might be helpful.
See patch 3 for the (current) motivation of this patch. Maybe more will
come as 2.2 evolves.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2014-07-30 8:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 7:01 [Qemu-devel] [PATCH 0/3] pc: Small fixes for Intel HDA config space and PC_COMPAT_1_0 Jan Kiszka
2014-07-30 7:01 ` [Qemu-devel] [PATCH 1/3] pc: Fix disabling of vapic for compat PC models Jan Kiszka
2014-07-30 8:57 ` Michael S. Tsirkin
2014-07-30 9:11 ` Paolo Bonzini
2014-07-30 11:19 ` Markus Armbruster
2014-09-02 15:11 ` Michael Roth
2014-10-02 7:27 ` Jan Kiszka
2014-10-02 8:03 ` Michael S. Tsirkin
2014-10-02 8:05 ` Jan Kiszka
2014-10-02 8:17 ` Michael S. Tsirkin
2014-07-30 7:02 ` [Qemu-devel] [PATCH 2/3] pc: Create 2.2 machine type Jan Kiszka
2014-07-30 8:41 ` Alex Bligh
2014-07-30 8:44 ` Jan Kiszka [this message]
2014-07-30 7:02 ` [Qemu-devel] [PATCH 3/3] hw/audio/intel-hda: Fix MSI capability address Jan Kiszka
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=53D8B07D.4080705@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=alex@alex.org.uk \
--cc=mst@redhat.com \
--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.