From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Jamie Lokier <jamie@shareable.org>, Avi Kivity <avi@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
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 16:45:46 +0200 [thread overview]
Message-ID: <20091011144545.GB10429@redhat.com> (raw)
In-Reply-To: <20091011143946.GP16702@redhat.com>
On Sun, Oct 11, 2009 at 04:39:46PM +0200, Gleb Natapov wrote:
> On Sun, Oct 11, 2009 at 04:35:35PM +0200, Michael S. Tsirkin wrote:
> > On Sun, Oct 11, 2009 at 03:57:48PM +0200, Gleb Natapov wrote:
> > > On Sun, Oct 11, 2009 at 03:52:40PM +0200, Michael S. Tsirkin wrote:
> > > > On Sun, Oct 11, 2009 at 03:45:59PM +0200, Gleb Natapov wrote:
> > > > > On Sun, Oct 11, 2009 at 03:36:26PM +0200, Michael S. Tsirkin wrote:
> > > > > > > No, I think Avi was right the first time.
> > > > > > >
> > > > > > > Migrating from an older qemu will be fine at first, but at the next
> > > > > > > reset _following_ migration, it'll be running the old BIOS on a new
> > > > > > > qemu and fail.
> > > > > > >
> > > > > > > -- Jamie
> > > > > >
> > > > > > So after discussion with Gleb, it seems that what will happen
> > > > > > after migration to new qemu, old BIOS is shadowed, but memory
> > > > > > is already enabled. After reset, new BIOS will be shadowed
> > > > > > and it will enable memory. Makes sense?
> > > > > >
> > > > > I don't see how you made this conclusion after the discussion.
> > > > > What should happen is after migration old bios should be used until reboot.
> > > > > After reboot new bios should be used.
> > > >
> > > > I think that's what I said.
> > > >
> > > First shadowing bios has nothing to do with it. Second what do you mean
> > > by "will happen"? That is how code works now or that is how it should
> > > work? I am not sure this is how it works.
> >
> > No, this is not how it works, I think.
> > Currently BIOS ROM is loaded only on init, directly into qemu memory.
> And have you checked if it is transfered to destination on migrate?
>
> > BTW, I don't think it's write-protected and it probably should be?
> >
> AFAIR it is not writable on plain qemu.
What makes it non-writeable?
It goes:
bios_offset = qemu_ram_alloc(bios_size);
ret = load_image(filename, qemu_get_ram_ptr(bios_offset));
Does qemu_ram_alloc allocate read-only memory then?
> --
> Gleb.
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Avi Kivity <avi@redhat.com>, kvm-devel <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: [PATCH 2/3] qemu: make cirrus init value pci spec compliant
Date: Sun, 11 Oct 2009 16:45:46 +0200 [thread overview]
Message-ID: <20091011144545.GB10429@redhat.com> (raw)
In-Reply-To: <20091011143946.GP16702@redhat.com>
On Sun, Oct 11, 2009 at 04:39:46PM +0200, Gleb Natapov wrote:
> On Sun, Oct 11, 2009 at 04:35:35PM +0200, Michael S. Tsirkin wrote:
> > On Sun, Oct 11, 2009 at 03:57:48PM +0200, Gleb Natapov wrote:
> > > On Sun, Oct 11, 2009 at 03:52:40PM +0200, Michael S. Tsirkin wrote:
> > > > On Sun, Oct 11, 2009 at 03:45:59PM +0200, Gleb Natapov wrote:
> > > > > On Sun, Oct 11, 2009 at 03:36:26PM +0200, Michael S. Tsirkin wrote:
> > > > > > > No, I think Avi was right the first time.
> > > > > > >
> > > > > > > Migrating from an older qemu will be fine at first, but at the next
> > > > > > > reset _following_ migration, it'll be running the old BIOS on a new
> > > > > > > qemu and fail.
> > > > > > >
> > > > > > > -- Jamie
> > > > > >
> > > > > > So after discussion with Gleb, it seems that what will happen
> > > > > > after migration to new qemu, old BIOS is shadowed, but memory
> > > > > > is already enabled. After reset, new BIOS will be shadowed
> > > > > > and it will enable memory. Makes sense?
> > > > > >
> > > > > I don't see how you made this conclusion after the discussion.
> > > > > What should happen is after migration old bios should be used until reboot.
> > > > > After reboot new bios should be used.
> > > >
> > > > I think that's what I said.
> > > >
> > > First shadowing bios has nothing to do with it. Second what do you mean
> > > by "will happen"? That is how code works now or that is how it should
> > > work? I am not sure this is how it works.
> >
> > No, this is not how it works, I think.
> > Currently BIOS ROM is loaded only on init, directly into qemu memory.
> And have you checked if it is transfered to destination on migrate?
>
> > BTW, I don't think it's write-protected and it probably should be?
> >
> AFAIR it is not writable on plain qemu.
What makes it non-writeable?
It goes:
bios_offset = qemu_ram_alloc(bios_size);
ret = load_image(filename, qemu_get_ram_ptr(bios_offset));
Does qemu_ram_alloc allocate read-only memory then?
> --
> Gleb.
next prev parent reply other threads:[~2009-10-11 14:48 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1255013225.git.mst@redhat.com>
2009-10-08 14:52 ` [PATCH 1/3] pc-bios: enable io/memory unconditionally Michael S. Tsirkin
2009-10-08 14:52 ` [Qemu-devel] " Michael S. Tsirkin
2009-10-08 14:52 ` [PATCH 2/3] qemu: make cirrus init value pci spec compliant Michael S. Tsirkin
2009-10-08 14:52 ` [Qemu-devel] " Michael S. Tsirkin
2009-10-08 15:29 ` Avi Kivity
2009-10-08 15:29 ` [Qemu-devel] " Avi Kivity
2009-10-08 16:06 ` Michael S. Tsirkin
2009-10-08 16:06 ` [Qemu-devel] " Michael S. Tsirkin
2009-10-08 16:13 ` Avi Kivity
2009-10-08 16:13 ` [Qemu-devel] " Avi Kivity
2009-10-08 18:40 ` Jamie Lokier
2009-10-08 18:40 ` Jamie Lokier
2009-10-08 19:39 ` Michael S. Tsirkin
2009-10-08 19:39 ` Michael S. Tsirkin
2009-10-09 6:43 ` Michael S. Tsirkin
2009-10-09 6:43 ` Michael S. Tsirkin
2009-10-09 7:00 ` Gleb Natapov
2009-10-09 7:00 ` Gleb Natapov
2009-10-09 10:13 ` Michael S. Tsirkin
2009-10-09 10:13 ` [Qemu-devel] " Michael S. Tsirkin
2009-10-09 11:49 ` Gleb Natapov
2009-10-09 11:49 ` Gleb Natapov
2009-10-09 12:59 ` Michael S. Tsirkin
2009-10-09 12:59 ` Michael S. Tsirkin
2009-10-09 15:08 ` Gleb Natapov
2009-10-09 15:08 ` Gleb Natapov
2009-10-12 13:45 ` Gerd Hoffmann
2009-10-12 13:45 ` Gerd Hoffmann
2009-10-12 13:53 ` Gleb Natapov
2009-10-12 13:53 ` Gleb Natapov
2009-10-12 14:50 ` Gerd Hoffmann
2009-10-12 14:50 ` Gerd Hoffmann
2009-10-12 14:52 ` Gleb Natapov
2009-10-12 14:52 ` Gleb Natapov
2009-10-12 15:21 ` Jamie Lokier
2009-10-12 15:21 ` Jamie Lokier
2009-10-12 15:43 ` Gerd Hoffmann
2009-10-12 15:43 ` [Qemu-devel] " Gerd Hoffmann
2009-10-12 16:57 ` Michael S. Tsirkin
2009-10-12 16:57 ` Michael S. Tsirkin
2009-10-09 11:37 ` Jamie Lokier
2009-10-09 11:37 ` Jamie Lokier
2009-10-09 11:54 ` Gleb Natapov
2009-10-09 11:54 ` Gleb Natapov
2009-10-11 13:36 ` Michael S. Tsirkin
2009-10-11 13:36 ` Michael S. Tsirkin
2009-10-11 13:45 ` Gleb Natapov
2009-10-11 13:45 ` Gleb Natapov
2009-10-11 13:52 ` Michael S. Tsirkin
2009-10-11 13:52 ` [Qemu-devel] " Michael S. Tsirkin
2009-10-11 13:57 ` Gleb Natapov
2009-10-11 13:57 ` Gleb Natapov
2009-10-11 14:35 ` Michael S. Tsirkin
2009-10-11 14:35 ` Michael S. Tsirkin
2009-10-11 14:39 ` Gleb Natapov
2009-10-11 14:39 ` Gleb Natapov
2009-10-11 14:45 ` Michael S. Tsirkin [this message]
2009-10-11 14:45 ` Michael S. Tsirkin
2009-10-11 15:00 ` Gleb Natapov
2009-10-11 15:00 ` [Qemu-devel] " Gleb Natapov
2009-10-12 13:44 ` Anthony Liguori
2009-10-12 13:44 ` [Qemu-devel] " Anthony Liguori
2009-10-12 14:21 ` Gleb Natapov
2009-10-12 14:21 ` Gleb Natapov
2009-10-12 14:31 ` Anthony Liguori
2009-10-12 14:31 ` Anthony Liguori
2009-10-12 15:00 ` Kevin O'Connor
2009-10-12 15:00 ` Kevin O'Connor
2009-10-11 14:42 ` Avi Kivity
2009-10-11 14:42 ` Avi Kivity
2009-10-11 14:44 ` Michael S. Tsirkin
2009-10-11 14:44 ` Michael S. Tsirkin
2009-10-11 14:53 ` Avi Kivity
2009-10-11 14:53 ` Avi Kivity
2009-10-11 16:12 ` Michael S. Tsirkin
2009-10-11 16:12 ` Michael S. Tsirkin
2009-10-11 16:24 ` Avi Kivity
2009-10-11 16:24 ` Avi Kivity
2009-10-11 16:33 ` Michael S. Tsirkin
2009-10-11 16:33 ` Michael S. Tsirkin
2009-10-11 16:37 ` Avi Kivity
2009-10-11 16:37 ` Avi Kivity
2009-10-11 16:39 ` Michael S. Tsirkin
2009-10-11 16:39 ` [Qemu-devel] " Michael S. Tsirkin
2009-10-11 16:48 ` Avi Kivity
2009-10-11 16:48 ` [Qemu-devel] " Avi Kivity
2009-10-11 17:18 ` Michael S. Tsirkin
2009-10-11 17:18 ` Michael S. Tsirkin
2009-10-11 17:27 ` Avi Kivity
2009-10-11 17:27 ` Avi Kivity
2009-10-11 17:28 ` Avi Kivity
2009-10-11 17:28 ` Avi Kivity
2009-10-11 18:10 ` Michael S. Tsirkin
2009-10-11 18:10 ` Michael S. Tsirkin
2009-10-11 20:41 ` Avi Kivity
2009-10-11 20:41 ` Avi Kivity
2009-10-08 14:52 ` [PATCH 3/3] qemu: cleanup unused macros in cirrus Michael S. Tsirkin
2009-10-08 14:52 ` [Qemu-devel] " Michael S. Tsirkin
2009-10-08 15:24 ` Juan Quintela
2009-10-08 16:07 ` Michael S. Tsirkin
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=20091011144545.GB10429@redhat.com \
--to=mst@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jamie@shareable.org \
--cc=kvm@vger.kernel.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 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.