All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] update bochs vbe interface
Date: Thu, 25 Mar 2010 10:10:34 +0100	[thread overview]
Message-ID: <4BAB288A.3020902@redhat.com> (raw)
In-Reply-To: <m3sk7oiydc.fsf@trasno.mitica>

   Hi,

> Then our big problem is migration between read of the 1st register and
> of the 2nd register, no?

"big"?  The window is quite small, and I think we have a bunch of 
simliar issues elsewhere in qemu.  They are hardly avoidable for new -> 
old migration when adding new features to emulated devices.

Well, maybe sections can fix it, but probably only in case the old qemu 
is new enougth that it can handle sections too.

> Furthermore, older vga bios, seing VBE_DISPI_ID5, what are they going to
> do?

Work as they did before ;)

>>   So when migrating from new to old qemu:  Before reset
>> vgabios will have the video memory size saved somewhere.  After reset
>> ID will reset to ID0, and in case you are running vgabios 0.6c vesa
>> gfx modes will stop working.
>
> I see this part, but I still think that we have a window where we can be
> in very bad shape, no?  I guess that we don't support anything different
> that vgabios, so ....

See above.  Worst case is that vesa graphics modes stop working, even if 
you hit the race window (vgabios will think you have 0 MB video ram then 
and refuse all gfx modes).

cheers,
   Gerd

  reply	other threads:[~2010-03-25  9:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 14:14 [Qemu-devel] [PATCH] update bochs vbe interface Gerd Hoffmann
2010-03-24 17:04 ` [Qemu-devel] " Juan Quintela
2010-03-24 19:44   ` Gerd Hoffmann
2010-03-24 22:28     ` Juan Quintela
2010-03-25  8:22       ` Gerd Hoffmann
2010-03-25  8:44         ` Juan Quintela
2010-03-25  9:10           ` Gerd Hoffmann [this message]
2010-03-25 12:14             ` Juan Quintela
2010-03-25 15:51               ` Gerd Hoffmann

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=4BAB288A.3020902@redhat.com \
    --to=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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.