From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Gleb Natapov <gleb@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Re: [PATCH 2/3] qemu: make cirrus init value pci spec compliant
Date: Sun, 11 Oct 2009 22:41:11 +0200 [thread overview]
Message-ID: <4AD242E7.1080705@redhat.com> (raw)
In-Reply-To: <20091011181024.GA6411@redhat.com>
On 10/11/2009 08:10 PM, Michael S. Tsirkin wrote:
>
> So this is what happens:
> - after migration from old qemu to new old BIOS is used until reset
> - after reset new BIOS is used
> - after upgrade from old version of qemu upgrade does not have any
> effect until qemu is restarted
>
> If this is a fair summary, the only issue with fixing BIOS bug
> is migration from new qemu to old qemu, and we do not care much.
>
Yes.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-10-11 20:41 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1255013225.git.mst@redhat.com>
2009-10-08 14:52 ` [Qemu-devel] [PATCH 1/3] pc-bios: enable io/memory unconditionally Michael S. Tsirkin
2009-10-08 14:52 ` [Qemu-devel] [PATCH 2/3] qemu: make cirrus init value pci spec compliant Michael S. Tsirkin
2009-10-08 15:29 ` [Qemu-devel] " Avi Kivity
2009-10-08 16:06 ` Michael S. Tsirkin
2009-10-08 16:13 ` Avi Kivity
2009-10-08 18:40 ` Jamie Lokier
2009-10-08 19:39 ` Michael S. Tsirkin
2009-10-09 6:43 ` Michael S. Tsirkin
2009-10-09 7:00 ` Gleb Natapov
2009-10-09 10:13 ` Michael S. Tsirkin
2009-10-09 11:49 ` Gleb Natapov
2009-10-09 12:59 ` Michael S. Tsirkin
2009-10-09 15:08 ` Gleb Natapov
2009-10-12 13:45 ` Gerd Hoffmann
2009-10-12 13:53 ` Gleb Natapov
2009-10-12 14:50 ` Gerd Hoffmann
2009-10-12 14:52 ` Gleb Natapov
2009-10-12 15:21 ` Jamie Lokier
2009-10-12 15:43 ` Gerd Hoffmann
2009-10-12 16:57 ` Michael S. Tsirkin
2009-10-09 11:37 ` Jamie Lokier
2009-10-09 11:54 ` Gleb Natapov
2009-10-11 13:36 ` Michael S. Tsirkin
2009-10-11 13:45 ` Gleb Natapov
2009-10-11 13:52 ` Michael S. Tsirkin
2009-10-11 13:57 ` Gleb Natapov
2009-10-11 14:35 ` Michael S. Tsirkin
2009-10-11 14:39 ` Gleb Natapov
2009-10-11 14:45 ` Michael S. Tsirkin
2009-10-11 15:00 ` Gleb Natapov
2009-10-12 13:44 ` Anthony Liguori
2009-10-12 14:21 ` Gleb Natapov
2009-10-12 14:31 ` Anthony Liguori
2009-10-12 15:00 ` Kevin O'Connor
2009-10-11 14:42 ` Avi Kivity
2009-10-11 14:44 ` Michael S. Tsirkin
2009-10-11 14:53 ` Avi Kivity
2009-10-11 16:12 ` Michael S. Tsirkin
2009-10-11 16:24 ` Avi Kivity
2009-10-11 16:33 ` Michael S. Tsirkin
2009-10-11 16:37 ` Avi Kivity
2009-10-11 16:39 ` Michael S. Tsirkin
2009-10-11 16:48 ` Avi Kivity
2009-10-11 17:18 ` Michael S. Tsirkin
2009-10-11 17:27 ` Avi Kivity
2009-10-11 17:28 ` Avi Kivity
2009-10-11 18:10 ` Michael S. Tsirkin
2009-10-11 20:41 ` Avi Kivity [this message]
2009-10-08 14:52 ` [Qemu-devel] [PATCH 3/3] qemu: cleanup unused macros in cirrus Michael S. Tsirkin
[not found] ` <m34oq9kix8.fsf@neno.mitica>
2009-10-08 16:07 ` [Qemu-devel] " 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=4AD242E7.1080705@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@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 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).