From: "Blue Swirl" <blauwirbel@gmail.com>
To: sol10x86@cox.net, qemu-devel@nongnu.org
Cc: risc@volumehost.com
Subject: Re: [Qemu-devel] Regression bug
Date: Tue, 29 May 2007 20:34:02 +0300 [thread overview]
Message-ID: <f43fc5580705291034n7f33d02eg8a5293144187b438@mail.gmail.com> (raw)
In-Reply-To: <2765066.1180444125665.JavaMail.root@eastrmwml26.mgt.cox.net>
On 5/29/07, Ben Taylor <sol10x86@cox.net> wrote:
> Looks like the patch from http://cvs.savannah.gnu.org/viewcvs/qemu/exec.c?cvsroot=qemu&r1=1.96&r2=1.97
> needs to be reverted and reworked before being recommitted.
Thank you for the reports. I still can't reproduce the bug, but it
seems that on PC, the area between 0xa0000 and 0x100000 is registered
multiple times and this could confuse the subpage code.
Adding printf to cpu_register_physical memory reveals:
cpu_register_physical_memory: start_addr 00000000000a0000 size 1000 phys_offset
70
cpu_register_physical_memory: start_addr 00000000000a0000 size 1000 phys_offset
70
cpu_register_physical_memory: start_addr 00000000000a0000 size 1000 phys_offset
70
cpu_register_physical_memory: start_addr 00000000000a0000 size 1000 phys_offset
70
cpu_register_physical_memory: start_addr 00000000000a0000 size 1000 phys_offset
70
cpu_register_physical_memory: start_addr 00000000000a0000 size 20000 phys_offset
70
cpu_register_physical_memory: start_addr 00000000000a0000 size 20000 phys_offset
a0000
The subpage part in cpu_register_physical_memory could be disabled
just for i386. A better fix would be to fix the PC/VGA/PIIX memory
registrations and also make the subpage code handle this case.
next prev parent reply other threads:[~2007-05-29 17:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 13:08 [Qemu-devel] Regression bug Ben Taylor
2007-05-29 17:34 ` Blue Swirl [this message]
2007-05-29 18:44 ` Blue Swirl
2007-05-29 19:04 ` risc
2007-05-29 19:33 ` Blue Swirl
2007-05-29 20:01 ` risc
-- strict thread matches above, loose matches on Subject: below --
2007-05-30 11:27 Ben Taylor
2007-05-29 5:10 Ben Taylor
2007-05-29 8:56 ` Xavier Gnata
2007-05-29 12:31 ` risc
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=f43fc5580705291034n7f33d02eg8a5293144187b438@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=risc@volumehost.com \
--cc=sol10x86@cox.net \
/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).