From: Blue Swirl <blauwirbel@gmail.com>
To: malc <av1474@comtv.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>, Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Standard vga breakage
Date: Sun, 15 Nov 2009 23:35:29 +0200 [thread overview]
Message-ID: <f43fc5580911151335k51fb187aq6d98243847ec21da@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0911160019370.2440@linmac.oyster.ru>
On Sun, Nov 15, 2009 at 11:21 PM, malc <av1474@comtv.ru> wrote:
> On Sun, 15 Nov 2009, Stefan Weil wrote:
>
>> malc schrieb:
>> > On Sun, 15 Nov 2009, Gleb Natapov wrote:
>
> [..snip..]
>
>>
>> Here is a summary of my analysis of this problem:
>>
>> Graphics mode memory (ram 0xe0000000 ...) is not mapped
>> in QEMU address space (which results in unassigned
>> memory writes) for standard pci vga (-vga std), so users
>> don't get vga display output with grub (in graphical mode),
>> debian installer (in graphical mode) or similar boot software.
>>
>> This happens for PC system emulation using SeaBIOS.
>> It won't happen when using Bochs BIOS.
>>
>> Other system emulations which can run standard pci vga
>> seem to suffer from the same problem: when I run mips
>> malta using -vga std, it won't display anything on the vga
>> screen (it works with cirrus pci vga).
>>
>> Malta has no vga bios, so the error might be in QEMU's
>> vga code (hw/vga-pci.c). Maybe wrong initial PCI mappings?
>> Maybe this has always be wrong (which would explain why
>> git bisect does not work).
>
> git bisect doesn't work because most of the time:
>
> a. Compilation fails
> b. Compilation succeeds but qemu segfaults before even trying to
> execute any guest code
With infinite time and resources, we could construct a fully
bisectable tree with the following properties:
- buggy commits (especially commits that break build or require manual
reconfiguration) are replaced with corrected commits by changing the
history
- no merges, linear history
- compound commits are broken down to simple, atomic versions
- documentation is added by the first commit to reduce the number of commits
- spelling fixes applied by changing history, not as a separate commit
- each commit should still have some relation to some real tree commit
next prev parent reply other threads:[~2009-11-15 21:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 1:25 [Qemu-devel] Standard vga breakage malc
2009-11-15 10:20 ` Blue Swirl
2009-11-15 15:22 ` malc
2009-11-15 15:28 ` Gleb Natapov
2009-11-15 15:40 ` malc
2009-11-15 20:16 ` Stefan Weil
2009-11-15 20:37 ` Blue Swirl
2009-11-15 21:21 ` malc
2009-11-15 21:35 ` Blue Swirl [this message]
2009-11-16 18:21 ` Stefan Weil
2009-11-16 19:12 ` Anthony Liguori
2009-11-16 20:11 ` [Qemu-devel] [PATCH] vga-pci: Fix access to linear framebuffer Stefan Weil
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=f43fc5580911151335k51fb187aq6d98243847ec21da@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=av1474@comtv.ru \
--cc=gleb@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).