[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Re: "Bad ram offset"?
From: |
Blue Swirl |
Subject: |
Re: [Qemu-devel] Re: "Bad ram offset"? |
Date: |
Wed, 29 Sep 2010 16:09:23 +0000 |
On Tue, Sep 28, 2010 at 8:42 PM, Andreas Färber <address@hidden> wrote:
> Am 28.09.2010 um 22:24 schrieb Blue Swirl:
>
>> On Tue, Sep 28, 2010 at 8:02 PM, Andreas Färber <address@hidden>
>> wrote:
>>>
>>> Am 28.09.2010 um 21:31 schrieb Artyom Tarasenko:
>>>
>>>> 2010/9/28 Blue Swirl <address@hidden>:
>>>>>
>>>>> On Mon, Sep 27, 2010 at 9:19 PM, Artyom Tarasenko
>>>>> <address@hidden> 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 <address@hidden>
>
> Above test cases work fine on ppc64 now. Anything else to cross-check?
32 bit host, like ppc32 or x86?
- [Qemu-devel] "Bad ram offset"?, Artyom Tarasenko, 2010/09/27
- [Qemu-devel] Re: "Bad ram offset"?, Blue Swirl, 2010/09/28
- [Qemu-devel] Re: "Bad ram offset"?, Artyom Tarasenko, 2010/09/28
- [Qemu-devel] Re: "Bad ram offset"?, Blue Swirl, 2010/09/28
- Re: [Qemu-devel] Re: "Bad ram offset"?, Andreas Färber, 2010/09/28
- Re: [Qemu-devel] Re: "Bad ram offset"?, Blue Swirl, 2010/09/28
- Re: [Qemu-devel] Re: "Bad ram offset"?, Andreas Färber, 2010/09/28
- Re: [Qemu-devel] Re: "Bad ram offset"?,
Blue Swirl <=
- Re: [Qemu-devel] Re: "Bad ram offset"?, Artyom Tarasenko, 2010/09/30