From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Bug 1180923 <1180923@bugs.launchpad.net>,
qemu-devel <qemu-devel@nongnu.org>, TC1988 <panie@tiscali.it>
Subject: Re: [Qemu-devel] [Bug 1180923] [NEW] unused memory filled with 0x00 instead of 0xFF
Date: Thu, 16 May 2013 21:52:56 +0200 [thread overview]
Message-ID: <CAJSP0QUWf8RVrGtcajoq_pPrHaPMU+U4uk-Lw4Kh8KwiYCMbEQ@mail.gmail.com> (raw)
In-Reply-To: <51953162.3000107@redhat.com>
On Thu, May 16, 2013 at 9:20 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> Il 16/05/2013 19:34, TC1988 ha scritto:
>> Public bug reported:
>>
>> Qemu, ever since it was made (so, since 2003), has this problem in DOS
>> (either PC-DOS or MS-DOS and partly Windows 9x) not recognizing the
>> memory available when the memory is filled with 0x00 but when it is
>> filled with 0xFF it gets recognized properly, where should I patch qemu
>> to solve this memory problem?
>
> Can you provide reproduction instructions for this bug?
Sounds like (risky) memory probing. On a PC the memory regions that
are unpopulated produce 0xff.
But you're supposed to use e820 or other mechanisms to retrieve the
proper memory layout from the firmware.
Stefan
next prev parent reply other threads:[~2013-05-16 19:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 17:34 [Qemu-devel] [Bug 1180923] [NEW] unused memory filled with 0x00 instead of 0xFF TC1988
2013-05-16 17:40 ` [Qemu-devel] [Bug 1180923] " TC1988
2013-05-16 17:45 ` Battler
2013-05-16 19:20 ` [Qemu-devel] [Bug 1180923] [NEW] " Paolo Bonzini
2013-05-16 19:52 ` Stefan Hajnoczi [this message]
2013-05-16 20:00 ` Peter Maydell
2013-05-17 7:25 ` Paolo Bonzini
2013-05-17 15:59 ` Anthony Liguori
2013-05-21 1:31 ` Kevin O'Connor
2013-05-16 19:20 ` [Qemu-devel] [Bug 1180923] " Battler
2013-05-17 14:26 ` Battler
2013-05-17 14:36 ` Battler
2013-05-17 16:43 ` Battler
2020-08-07 9:25 ` Thomas Huth
2020-10-07 4:17 ` Launchpad Bug Tracker
2022-07-31 20:59 ` David Glover
2022-08-01 6:29 ` 罗勇刚(Yonggang Luo)
2022-08-01 6:29 ` Yonggang Luo
2022-08-01 6:30 ` Yonggang Luo
2023-06-12 21:57 ` Evren
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=CAJSP0QUWf8RVrGtcajoq_pPrHaPMU+U4uk-Lw4Kh8KwiYCMbEQ@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=1180923@bugs.launchpad.net \
--cc=panie@tiscali.it \
--cc=pbonzini@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).