From: Blue Swirl <blauwirbel@gmail.com>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Artyom Tarasenko <atar4qemu@googlemail.com>
Subject: Re: [Qemu-devel] Re: "Bad ram offset"?
Date: Wed, 29 Sep 2010 16:09:23 +0000 [thread overview]
Message-ID: <AANLkTikTJGzZOca5WbZCpb2VQqD946-0iTdRqzAnmq4N@mail.gmail.com> (raw)
In-Reply-To: <25955517-8FA0-4FDC-A802-3EAAD13AFFBA@web.de>
On Tue, Sep 28, 2010 at 8:42 PM, Andreas Färber <andreas.faerber@web.de> wrote:
> Am 28.09.2010 um 22:24 schrieb Blue Swirl:
>
>> On Tue, Sep 28, 2010 at 8:02 PM, Andreas Färber <andreas.faerber@web.de>
>> wrote:
>>>
>>> Am 28.09.2010 um 21:31 schrieb Artyom Tarasenko:
>>>
>>>> 2010/9/28 Blue Swirl <blauwirbel@gmail.com>:
>>>>>
>>>>> On Mon, Sep 27, 2010 at 9:19 PM, Artyom Tarasenko
>>>>> <atar4qemu@googlemail.com> wrote:
>>>>>>
>>>>>> In today's git master:
>>>>>>
>>>>>> $ ./qemu-system-sparc64 -M sun4u -m 2048
>>>>>> Bad ram offset ffffffff80000000
>>>>>
>>>>> Smells like unwanted sign extension somewhere.
>>>>
>>>> fwiw, tested -m 2048 with i386 and x86-64 and they both are fine with
>>>> it. So it must be something platform-specific.
>>>
>>> Same behavior on ppc host fwiw.
>>
>> The attached patch should fix this.
>> <0001-sysbus-fix-address-truncation.patch>
>
>
> Tested-by: Andreas Färber <andreas.faerber@web.de>
>
> Above test cases work fine on ppc64 now. Anything else to cross-check?
32 bit host, like ppc32 or x86?
next prev parent reply other threads:[~2010-09-29 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 21:19 [Qemu-devel] "Bad ram offset"? Artyom Tarasenko
2010-09-28 17:43 ` [Qemu-devel] " Blue Swirl
2010-09-28 19:31 ` Artyom Tarasenko
2010-09-28 19:45 ` Blue Swirl
2010-09-28 20:02 ` Andreas Färber
2010-09-28 20:24 ` Blue Swirl
2010-09-28 20:42 ` Andreas Färber
2010-09-29 16:09 ` Blue Swirl [this message]
2010-09-30 20:36 ` Artyom Tarasenko
2010-10-02 14:47 ` Blue Swirl
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=AANLkTikTJGzZOca5WbZCpb2VQqD946-0iTdRqzAnmq4N@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=andreas.faerber@web.de \
--cc=atar4qemu@googlemail.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).