qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PULL v3 00/15] Tracing patches


From: Alistair Francis
Subject: Re: [Qemu-devel] [PULL v3 00/15] Tracing patches
Date: Fri, 20 Nov 2015 17:45:40 +0530

On Fri, Nov 13, 2015 at 10:33 PM, Edgar E. Iglesias
<address@hidden> wrote:
> On Fri, Nov 13, 2015 at 11:28:41AM +0000, Peter Maydell wrote:
>> On 13 November 2015 at 10:30, Peter Maydell <address@hidden> wrote:
>> > I also now get a handful of extra warnings in the 'make check' output:
>> >
>> >   /aarch64/qom/xilinx-zynq-a9:                                         OK
>> >   /aarch64/qom/xlnx-ep108:
>> > WARNING: RAM size 8000000 is small for EP108OK
>> >   /aarch64/qom/vexpress-a9:                                            OK
>> >
>> > (note the missing newline...)
>> >
>> > TEST: tests/qom-test... (pid=19738)
>> >   /microblaze/qom/none:                                                OK
>> >   /microblaze/qom/petalogix-s3adsp1800:
>> > Invalid MicroBlaze version number: (null)
>> > OK
>> >   /microblaze/qom/petalogix-ml605:
>> > Invalid MicroBlaze version number: (null)
>> > OK
>>
>> Peter/Alistair/Edgar: this patchset of Stefan's has now been deferred
>> until 2.6, but you might want to look into the log warning issues
>> it exposed (the missing newline, attempt to print NULL, and maybe
>> whether the warnings should really be printed for a simple attempt
>> to start the board with no arguments).
>>
>
> Thanks,
>
> I've posted patches to fix the MicroBlaze warings on the list.
>
> I don't know what the inention was with the E1P08 warning.. IMO we
> can remove it...

The warning is there because the RAM size is user definable, if the
user tries to set a size that is too small QEMU will warn them.

I sent a patch that fixes up the size check logic.

Thanks,

Alistair

>
> Cheers,
> Edgar
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]